FindOutMy Review: Useful tools, weak experience (61/100)

FindOutMy is a free AI photo-analysis site reviewed from its public surface.

Field	Value
Domain	findoutmy.com
Category	AI photo analysis tools for body, style, and age
Pricing	Free CTAs are present; pricing and limits are not clearly explained
Pages crawled	40
Crawl date	2026-09-28

FindOutMy earns a 61/100 overall score because solid technical foundations sit alongside a weak user experience. Accessibility scores 85/100, and technical SEO scores 86/100: the 40-page partial crawl found sampled public URLs returning 200, self-referencing canonicals, an allowed public surface, a declared sitemap, HTTPS, and host consistency. Risk and stability also scores 86/100.

The largest drag is performance at 35/100. On mobile, the homepage's LCP is 2.3 seconds, while the supplied performance evidence also records CLS 0.5, a 10,920-byte logo, 8 blocking requests, and TTFB of 186ms. Design execution scores 58/100, with contrast, tap-target, horizontal-scroll, and component-consistency issues. Messaging is also underdeveloped: audience and onboarding guidance are unclear, and key questions about pricing, trust, and error handling remain unanswered. Writing quality scores 52/100 because sampled pages present roughly 1,800–2,600 words as single paragraphs.

The result is a site with credible crawl and accessibility basics, but too much friction between the promise of photo analysis and a confident first use.

FindOutMy presents AI photo analysis for age, style, and body feedback, but its first promise does not make the product or audience specific. The homepage H1, ‘Upload a photo. Let AI find out.’, names an action without a distinctive outcome, named segment, or proof point. The crawl found no testimonials, customer metrics, case studies, comparison pages, pricing tiers, or free-trial explanation. That leaves a prospective user to infer who the tools are for and why the result deserves trust. Rewrite the hero around a named primary audience and a concrete outcome, then support it with verifiable user evidence and a clearer explanation of how to start.

FindOutMy’s messaging leaves the central buying questions unresolved: what it costs, whether it can be trusted, how to begin, and what happens when a tool fails. The crawled site has no pricing page, trial or subscription tiers, named testimonials, case studies, step-by-step guide, support page, cancellation or refund guidance, or SLA. Tool CTAs use ‘Free’, but that is not a complete explanation of cost or limits. The only onboarding instruction is ‘Upload a photo’, and the audience hint ‘Made for curious people, not judgment’ does not define a usable segment. Add a pricing page, a three-to-five-step ‘How It Works’ path, named proof, and explicit support and error guidance. These additions would reduce uncertainty before the upload step.

Accessibility is largely compliant: the crawl reports a skip link and consistent navigation. Two sampled pages contain an image with an empty alt attribute: the face-shape detector and AI palm-reading pages. Empty alt is correct for decorative imagery, so the fix is to confirm intent and add concise descriptions only where the image conveys information. The supplied PSI evidence also reports contrast failures on the rate-my-body and AI palm-reading pages, but it does not identify the affected text or background; that gap should be verified before making a specific contrast claim. Run a targeted accessibility audit, classify the two images, and document any confirmed contrast corrections.

Design execution is held back by measurable contrast, touch, mobile-layout, and consistency defects. Body text on white is #9CA3AF at a 2.8:1 ratio, below the 4.5:1 text requirement; form borders measure about 1.5:1, below the 3:1 UI threshold. The sampled ‘Rate My Body’ button is 38×20px, inputs use 14px text, and the page scrolls horizontally at a 390px viewport. Buttons also mix pill and rounded-rectangle radii. Darken text and borders, bring controls to at least 44px, raise input text to 16px, constrain mobile content, and standardize component tokens for radius, padding, and type.

Performance is the clearest technical drag: the homepage's mobile time to interactive is 7.7 seconds, while LCP is reported in the performance audit and CLS is 0.5. The LCP element is the 10,920-byte logo image, rendered at 152px from a 760px-wide source without preload; missing image dimensions also produce layout shifts, including a 160×160px avatar rendered at 24×24px. The page has 8 blocking requests, including Google Tag Manager and AdSense, while TTFB is 186ms. Resize or serve the logo appropriately, reserve image space with explicit dimensions, and load blocking third-party scripts asynchronously. Verify the resulting interaction and layout metrics after each change.

FindOutMy’s tool names are concrete, but the rendered editorial structure makes the explanations hard to scan. On Rate My Body, the N1 statistics report 2,031 words with paragraph_count 1, and the same one-paragraph pattern appears across sampled tool pages. The homepage extraction also repeats navigation labels and tool links inside the page content, adding noise to the reading path. Restore paragraph boundaries and the descriptive H2 structure so requirements, limitations, and results can be found quickly. Then remove duplicated navigation from the main-content rendering, fix the reported image-alt issues, and shorten the 80-character Style & Fashion title. Because the crawl is partial and language detection is inconsistent on several English pages, this verdict stays focused on structure rather than lexical style.

FindOutMy shows no confirmed sitewide traffic-suppression defect in the supplied evidence. Robots.txt allows the public surface, HTTPS and www redirects are single-hop 301s, the nonexistent probe returns 404, and the 40 sampled pages have matching raw and rendered word counts. The specific resilience risk is URL duplication around rate-my-body: both slashed and non-slashed forms appear in the inventory, while the canonical and sitemap use the slashed form. Standardize all internal references and ensure the alternate resolves consistently. Measurement confidence is limited because Search Console is unavailable; Wayback provides four sampled snapshots from 2013 and 2021, while RDAP records registration on 2026-08-06. Connect Search Console and analytics before drawing traffic or indexing conclusions.

The sampled technical SEO foundation is strong: all 40 crawled URLs return 200, canonicals are self-referencing, robots.txt allows the public surface, the sitemap is declared, HTTPS and www consolidation use single-hop 301 redirects, and raw-versus-rendered word counts match. The main cleanup is URL consistency: the non-slashed rate-my-body URL is duplicated in the inventory even though the canonical and sitemap use the slashed form. The issue table also reports one missing alt attribute on multiple tool pages and category titles from 68 to 80 characters, including the 80-character Style & Fashion title. Use one permanent URL form in links, add meaningful alt text where imagery is informative, and shorten the longest titles. This remains a partial crawl, so unobserved pages are outside the finding set.

The site implies a B2C audience, but it does not define a named segment; its source copy includes the phrase ‘Made for curious people, not judgment’. Its strongest work is structural: accessibility scores 85/100, technical SEO scores 86/100, and risk and stability scores 86/100.

The fixable weaknesses are clear. First, mobile performance is weak, with LCP 2.3 seconds and CLS 0.5. Second, the product needs sharper communication around audience, pricing, trust, onboarding, and errors. Third, the visual and editorial presentation needs more usable hierarchy, including stronger contrast, larger tap targets, less horizontal scrolling, and more readable page structure.

The core opportunity is to make the first-use experience as dependable and understandable as the underlying technical foundation.

This is a 13-dimension review based on a 40-page crawl completed on 2026-09-28. The article uses the public score table and its one-line findings; scores are rounded to the persisted article value of 61/100.

The review excludes 03 · Usability, 12 · Decision-support surfaces, and 13 · Review-content integrity because they were marked not applicable. Google Search Console was not connected, so no Search Console enrichment is included.

Read the full SiteList methodology for the scoring framework and data notes.