PROBIE
Fix these issues
Report readyDispatch 93

We found 1 issuecosting you truston ibuildinpublic.com.

Probie inspected ibuildinpublic.com the way a new customer would. 1 page, desktop and phone, 8 minutes. Oct 13, 2026.

Probie could not finish a customer's path through the product. Onboarding and the Premium upgrade are only reachable after creating an account, so a visitor who does not sign up cannot get past the sign-up step.

Makers checking whether the community is real before signing up find the headline member count does not match the project's own directory.

1 page visited126 controls found0 clicked
ibuildinpublic.com's report cardOct 13, 2026

The sign-up page claims +1000 builders but the directory lists 273.

0 serious1 medium
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.
85Trust before buyingThe sign-up page claims +1000 builders but the directory lists 273
100MobileNo verified phone layout problems on the pages a buyer needs.
100SpeedNo verified slow pages or slow responses on the pages a buyer needs.
100Polish and auditNo verified accessibility, security header or visual polish problems.
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
Medium/signup · phone

The sign-up page claims +1000 builders but the directory lists 273

Makers checking whether the community is real before signing up find the headline member count does not match the project's own directory.

The avatar wall on the home page and on /signup reads "+1000 builders · tap a profile", directly beside the sign-up form. The public /builders directory reads "273 builders · Showing 1, 20". The avatars also link to x.com profiles, not to builder pages on the project, so "tap a profile" never shows a visitor a builder on ibuildinpublic.

ibuildinpublic.com/signup
Captured during the scan: The sign-up page claims +1000 builders but the directory lists 273
from the scan · /signup · mobileopen full capture ↗

Try it: Open /signup and read the caption under the avatar wall. Then open /builders and compare it with the "273 builders" count.

additional findings
Medium

Keyboard focus lands on demo controls hidden behind the home hero

On the mobile home page, keyboard focus can land on a demo chat INPUT and a Follow back button from the faded background widgets. When they are focused, the hero's Log in link and an avatar image paint on top of them, so the focus sits on a control nobody can see. This is an accessibility gap in the decorative layer and does not block Log in or Start free.

Medium

The home page has no Cross-Origin-Resource-Policy header

The response from https://www.ibuildinpublic.com/ is missing Cross-Origin-Resource-Policy.

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
PRFix: The sign-up page claims +1000 builders but the directory lists 273
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.