We found 2 issuescosting you truston trytofu.ai.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
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.
The pricing page and the terms disagree on paid billing
Conflicting purchase terms undermine trust before customers pay.
The pricing card on / states "Tofu $9.99/mo For up to five apps that need builds and ongoing updates" with the feature line "Up to 5 apps with managed hosting". The terms page states "Paid plans are billed monthly per app. The current paid plan is USD 9.99 per app per month". One describes $9.99 covering five apps, the other $9.99 for each app, so a customer running five apps would owe either $9.99 or $49.95 per month depending on which page they read. Both statements are present on the live routes.
Try it: Open / and read the paid Tofu card, then open /terms and read the "Plans and what you pay" section; compare the per-app wording against "up to five apps".
The MCP bridge tool count differs between features and docs
Customers have to decide which of your promises to trust.
The /features page states "Twenty-two tools do the same work as the dashboard: upload, framework confirmation, the safety check, deploy, status, logs, history, rollback, environment names, a repair brief, the app's managed database and a domain you own." The /docs page, describing the same MCP bridge and the same device-flow connection, states "The bridge exposes 30 tools:" followed by the grouped table of tool names. Both passages describe the tool set of the bridge, so one of the two counts is out of date.
Try it: Open /features and search for "Twenty-two tools", then open /docs and search for "The bridge exposes 30 tools", and compare the two counts against the tool table on /docs.
The install command is clipped inside the docs code block
On /docs, in the "Give the work to your coding agent" code block, the third line of the install snippet extends past the block's right edge and is cut off mid-token at "<absolut", with no horizontal scrollbar or wrapping to reach the rest. The first two lines fit, so only the longest command is truncated. The remainder of that command cannot be read or copied from the rendered page.
Docs install commands are cut off on mobile
On /docs at a 390px viewport, the install code block clips all three command lines at the right edge of its rounded panel. The lines end mid-token ("the regist", "tofu-agen", "https://app."), and no scrollbar or other affordance signals that more text exists to the right. The commands include the TOFU_URL value and the agent invocation, so the copy shown on screen is incomplete.
A red line strikes through every stack row
On the mobile home page, in the "What you'd wire up yourself, list prices" comparison list, a red strikethrough rule runs the full width of each row instead of covering only the price. In the Supabase row it starts at the left edge of the card, crosses the green service icon, and cuts through the "Supabase" and "Database" labels before reaching "$25/mo". The same full-width rule appears on the Vercel, Clerk, Resend, GitHub and Analytics rows, and it also overruns past the right edge of the price on several of them.
The Cross-Origin-Resource-Policy header is missing
The response from https://trytofu.ai/ is missing Cross-Origin-Resource-Policy.
Small grey labels fall below the contrast minimum
Several 10.5px grey labels on the landing page sit below the WCAG AA contrast minimum of 4.5:1. The hero helper text "or paste this into your agent" measures 3.85:1 (#767c8e on #f5f6f9), the comparison heading "What you'd wire up yourself · list prices" measures 3.91:1 (#767c8e on #f7f8fa), and service sublabels such as "Hosting" in the pricing grid measure 4.16:1 (#767c8e on #ffffff).
Inline links are set apart only by color
Inline links inside body paragraphs on /features, /docs, /terms and /privacy carry no underline or other non-color styling, so color alone marks them as links. This maps to WCAG 2.0 A, success criterion 1.4.1.
Code blocks on /docs cannot be scrolled by keyboard
On /docs, the setup command block in the "Give the work to your coding agent" section (section:nth-child(2) > .project-module__H4hNEG__prose > pre) scrolls horizontally but is neither focusable nor contains focusable content, so a keyboard user cannot reach the clipped text. The block's third line runs past the right edge at "codex mcp add tofu --env TOFU_URL=https://app.trytofu.ai --env TOFU_CLIENT=codex -- <absolute-node> <absolut...".
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 fixedFree 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.
Enter an address and we will email the report card link.