57/100
Better than 48% of sites we have audited
50–59 · More working than not — Much of what we measure is holding up. What's left tends to be a handful of things rather than everything.
162 sites audited. Median 57, and the top 10% start at 72. Most land in the 60s.
"Solin has a genuinely exciting core product and crisp copy — nail the social proof gap and fix the mobile LCP and you have a page that could convert at 2–3×."
Scores and fixes by category
Weakest categories are open. The score and its reasoning are the AI's reading; the fixes underneath come from checks we ran against your page.
› Value Prop 20% of score 72
The core benefit — AI audio feedback on your speaking in 60 seconds — is clear and specific within the first two sentences, which is genuinely strong for an early-stage product.
› Trust 20% of score 4 fixes 12
Zero testimonials, zero user count, zero logos, no about page, no privacy policy link — every trust check failed; the only saving grace is the 'free forever, no credit card' risk reversal.
Generic "trusted by" claims aren't trust — named testimonials with real attribution are. Anonymous quotes read as marketing copy.
Do this: Add at least one testimonial with real attribution (full name plus role or company). A single specific, outcome-focused quote outperforms a grid of generic ones.
Industry benchmark: +34% conversions — Nielsen
Every additional second of load time measurably increases bounce rate — 1s→3s nearly doubles it.
Do this: Compress images, enable HTTP/2 or HTTP/3, add CDN caching, and remove unused JS/CSS.
Industry benchmark: -32% (1s→3s load) bounce rate — Google
Buyers check who is behind a product before they trust it with work or money. No visible team reads as either very early or deliberately anonymous.
Do this: Link an About or team page from the main navigation, with real names and faces. For a solo product, say so plainly — that is a story, not a weakness.
A missing privacy link is a trust signal in the wrong direction, and it blocks you outright in regulated markets and on app stores.
Do this: Link a privacy policy from the footer. If you collect anything at all, this is table stakes rather than an optional extra.
› Design / UX 13% of score 74
All 6 design/UX automated checks passed, mobile-friendly, fast server response, and the page structure is clean and scannable — solid foundation for a v1.
› Copy 12% of score 68
Copy is punchy and benefit-focused ('watch your confidence skyrocket', '60 seconds'), the free-forever offer is clearly stated, but 126 words total is too thin to handle objections or build narrative momentum.
› CTA 15% of score 82
'Sign Up with Google' is a zero-friction OAuth flow clearly labeled free with 'Free forever for personal practice • No credit card required' right below it — that's a strong conversion pattern executed well.
› Technical 10% of score 1 fix 45
Mobile LCP of 3,847ms fails the 2.5s threshold, unused JS flags 900ms savings, robots.txt and sitemap are missing, and the viewport accessibility issue costs points — though server response and desktop performance are solid.
LCP over 2.5s means visitors stare at a loading skeleton during peak buying intent. Most abandon before it finishes.
Do this: Preload the hero image, serve it as WebP/AVIF, remove render-blocking scripts, and upgrade to a fast CDN.
Industry benchmark: +7% per 100ms faster conversions — Google Web Vitals
› Differentiation 5% of score 55
'AI-powered + audio analysis + 60-second prompts' is a specific and differentiating angle, but the page doesn't explicitly compare itself to alternatives like Toastmasters or generic speaking apps.
› Emotional 5% of score 50
'Watch your confidence skyrocket' and 'speak with impact' tap into real aspiration, but there are no real human stories or relatable struggle moments to make it land emotionally.
Technical Analysis
Agentic Browsing
New Google · experimentalCan an AI agent read and use this page? ChatGPT, Claude and Perplexity increasingly visit sites on someone's behalf — this is Google's new Lighthouse check for whether yours is usable when they do.
- ✓ Accessibility tree is well-formed — All audits passed
- ✓ Cumulative Layout Shift — 0
- ✗ llms.txt does not follow recommendations File is missing a required H1 header (e.g., "# Title"). File does not appear to contain any links.
Scored by Google and reported alongside your roast, not folded into it. The category is still changing.
Core Web Vitals
How long until your main content (hero image, headline) shows up. Slow = visitors bounce before they see what you offer.
How much your page jumps around while loading. Jumpy pages feel broken and cause accidental taps on the wrong thing.
How long until anything appears on screen. A blank white page for 3+ seconds loses impatient visitors instantly.
How fast your page responds when someone clicks or taps. Slow response feels broken — people click again thinking it failed.
How fast your hosting server starts sending the page. Slow TTFB means the problem is your hosting, not your images or design.
How long until your main content (hero image, headline) shows up. Slow = visitors bounce before they see what you offer.
How much your page jumps around while loading. Jumpy pages feel broken and cause accidental taps on the wrong thing.
How long until anything appears on screen. A blank white page for 3+ seconds loses impatient visitors instantly.
How fast your page responds when someone clicks or taps. Slow response feels broken — people click again thinking it failed.
How fast your hosting server starts sending the page. Slow TTFB means the problem is your hosting, not your images or design.
Top Speed Opportunities (Mobile)
- Reduce unused JavaScript
- −900ms
- Initial server response time was short
- −2ms
Technical SEO Files
These files tell search engines and AI crawlers how to read your site. Missing ones mean less organic traffic.
- robots.txt not found (HTTP 307) - search engines can't see your crawl preferences
- No sitemap.xml found - search engines may miss pages
- No llms.txt found - consider adding one to guide AI crawlers (emerging best practice)
- No security.txt found - good practice to help security researchers
Accessibility (WCAG 2.1 static audit)
How usable your page is for visitors with disabilities (~15% of users). Low score = lost customers and legal exposure.
-
meta-viewport-scale major
Viewport restricts maximum zoom (maximum-scale ≤ 1). Low-vision users need to zoom.
1.4.4
-
skip-nav minor
No skip navigation link found. Keyboard users must tab through all nav links to reach content.
2.4.1
-
landmark-regions minor
Missing landmark region(s): navigation. Landmarks help screen reader users navigate.
1.3.1
Tech Stack Measured
What your site is built with. Matters because your CMS/framework/hosting choice caps how fast you can fix things and what optimizations are even possible.
Page Structure
- Hero
- Good
- Headline
- Good
- Subheadline
- Good
- CTA
- Good
- Social Proof
- Missing
- Features
- Good
- Pricing
- Missing
- FAQ
- Missing
- Footer
- Weak
What Works
- The 'Free forever for personal practice • No credit card required' line directly below the CTA is excellent risk reversal — it removes the #1 objection before visitors even ask it.
- The 60-second practice format is a concrete, differentiating mechanism that immediately answers 'what do I actually DO here?' — most EdTech apps never answer that above the fold.
- Page load is 473ms server-side with a 2ms server response time — the backend is fast, and the Next.js stack is well-deployed; this is a solid technical foundation to build on.
- The three features (Targeted Practice, In-Depth Audio Analysis, Personalized Coaching) are clearly named and cover the full coaching loop — they tell a coherent product story.
What Doesn't
-
Critical
Zero social proof — no testimonials, no user count, no logos, nothing. You're asking strangers to hand over their Google account on pure faith. The social proof score is literally 0/4. Even a single real quote from a beta user would double your trust signal overnight.
Fix: Add a section with 3–5 real beta-user testimonials (name, role, specific outcome like 'dropped filler words by 40% in 2 weeks'). If you don't have testimonials yet, add a '[X] speakers trained' counter once you have a real number, and a link to your About page or founder story.
-
Major
No FAQ means every silent objection kills the conversion. Visitors wondering 'will my recordings be stored?' or 'what happens when I hit the free tier limit?' have nowhere to get answers except their own imagination — which is almost always pessimistic.
Fix: Add a visible FAQ section answering: 'Is my audio stored?' 'How is this different from YouTube tutorials?' 'What happens after the free tier?' 'How long until I see improvement?' These objections are silent conversion killers right now.
-
Major
No pricing section means visitors can't evaluate the offer. 'Free forever for personal practice' is in the subheadline, which is great — but there's no ceiling defined. What does 'free forever' actually cover? The absence creates anxiety, not excitement.
Fix: Add a brief pricing or 'what's free vs. paid' section. Even a simple 3-column table (Free / Pro / Team) with feature checkmarks and a price gives people a mental anchor and removes the fear of hidden costs.
-
Major
Missing robots.txt, sitemap.xml, and no privacy policy link in the footer. Google can't crawl you efficiently, your SEO baseline is broken, and the missing privacy policy is a legal and trust risk — especially for an app that records users' voices.
Fix: Add a robots.txt, sitemap.xml, and a privacy policy link in the footer. These are 30-minute tasks in a Next.js project. robots.txt can be a single static file in /public, sitemap can use next-sitemap, and the privacy policy protects you legally.
-
Major
Mobile LCP is 3,847ms — nearly 4 seconds before the main content paints on mobile. Lighthouse flags 900ms of unused JavaScript as the culprit. For a speech training app, first impressions on mobile matter enormously. Slow = untrustworthy.
Fix: Audit your JavaScript bundle with Next.js Bundle Analyzer. Look for heavy libraries loaded on the homepage that aren't needed for initial render. Code-split them with dynamic imports. Target Mobile LCP under 2.5s to hit Google's 'Good' threshold.
-
Minor
The viewport meta tag sets maximum-scale=1, which locks out zoom for visually impaired users. This is flagged as a major accessibility issue (score 86/100) and could expose you to accessibility complaints while hurting your SEO.
Fix: Fix the meta viewport tag: remove 'maximum-scale=1'. This prevents users from zooming in on your content, which is an accessibility violation. In your Next.js layout, change the viewport meta to: initial-scale=1 with no maximum-scale restriction.
Suggested Rewrites AI reading
Speak sharper in 60 seconds a day — AI coaching for public speaking & interviews
Record a 60-second response and get instant AI feedback on filler words, pace (WPM), structure, and vocabulary — so every conversation makes you sharper.
Start Speaking Free — Sign Up with Google
Roast your own site