PROBIE
Fix these issues
Report readyDispatch 34

Nothing onradius.toworth reporting.

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

Nothing serious broke.

0 issues
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
scores · out of 100
100Getting the productEvery step checked between arriving and paying worked.
100Trust before buyingNo contradictions or broken pages found before buying.
100MobileNo verified phone layout problems on the pages a buyer needs.
100SpeedNo verified slow pages or slow responses on the pages a buyer needs.
68Polish and auditThe last member row is clipped by the Load more panel
How the composite score works

The overall score is a weighted average of the categories: Getting the product 40%, Trust before buying 20%, Mobile 15%, Speed 15%, and Polish and audit 10%. It is never more than 10 points above the Getting the product score, because a product a visitor cannot get cannot score well on anything else, and never more than 25 points above the weakest category, so one badly broken area is not averaged away. Any issue in the main list caps it at 89, so a score above 90 means nothing worth fixing was found.

Each category starts at 100 and stays there when nothing was found in it, whether or not the inspection got that far. Each distinct verified finding deducts 60 points for a serious problem on the path from arriving to paying, 40 for another serious problem, 30, 15 or 8 by high, medium or low severity otherwise, and 4 for an audit finding. Each additional finding below the list takes 2 more points off the overall score, up to 10. Scores stop at zero and round to whole numbers. The formula is fixed and versioned, so the same saved evidence always receives the same score.

issues
No issues found in the pages and actions checked.
additional findings
Medium

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.

Medium

A map marker covers the zoom-in button on mobile

On /members at a 390px wide viewport, the map's right edge control stack is partly covered by a large circular avatar marker. The top of the stack, the zoom-in button, sits behind the marker, so only the minus button and the compass control below it stay reachable. The same overlap appears at the same spot on a fresh load, with the marker shifted slightly but still sitting over the top control.

Medium

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. Each avatar links to a separate profile route, so a tap near an edge lands on a neighbouring member.

Medium

Two security response headers are missing

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

Medium

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.

Medium

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. 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.

from report to pull request

Probie fixes this for you.

Stop customers hitting the same friction. Connect your codebase and Probie reproduces these failures, tests the fix, and opens a pull request for your review.

Sign up and get this fixed
PRFixes, one PR at a time
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.