Overall Score
Dashwall is a sharp, focused pre-launch landing page with solid design fundamentals and compelling messaging, but it's hemorrhaging SEO value and performance—like a startup that looks good in the pitch deck but hasn't optimized the engine room.
The Roast
Dashwall's got the vibes of a premium SaaS product: sleek dark hero, snappy copy, crisp CTAs everywhere. But here's the thing—they're scoring a flat 0 on SEO despite having decent content structure, which means Google's basically ignoring them. It's like building a Ferrari with no transmission: beautiful to look at, goes absolutely nowhere. The LCP is chunky at nearly 5 seconds, there's 83ms of total blocking time, and they're hauling unused JavaScript like a hoarder. They nailed the waitlist hustle, but they're optimizing for *vibes* instead of *visibility*.
🎯 Start Here
Google PageSpeed Insights
(Real metrics from Google)These scores come directly from Google's PageSpeed API. The AI scores above evaluate broader aspects like copy, trust signals, and conversion.
Core Web Vitals
SEO
Trust Signals
Performance
Accessibility
Conversion
Mobile
Design & UX
Copy & Messaging
SEO
SEO score is a catastrophic 0 despite solid on-page fundamentals (schema markup, semantic HTML, 1554 words)—the real killer is likely missing indexability signals, no external backlinks, or canonical/robots.txt issues that are blocking Google entirely.
Issues Found
- Zero external links on the entire page (23 internal links, 0 external) suggests either aggressive link pruning or a robots.txt/robots meta tag blocking external crawls—unusual for a pre-launch product trying to build buzz
- Schema markup present (Organization, WebSite, SoftwareApplication) but no review/rating schema, product schema breadth, or FAQ schema for the accordion—missed rich snippet opportunities
- No visible meta tags or open graph optimization beyond basic title/description; no canonical tag documented in crawl data (though it should exist)
Recommendations
-
Audit robots.txt and meta robots directives high
Verify the site isn't accidentally noindexed or disallowed from Googlebot—a 0 SEO score suggests a technical blocker.
-
Add FAQ schema to accordion high
Implement FAQPage schema markup with Question/Answer pairs to enable rich snippets in SERP.
-
Build strategic external links medium
Add 5–10 contextual external links to relevant resources (e.g., 'webhook documentation,' 'KPI best practices,' industry reports) to improve domain authority and topical relevance.
Trust Signals
Almost no visible trust signals on the page—no testimonials, user count, press mentions, or security badges—which is risky even for a pre-launch product trying to build hype.
Issues Found
- No visible testimonials, case studies, or beta user quotes—'Now in pre-launch' is a trust *question*, not a trust *answer*
- No user count, company logos, or 'built by' credentials (e.g., 'Built by ex-Datadog engineers')—missing founder/team credibility markers
- Privacy policy linked but no security badges, data hosting info, or SOC 2 roadmap visible—enterprise buyers will ask these questions
Recommendations
-
Add beta user testimonials or press mentions high
Include 1–2 quotes from early testers or a press mention (e.g., 'Featured in TechCrunch') to build social proof.
-
Highlight founder/team credentials medium
Add a small 'About' section or footer callout with founding team backgrounds (e.g., 'Built by engineers from Zapier and Figma').
-
Add security & privacy reassurance medium
Include a line in footer about data hosting (e.g., 'Hosted on AWS EU') or a roadmap link for SOC 2 compliance.
Performance
PageSpeed mobile performance is a respectable 80, but Core Web Vitals are soft disasters: LCP is nearly 5 seconds (target: <2.5s), TBT is 83ms (target: <50ms), and unused JavaScript is dragging the page down like dead weight.
Issues Found
- LCP of 4.991s is well above Google's 'Good' threshold (2.5s); likely caused by large hero image, render-blocking resources, or lazy-load failure on primary content
- Total Blocking Time (TBT) of 83ms exceeds Web Vitals 'Good' threshold (50ms), indicating heavy main-thread work during interaction window—probably third-party scripts (analytics, chat, forms) firing synchronously
- Unused JavaScript flagged in recommendations suggests bundle bloat; no code-splitting or dynamic imports visible in crawl data
Recommendations
-
Optimize and lazy-load hero image/dashboard preview high
Convert dashboard card to a low-resolution placeholder with blur-up effect, or serve a static image with conditional JS loading to reduce LCP.
-
Defer non-critical third-party scripts high
Move analytics (GA, Segment, Fullstory if present) and chat widgets to load after user interaction, not on page init.
-
Audit and tree-shake unused JavaScript medium
Run webpack-bundle-analyzer or similar to identify dead code; remove unused polyfills, libraries, or CSS-in-JS overhead.
Accessibility
Decent ARIA coverage (76 attributes) and solid form handling (15 inputs, all labeled), but the absence of a skip link is a red flag, and the dark navy hero likely has contrast issues in certain contexts.
Issues Found
- No skip-to-main-content link detected—users with keyboard navigation must tab through 6+ nav items before reaching main content
- Dark navy (#001a3a estimated) on hero section with white text may pass WCAG AA but CMS forms and input fields use lighter backgrounds that could fail contrast checks at smaller sizes
- Cookie consent banner uses blue buttons on default browser style; not all users will perceive button state clearly if color-blind (rely on shape/text, not color alone)
Recommendations
-
Add skip-to-main-content link high
Insert a visibly hidden skip link at top of page (visible on focus) that jumps to main content container.
-
Validate color contrast ratios medium
Run WAVE or Axe DevTools to confirm all text/button combinations meet WCAG AA (4.5:1 for body, 3:1 for large text).
-
Add focus indicators and keyboard navigation hints medium
Ensure all interactive elements have visible :focus-visible states; consider adding a focus indicator style guide for forms.
Conversion
Waitlist CTA is persistent, well-placed (sticky header + hero + bottom CTA), and forms are clean—but the conversion funnel lacks urgency drivers, social proof, and confidence-building signals that would push fence-sitters over the edge.
Issues Found
- No visible social proof on page (testimonials, user count, company logos, press mentions not visible in screenshots)—pre-launch product but could highlight early adopters or beta testers
- CTA copy doesn't vary by context; 'Join the waitlist' appears identically in header sticky nav, hero form, and footer—missed opportunity for contextual urgency ('Join now—limited spots' or 'Get early access')
- Form lacks confidence signals (no privacy assurance badge, no 'no spam' guarantee visible above fold on mobile)
Recommendations
-
Add social proof block high
Include beta user count, press mentions, or early adopter logos in a dedicated section above the fold (or below hero) to build credibility.
-
Contextualize CTA messaging medium
Vary CTA copy by placement: header = 'Get early access', hero = 'Join the waitlist—launch Q1', footer = 'Be first to know'.
-
Add trust markers to form low
Add a small icon + text ('No spam. Privacy first.' or similar) near the form to reduce friction.
Mobile
Mobile layout is responsive and readable; CTAs and forms are touch-friendly with adequate sizing—but the hero takes up nearly 100% of viewport on small screens, burying the value prop and causing scroll friction.
Issues Found
- Hero section is vertically stacked but still too tall on mobile (estimated 50–60% of viewport); users don't see copy + CTA without scrolling, reducing immediate engagement
- Dashboard preview card is not visible on mobile at all (likely hidden via media query), which means mobile users don't see the product demo until deep scroll—lost trust-building moment
- Input fields use 'you@company.com' placeholder text which is smaller than body text; could be harder to read for users with low vision
Recommendations
-
Compress hero on mobile high
Reduce hero height to ~35–40% of viewport on mobile (375px–425px max) so copy and CTA are visible without scrolling.
-
Show mobile-optimized product preview medium
Replace the desktop dashboard card with a mobile-friendly version (stacked, smaller) or a static screenshot with transparent overlay CTA.
-
Increase placeholder text size and contrast low
Use larger, higher-contrast placeholder text; consider using labels instead of relying on placeholder alone.
Design & UX
Clean, modern design with excellent visual hierarchy, strong contrast, and purposeful use of space—but the dark navy hero, while striking, dominates so heavily that secondary content feels buried beneath an avalanche of cool.
Issues Found
- Hero section is visually dominant but content-dense, pushing key messaging below fold on mobile (users see the dashboard preview before understanding the value prop)
- The dashboard demo card on desktop is right-aligned and competes with left-aligned copy for attention, creating unclear focal point hierarchy
- Feature cards in the 'Everything you need' section lack visual hierarchy markers (no icons on desktop version visible, inconsistent visual weight)
Recommendations
-
Reduce hero visual weight on mobile high
Shrink or collapse the dashboard preview on mobile to push the value prop and CTA higher without scrolling.
-
Establish clearer content hierarchy with icons/visual cues medium
Add consistent iconography to feature cards to help users scan and process benefits faster.
-
Improve mobile spacing and readability medium
Increase padding and line-height in body copy on mobile (currently feels cramped at 375px).
Copy & Messaging
Copy is punchy, problem-focused, and action-oriented—'Your best numbers are hidden in a tab nobody opens' cuts through the noise brilliantly, and the three-step onboarding narrative is immediately clear.
Issues Found
- Meta description is identical to H1 and value prop—missed opportunity for search diversity or nuance at 158 chars (could expand to use the full 160-character envelope)
- CTA microcopy 'Join the waitlist' is functional but lacks urgency or exclusivity messaging (compare to 'Be first to know' tagline above it)
- FAQ section headings are questions but don't hint at answers, reducing scanability (e.g., 'Is Dashwall live yet?' gives no preview of status)
Recommendations
-
Craft distinct meta description medium
Rewrite meta description to highlight a unique benefit or differentiator, not just repeat the H1.
-
Add urgency to CTA microcopy low
Change 'Join the waitlist' to 'Join the waitlist—early access' or 'Get early access' to increase perceived exclusivity.
-
Make FAQ answers visible in headers low
Add answer previews to FAQ headers (e.g., 'Is Dashwall live yet? — Launching Q1 2024') to aid scanning.
Think you can beat 66/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.