PROBIE
Fix these issues
Report readyDispatch 43

Nothing onpostraid.comworth reporting.

Probie inspected postraid.com the way a new customer would. 11 pages, desktop and phone, 14 minutes. Sep 25, 2026.

11 pages visited253 controls found48 clicked
postraid.com's report cardSep 25, 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.
40Polish and auditExplore rows misalign across the first card row
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 Industries nav pill is clipped off the mobile screen

On /for at a 390px wide viewport, the secondary nav row (Tools, Compare, Alternatives, Industries) is wider than the screen. The black "Industries" pill starts near the right edge and runs past it, so its label is cut mid-word and the pill's right end and any items after it are off screen. The row is the active-page indicator for this route, and it is the only nav item a phone visitor cannot read.

Medium

The header nav row is cut off on mobile

On /record-product-demo at a 390px wide viewport, the header navigation row runs past the right edge of the screen. "Tools", "Compare" and "Alternatives" fit, but the fourth item is truncated mid-word at the viewport boundary and any items after it are not reachable without horizontal scrolling. The row has no visible scroll affordance or wrap, so those navigation destinations are effectively hidden on a phone.

Medium

The tools nav row is cut off at the right edge on mobile

On /tools/ugc-ads at a 390px wide viewport, the secondary navigation row below the header runs past the right edge of the screen. "Tools", "Compare" and "Alternatives" fit, but the next item is sliced mid word at the viewport boundary with no wrap and no visible scroll affordance, so there is nothing to indicate more nav items exist beyond it. The same clipping appears at the top of the page on a fresh load.

Medium

Six security response headers are missing

The response from https://www.postraid.com/ is missing Strict-Transport-Security, Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, X-Content-Type-Options: nosniff, Referrer-Policy, and Cross-Origin-Resource-Policy.

Medium

Format labels on the home page use a prohibited ARIA attribute

On the home page, the format labels in the sample batch library carry an aria-label on a plain span with no role, which ARIA does not permit, so the label is not guaranteed to reach assistive technology.

Medium

Grey body text on the contact page fails contrast

On /contact, several text elements fall below the WCAG AA contrast minimum of 4.5:1. The "Email us" eyebrow above the address renders at #999999 on #ffffff for a ratio of 2.84, and the supporting lines "We answer within one business day, usually sooner." and the paragraph starting "Support goes faster when the first email already has the details." render at #808080 on #ffffff for a ratio of 3.94. The same color-contrast failure appears on /record-product-demo, /tools and /alternatives.

Medium

Social platform icons lack accessible text

The parent buttons do carry aria-labels, so the platform name is still announced, but the graphic itself is exposed as an unnamed image role in the accessibility tree. The markup is <svg stroke="currentColor" fill="currentColor" stroke-width="0" role="img" viewBox="0 0 24 24" height="16" width="16">.

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.