Overall Score
Dashwall has maintained its sleek design and sharp messaging but remains tragically invisible to Google—still scoring 0 on SEO with a bloated 3.5s LCP. The site looks premium but performs like it's running on a potato, and trust signals are still missing in action.
The Roast
Dashwall is that friend who shows up to the party looking absolutely flawless but can't find the door because there are no signs pointing to it. They've fixed nothing since the last roast—same 0 SEO score, same chunky performance, same missing external links that make Google question whether they exist. It's like they read the feedback, nodded thoughtfully, and decided to ignore every single word. Beautiful execution, zero discoverability, and still no social proof to convince anyone this product isn't vaporware.
🎯 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
Still a catastrophic SEO wasteland: 0 external links, no FAQ schema, missing review/rating schema, and zero organic discoverability despite solid content structure. It's like building a billboard in a forest with no roads.
Issues Found
- Zero external links (23 internal, 0 external) remains a red flag—no outbound links to credibility sources, integrations, or partner companies; suggests either aggressive link pruning or deliberate isolation from the web
- No FAQ schema markup despite 9-question accordion section—missing easy rich snippet wins for 'People also ask'
- No review schema, product schema depth, or structured data for pricing tiers, availability, or software application features beyond basic Organization/WebSite/SoftwareApplication tags
Recommendations
-
Add outbound links to credibility sources high
Link to Zapier, Make, or integrations you support; link to Geckboard (mentioned in footer) as a comparison; link to privacy tools. This signals you're not hiding and builds topical authority.
-
Implement FAQ schema markup high
Wrap accordion items in JSON-LD FAQPage schema so Google can surface your Q&A in 'People also ask' and search results.
-
Expand SoftwareApplication schema with pricing, reviews, offers medium
Add aggregateRating, review objects, and Offer details (free tier, paid tiers with pricing) to unlock rich snippet eligibility.
Trust Signals
Still barren. No testimonials, case studies, user count, company logos, or founder credibility markers visible—'Now in pre-launch' raises more questions than answers, and the footer-only 'hello@dashwall.io' and 'Made in the Netherlands' are insufficient to build enterprise trust.
Issues Found
- No testimonials, case studies, or beta user quotes visible—'pre-launch' status is defensible, but even one early adopter quote would signal traction
- No 'built by' founder credentials, team bios, or 'ex-[Datadog/Segment/Mixpanel]' credibility markers—nothing to establish founder/team authority
- No security badges (SOC 2, ISO 27001 roadmap), data hosting info, or privacy assurances beyond 'Privacy Policy' link—enterprise buyers will have compliance questions
Recommendations
-
Add early adopter testimonial or case study snippet high
Feature 1–2 beta user quotes or a lightweight case study ('Used by [Company] to track [metric]') near the CTA or features section.
-
Surface founder/team credibility medium
Add an 'About' or 'Team' page (linked in footer) showcasing founders with LinkedIn profiles, prior companies, and relevant expertise (e.g., 'Built by ex-Datadog engineers').
-
Publish security/compliance roadmap medium
Add a brief statement: 'SOC 2 Type II in progress. Data hosted on [AWS/GCP]. GDPR compliant.' Link to Privacy Policy and consider a security FAQ.
Performance
LCP has dropped slightly to 3.475s (was 4.991s)—improvement, but still well above the 2.5s 'Good' threshold; TBT (565ms!) is now 10x the acceptable limit, suggesting heavy third-party script blocking.
Issues Found
- LCP 3.475s is still 40% above Google's 'Good' threshold (2.5s); likely caused by lazy-loaded hero image or render-blocking resources firing synchronously
- TBT 565ms is catastrophic—nearly 6x the 50ms 'Good' threshold, indicating main-thread blocking from analytics, chat widgets, or forms executing synchronously during interaction window
- Unused JavaScript flagged but not addressed; no visible code-splitting, dynamic imports, or lazy-loading strategy documented
Recommendations
-
Defer non-critical JavaScript execution high
Move analytics, chat, and form validation scripts to load after interaction-window (use defer/async attributes), and consider loading third-party widgets like Intercom only on user interaction.
-
Optimize hero image delivery high
Serve WebP versions with srcset fallbacks, use native lazy-loading (loading='lazy') for below-fold images, and consider a lower-res placeholder during LCP.
-
Audit and remove unused JavaScript medium
Run bundle analysis (webpack-bundle-analyzer or similar) to identify dead code, unused dependencies, and polyfills; remove or dynamically import only when needed.
Accessibility
71 ARIA attributes is solid scaffolding, but no skip link, and form inputs likely fail color contrast checks at smaller sizes—dark navy backgrounds and light inputs create edge-case accessibility debt.
Issues Found
- No skip-to-main-content link detected—keyboard users must tab through 6+ nav items (Dashwall logo, How it works, Agents, Use cases, Pricing, FAQ, Blog, Log in, Start free) before reaching main content
- Cookie consent banner uses color-only differentiation for 'Accept' (blue) vs. 'Decline' (gray)—color-blind users may not perceive button state clearly; should use shape/icon/text contrast
- Input field placeholder text ('you@company.com') is smaller than body text and may fail contrast at low zoom; no visible label outside form on mobile
Recommendations
-
Add skip-to-main-content link high
Insert a keyboard-accessible skip link before the nav that jumps to the main content area on Tab/Enter; style it to appear on focus.
-
Improve button distinction in cookie banner medium
Add outline/border to 'Decline' button and ensure both buttons have sufficient color contrast (4.5:1 minimum); use icon or text weight to reinforce action.
-
Ensure form label visibility on mobile medium
Display visible labels for email input field (not just placeholder); increase placeholder text size to match body text for low-vision users.
Conversion
CTAs are well-placed (hero, sticky nav, mid-page, footer) and the form friction is low (just email)—but zero social proof, no testimonials, no beta user credentials, and identical CTA copy across all contexts kills contextual urgency.
Issues Found
- No visible social proof: no testimonials, case studies, user count, company logos, or 'built by' founder credentials—pre-launch status is acceptable, but no early adopter quotes or beta user credibility markers visible
- CTA microcopy 'Start free' is functional but lacks urgency or exclusivity ('Limited spots,' 'Be first to know,' 'Get early access')—especially weak for a product that's 'now live'
- No confidence signals above/below form: no 'no spam' guarantee, no privacy badge, no 'instant access' promise visible above fold on mobile
Recommendations
-
Add early adopter testimonials or case study snippet high
Include a single testimonial card or quote near the CTA ('Used by teams at [Company]' or a 1-2 sentence beta user quote) to build trust without heavy social proof design.
-
Vary CTA copy and add urgency medium
Hero: 'Start free—no card required,' Mid-page features: 'See how it works,' Footer: 'Get early access' to create contextual momentum and hint at limited availability.
-
Add micro-copy confidence signals medium
Place 'Free forever. No credit card. Instant setup.' or similar 3-line trust builder above the email form on desktop and mobile.
Mobile
Mobile nav is clean and the layout is properly stacked—but the hero section is vertically massive, pushing copy and CTA below fold, and the dashboard demo is entirely hidden until deep scroll.
Issues Found
- Hero section is ~50–60% of viewport height on mobile (estimated from screenshot); users don't see copy 'Dashwall shows your live business metrics...' or CTA without scrolling, reducing immediate engagement
- Dashboard preview card (Growth board) is completely hidden on mobile (media query display:none)—users never see the product until deep scroll, losing a critical trust-building moment
- Input field placeholder text is smaller than body text; no visible form label; form is squeezed between cookie banner and product copy, creating visual clutter on small screens
Recommendations
-
Reduce hero height and surface value prop above fold high
Trim hero to 40% viewport height max; ensure h1 + subheading + CTA button are visible without scroll on a 375px mobile screen.
-
Show compact dashboard preview on mobile high
Display a scaled or simplified version of the Growth board screenshot immediately below the hero CTA (not hidden) to establish product credibility early.
-
Improve form label and input visibility medium
Add explicit 'Email' label above input field, increase placeholder text size, and reduce vertical spacing between elements to prioritize form over cookie banner.
Design & UX
The dark hero with white typography is crisp and modern, and the dashboard demo card is visually compelling—but the layout still overwhelms mobile users with content-heavy sections and unclear focal point hierarchy on desktop.
Issues Found
- Feature cards lack visible icon differentiation on desktop—'Create a tile,' 'Send a value,' 'The wall updates' are text-only with subtle color indicators, reducing scannability
- Mobile hero section pushes the dashboard demo below the fold entirely, hiding the product visual until deep scroll—users on mobile never see what they're building
- FAQ section is un-annotated question text with no visual preview of answers, forcing users to expand each accordion blindly
Recommendations
-
Add visible icons to feature cards medium
Place consistent, prominent icons (folder, lightning bolt, monitor) above each 'Create a tile' / 'Send a value' / 'The wall updates' card to improve scannability and visual weight.
-
Surface dashboard preview on mobile high
Show a compact version of the Growth board demo on mobile hero (or immediately below) to establish product credibility before users scroll.
-
Add answer previews to FAQ headers low
Change 'Is Dashwall live yet?' to 'Is Dashwall live yet? Yes—available now' so users can scan answers without expanding.
Copy & Messaging
The headline 'Live KPIs on your office wall' is punchy and the value prop is clear and concrete (webhook integration, AI agents, sub-second updates)—but CTA copy remains generic and FAQ titles still don't hint at answers.
Issues Found
- CTA remains 'Start free' and 'Join the waitlist' across all sections—no contextual urgency or exclusivity ('Be first to know,' 'Get early access,' 'Limited spots')
- Meta description (158 chars) is identical to H1, missing the full 160-character envelope for search result differentiation
- FAQ questions are generic without answer previews ('Is Dashwall live yet?', 'What does it cost?') forcing blind clicks
Recommendations
-
Vary CTA copy by section medium
Use 'Get started free' in hero, 'See how it works' in features, and 'Start building' in footer to create contextual momentum without sounding spammy.
-
Expand meta description with unique angle low
Extend to 160 characters: 'Dashwall puts live KPIs on your office wall in <1 second. Push webhook values or use AI agents to auto-track metrics. Free plan, no card required.'
-
Add answer hints to FAQ headers low
Restructure as 'Is Dashwall live yet? Yes, launching now' so users can skim answers without expanding accordions.
Think you can beat 66/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.