We found 4 issuescosting you truston co-found.site.
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.
Berlin and San Francisco pages show the same founder profiles
Founders who arrive on a city page looking for a local partner find the same profiles listed in every city, so they have reason to doubt the members are real before they sign up.
/co-founders/berlin and /co-founders/san-francisco show the same cards, word for word. Each has the same role, rating and bio, for example "L. N. Founder, Backend Developer, 4.9 (14 vouches), Building an open-source analytics platform", and only the location label changes from Berlin to San Francisco. Below the cards, each page says "Hundreds more founders in [city] are waiting", but a guest search for Berlin on /discover shows "Nobody here yet". A buyer meets this at the signup decision.
Try it: Open /co-founders/berlin and /co-founders/san-francisco in two tabs and compare the bios on the cards. Then search Berlin on /discover.
The home page offers a free try of the Prenup that pricing lists as Pro-only
Visitors who join free to try the AI Startup Prenup find out only after signing up that pricing lists it as a Pro feature.
The home page section "Your AI Startup Prenup, drafted in seconds." has a "Try it with your co-founder" button that opens the free signup at /auth?mode=signup. Nothing in that section says the feature costs money. The FAQ "Is Co-Found free to use?" names only profiles, browsing, connecting, team chat and Sunday Live as free, and /pricing lists "AI Startup Prenup" only under Pro, so a visitor at the signup step is not told that the feature they came to try is on a paid plan.
Try it: On the home page, find "Try it with your co-founder" in the Prenup section and click it. You land on the free signup. Then open /pricing and check that the Prenup appears only in the Pro feature list.
Deluxe yearly saves about 13%, not the "Save ~25%" the toggle claims
Buyers comparing billing periods for Deluxe find a smaller saving than the toggle promises, and the Early Founder discount disappears when they switch to yearly.
The billing toggle on /pricing reads "Yearly Save ~25%". Deluxe monthly is "$19 $9.50 / month · Early Founder price", which comes to $114 a year, but Deluxe yearly is "$99 / year", a saving of about 13%, and the yearly card drops the Early Founder line while Pro yearly keeps "50% OFF FOR LIFE". A buyer picking a plan at the pricing step gets a savings claim that does not hold for the top plan.
Try it: Open /pricing and note the Deluxe monthly price. Then click "Yearly Save ~25%" and compare $99 against 12 × $9.50.
Guest searches on Discover say "Nobody here yet" when members exist
Guests checking whether Co-Found has a co-founder in their city or skill are told nobody is there, which gives them a reason not to join.
Logged-out visitors on /discover see 6 profile cards, with no total count, no "load more" and no note that joining shows more members. A search for "Berlin" or "Developer" searches only those 6 and returns "Nobody here yet", even though developers such as Sona Badalyan (Developer, Full-stack Developer, active yesterday) have public profiles and show up in the Community pulse panel on the same page. This is the try step, where a guest decides whether the community is worth signing up for, and the empty result also tells a guest to "Complete your profile".
Try it: Open co-found.project/discover in a private window and search "Developer". Compare the results with /profile/9042ab0e-8d4c-4405-bbee-1baf75e51439, a public profile with Developer skills that the results leave out.
A home page nav button took 832ms to respond to a click
On the home page, one click on the button at nav.flex.flex-wrap.gap-5>button took 832ms to paint a response on desktop. Google rates Interaction to Next Paint above 500ms as poor. A second load did not show the same delay.
The Help button on /auth took 1.3 seconds to respond
On /auth, clicking the floating Help button in the bottom right corner took 1328ms to paint a response on desktop. Google classes anything above 500ms as poor. A second load did not show the same delay, and the signup form controls themselves were not the slow interaction.
Founder avatar links on /launches are too small to tap reliably
On /launches at phone width, the overlapping founder avatar links, such as "Co-Found Admin" and "Leo Marchetti", have a visible tap area of 16px by 24px. The clear space around each one is only 8px across, and the minimum is 24px. A visitor who taps one face in the stack can open the wrong founder's profile.
Home page avatars ship as 816px files but display at 32px
The member avatars in the home page hero (member-leo, member-aisha, member-sofia) are 816x816 files displayed at 32x32 at a device pixel ratio of 1, with transfer sizes of 65,574, 86,660 and 86,643 bytes. The Mira Solberg match preview photo is also an 816px file, displayed at 56x56. None of these images is the LCP element.
The home page lacks CSP, frame protection and CORP headers
The response from https://co-found.site/ is missing Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, and Cross-Origin-Resource-Policy.
The "96% fit" match badge is near-black text on dark teal
The "96% fit" badge in the home page match preview sets #0b0b1a text on a #1b4049 background, a contrast ratio of 1.74 where 4.5 is required. The red "New" tag on the Launches nav link is at 4.13 and uses 9px bold text. The same rule also fails on /auth and /discover.
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.