PROBIE
Fix these issues
Report readyDispatch 34

We found 6 issueson radius.toworth fixing.

Probie inspected radius.to the way a new customer would. 6 pages, desktop and phone, 24 minutes. Sep 22, 2026.

6 pages visited346 controls found101 clicked
radius.to's report cardSep 22, 2026

Member avatar links are too small to tap on mobile.

0 serious6 minor
See the breakdown
Probie doesn't stop at the report.Sign up and turn these findings into tested pull requests.
Fix these issues →
Probie on site

Watch the inspection.

We navigate your site the way customers would. Idle time is skipped.

Inspect your own site
the grades
B-VisualThe Toronto Ruby logo ships 328 KB for a 48 px icon
B-AccessibilityLow contrast text fails the AA threshold on several pages
AButtons and linksEverything we clicked did something.
BUnder the hoodTwo security response headers are missing
BMobileMember avatar links are too small to tap on mobile
the issues
Minorhome page · phone

Member avatar links are too small to tap on mobile

On the mobile home page and /feed, the overlapping member avatar links in the "Samuel R. and 40 others joined Radius" row are 20px by 20px, below the 24px by 24px minimum required by WCAG 2.5.8, and they overlap each other. axe-core reports target-size (serious) against a[aria-label="Fred M."], a[aria-label="Christopher B."] and a[aria-label="Nathan J."], with safe clickable space measured at 8px and 0px diameter instead of at least 24px. Each avatar links to a separate profile route, so a tap near an edge lands on a neighbouring member.

radius.to
Captured during the scan: Member avatar links are too small to tap on mobile
from the scan · / · mobileopen full capture ↗

Try it: Open / on a phone, scroll to the "Samuel R. and 40 others joined Radius" row, and try tapping a single avatar in the overlapping stack.

Minor/groups

The Toronto Ruby logo ships 328 KB for a 48 px icon

On /groups, the Toronto Ruby group logo is served at its full 1024x1024 intrinsic size and 336,259 bytes, then rendered into a 48x48 box at device pixel ratio 1. That is roughly 21 times the pixels actually painted, and the file is by far the heaviest asset on the listing page, where every other avatar and logo is a few kilobytes. The image is also marked loading="lazy" while sitting in the first card above the fold.

radius.to/groups
Captured during the scan: The Toronto Ruby logo ships 328 KB for a 48 px icon
from the scan · /groups · desktopopen full capture ↗

Try it: Open /groups on desktop with DevTools Network filtered to images and check the size of toronto-ruby-logo-transparent.png against its 48x48 rendered box.

Minorhome page

Two security response headers are missing

The response from https://radius.to/ is missing Content-Security-Policy and Cross-Origin-Resource-Policy.

radius.to
Captured during the scan: Two security response headers are missing
from the scan · / · desktopopen full capture ↗

Try it: Run curl -sI https://radius.to/ and look for Content-Security-Policy and Cross-Origin-Resource-Policy in the response headers.

Minorhome page

Low contrast text fails the AA threshold on several pages

Several pieces of small text on radius.to render below the WCAG AA contrast minimum. The "Activity Feed" link on the home page sits at 4.35:1 (#71717b on #000000, 14px), and the form labels "What best describes you?" and "Choose an interest" sit at 3.84:1 (#71717b on #131316, 14px), against a required 4.5:1. The same color-contrast failure appears on /, /groups and /members.

radius.to
Captured during the scan: Low contrast text fails the AA threshold on several pages
from the scan · / · desktopopen full capture ↗

Try it: Open radius.to, scroll to the "Activity Feed" link at the right of the hero, and sample its text color with a contrast checker against the black background.

Minor/members

The member list panel cannot be scrolled by keyboard

On /members the member list panel is a scrollable container that keyboard users cannot reach or scroll. axe-core flags the element `<div aria-live="polite" class="flex-1 min-h-0 overflow-y-auto scrollbar-dark" data-beta-members-map-target="memberList">` under the rule scrollable-region-focusable at impact level serious, mapped to WCAG 2.1.1 and 2.1.3. The container has overflow-y-auto with content taller than its box, but it is neither focusable itself nor contains focusable content, so the list of members below the visible rows is only available with a pointer. Three similar findings on the same route were suppressed.

radius.to/members
Captured during the scan: The member list panel cannot be scrolled by keyboard
from the scan · /members · desktopopen full capture ↗

Try it: Open /members on desktop, press Tab repeatedly, and try to scroll the left member list with the arrow keys without touching the mouse.

Minor/members · phone

The last member row is clipped by the Load more panel

On /members at a 390px-wide viewport, the final member row in the list is cut off by the footer panel that holds the "Load more" button. The row's name line renders in full, but the timestamp line directly under it is sliced horizontally, showing only the top half of the characters, and the location line and interest tags that other rows carry are not visible at all. Rows above it, such as "Abdul G.", render name, timestamp and location with full height.

radius.to/members
Captured during the scan: The last member row is clipped by the Load more panel
from the scan · /members · mobileopen full capture ↗

Try it: Open /members on a phone-width viewport and look at the last row above the "Load more" button: its timestamp line is sliced in half by the panel edge.

polish
Polish

The "What" text sits awkwardly

The "What's nearby" and "Browse Groups" buttons in the hero CTA row have different heights and vertical centers, with the purple button top edge sitting about 8px above and its bottom edge about 25px

Polish

A rough edge in the layout

The location and timestamp metadata line in the Bitcoin Meetup activity card runs together with no separator or space between the location text and the relative time text.

Polish

A rough edge in the layout

The footer link columns are unevenly distributed, with Product, Company and Explore packed at the left and Resources pushed to the far right edge, leaving a wide gap between the third and fourth colum

Polish

A rough edge in the layout

The location and timestamp metadata line in the tami activity card runs together with no separator or space between the location text and the relative time text.

Polish

A rough edge in the layout

The hero call to action buttons are inconsistently sized and aligned: the first row holds two buttons of unequal width and the third button on the second row spans a different width, breaking the butt

from report to pull request

Probie fixes this for you.

This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.

Sign up and get this fixed
PRFix: Member avatar links are too small to tap on mobile
probie/fix-1+12−4checks passing

Free inspection

What should Probie inspect next?

Enter a project URL. There is nothing to install.

Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.

Send this report to an inbox.

Enter an address and we will email the report card link.