We found 2 issuescosting you truston thisandthat.chat.
The English and Portuguese pricing pages disagree on who is billed.
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 English and Portuguese pricing pages disagree on who is billed
Portuguese-speaking teams counting seats are told that teammates who never connect a mailbox are not billed, and the English page says the opposite.
The English /pricing/ FAQ says a user is anyone with their own this+that account "whether or not they have connected a mailbox or a messaging account". The /pt-br/pricing/ FAQ says a user is "Qualquer pessoa com a própria conta this+that que conecte o e-mail ou as mensagens dela", so only people who connect their email or messages count. Buyers sizing a per-seat plan at the pricing step get a different seat count depending on the language they read. The PT-BR page also leaves out the English FAQ entry on removing teammates, and it lists Team in R$ next to Enterprise "A partir de US$ 125".
Try it: Open /pricing/ and /pt-br/pricing/, scroll to the FAQ, and compare "Who counts as a user?" with "Quem conta como usuário?".
The credits page says "Examples of costs are coming" and lists no prices
Buyers who need a per-seat budget for the $35 Team plan cannot find out how far 3,000 credits go or what extra credits cost.
The Pricing page offers the Team plan with 3,000 credits per user each month and says you can top up at any time. Its "How credits work" link goes to /credits/, and that page's "What a credit buys" section ends with "Examples of costs are coming." Neither /credits/ nor the Pricing FAQ gives a cost per action or a top-up price, so a buyer at the pricing step cannot work out what a seat will really cost.
Try it: Open /pricing/, click "How credits work", and read the "What a credit buys" section on /credits/ to its end. Then look on that page and in the Pricing FAQ for any top-up price.
The home page lacks Referrer-Policy and CORP headers
The response from https://www.thisandthat.chat/ is missing Referrer-Policy and Cross-Origin-Resource-Policy.
Grey section text on the home page falls just short of contrast
The paragraph under "Workflows and the brain make each other smarter" on / and /brain/ is #6b7280 on #f3f4f6, a contrast of 4.39:1 against the required 4.5:1. The same colour pair also applies to the "Supported by" label and the small "v7" tag. The text stays legible, but low-vision readers get fainter copy on the page that explains the product.
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.