Overall Score
Dashwall is a clean, modern SaaS site with solid fundamentals and excellent copy, but it's being sabotaged by sluggish performance, SEO handicaps, and mobile responsiveness issues that make it feel less polished than its product clearly deserves.
The Roast
Dashwall's website is like a luxury car with a broken speedometer—the design looks sleek, the messaging is sharp, but then you hit performance bottlenecks and realize the SEO score is literally zero. They're displaying live KPIs to offices worldwide, yet somehow their own page takes 5+ seconds to load and doesn't know what its own URL is. It's the irony that would make their dashboard weep in real time.
🎯 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
Performance
Trust Signals
Accessibility
Mobile
Conversion
Design & UX
Copy & Messaging
SEO
This is a disaster. SEO score is literally zero, meaning Google is probably seeing the site but has no idea what it does or where to rank it. The schema markup is solid and headings exist, but the actual SEO fundamentals are missing or broken in ways that make this look like a dev-only staging site.
Issues Found
- PageSpeed SEO score is 0/100—this typically indicates missing critical tags, poor crawlability, or rendering issues that prevent Google from parsing page content effectively
- URL structure is clean but no meta title/description optimization per page section (all sections reuse the same generic org schema)
- No visible H1-to-H2-to-H3 hierarchy enforcement; 24 H3s with only 1 H1 suggests heading tags are used for styling, not semantic structure
Recommendations
-
Audit and fix SEO rendering pipeline high
Run the site through Google Search Console, PageSpeed Insights, and Lighthouse; identify why SEO score is 0 (likely JS rendering, missing meta tags, or indexation blocks).
-
Implement per-section meta tags and schema high
Create unique page titles/descriptions for /pricing, /use-cases, /how-it-works; add schema.org markup for FAQPage (for the FAQ section) and Product schema for pricing tiers.
-
Restructure heading hierarchy medium
Ensure only 1 H1 per page, use H2 for major sections, and reserve H3-H4 for subsections; avoid using headings for styling (use CSS classes instead).
Performance
LCP of 5.2 seconds is painfully slow for a marketing site selling real-time dashboards—that's a cruel irony. TBT at 129ms suggests heavy JavaScript, and the PageSpeed mobile score of 78 masks critical issues hiding beneath the surface.
Issues Found
- LCP (Largest Contentful Paint) at 5.205s is well above the 2.5s 'good' threshold, likely caused by unoptimized hero imagery or render-blocking JavaScript
- TBT (Total Blocking Time) of 129ms indicates main-thread jank, suggesting bloated JS bundles, unminified code, or synchronous operations blocking user interaction
- Unused JavaScript flagged as a reducing factor—third-party scripts (analytics, trackers, vendor libs) are likely loaded on every page despite minimal usage
Recommendations
-
Optimize hero image and defer below-fold assets high
Convert dashboard mockup to WebP, lazy-load it, and defer CSS/JS for non-critical sections to improve LCP below 2.5s.
-
Audit and remove unused JavaScript high
Use Webpack Bundle Analyzer or similar tools to identify unused vendor code; tree-shake unused lodash/moment imports, lazy-load third-party trackers, and split critical vs. non-critical bundles.
-
Implement request-level caching and edge compression medium
Enable aggressive HTTP caching (max-age 1 year for assets with hashes), compress SVGs/JSON responses, and use a CDN to serve static assets from edge nodes.
Trust Signals
Trust signals are almost entirely absent—no testimonials, user counts, security badges, or third-party validation visible in the crawled data or screenshots. The site relies heavily on self-generated mockups and feature descriptions, with no external credibility markers to back claims.
Issues Found
- No visible customer testimonials, case studies, or logos anywhere in the captured screenshots (bottom sections not verified, but conspicuously absent from hero/mid-page areas)
- No security badges, GDPR/SOC2 compliance indicators, or privacy trust signals mentioned above fold; only generic 'Free plan, no credit card' reassurance
- Comparison page ('Dashwall vs Geckboard') exists in nav but may be positioning against outdated competitor; no mention of modern alternatives or market context
Recommendations
-
Add customer testimonials or logo wall high
Feature 3-5 short testimonials with avatars/roles or a 'Trusted by' logo carousel (even if just 5-10 recognizable company names) immediately below hero.
-
Display security and compliance badges medium
Add visible GDPR/CCPA compliance, SOC2 Type II (if applicable), or 'Trusted by Fortune 500' badges in footer or near sign-up CTA to reduce perceived risk.
-
Update competitive positioning with modern context medium
Ensure comparison pages reference current market alternatives (Databox, Klipboard, etc.); consider adding 'Why Dashwall' section with differentiators (real-time, AI agents, no install).
Accessibility
The site has decent ARIA coverage (71 attributes) and proper landmark structure (nav, main, footer), but no skip-to-content link, minimal keyboard navigation testing, and color contrast likely fails in several places (dark blue on darker blue in hero is risky).
Issues Found
- No skip link visible/documented—keyboard users can't jump directly to main content, forcing them to tab through entire nav menu on every page
- Dark-on-dark color scheme in hero (white text on navy background) may fail WCAG AA contrast on mobile where text renders smaller; no visible contrast ratios documented
- Cookie consent banner uses generic buttons ('Accept', 'Decline') with no clear focus management or keyboard trap prevention documented
Recommendations
-
Add and test skip-to-content link high
Implement a keyboard-accessible skip link (visible on :focus, hidden by default) that jumps to <main> element to pass WCAG 2.1 SC 2.4.1.
-
Audit color contrast on dark theme high
Run WAVE or Axe DevTools to verify all text meets WCAG AA (4.5:1) or AAA (7:1) on dark backgrounds; adjust hero text or background color if needed.
-
Document keyboard navigation and focus management medium
Test Tab/Shift+Tab through all interactive elements; ensure focus is visible, logical, and never trapped; document expected behavior for modal/cookie banner.
Mobile
Mobile layout is responsive and readable, but the experience feels cramped and cluttered—text is smaller than it should be, spacing is tight, and the cookie banner takes up ~30% of the viewport on initial load, creating friction before users even see the product.
Issues Found
- Cookie banner occupies excessive viewport height on mobile (3-4 lines + 2 buttons), pushing hero content below fold and blocking immediate value prop communication
- Hero text appears cramped and small (font size looks < 16px); readability suffers, particularly for older users or those on small phones
- Feature cards (3-column desktop grid) compress to single-column on mobile without sufficient vertical breathing room; content density makes scanning difficult
Recommendations
-
Reduce cookie banner footprint on mobile high
Use a minimal one-liner banner with 'Accept' button only; move 'Decline' and privacy link to a secondary action (e.g., collapsible or linked to privacy page).
-
Increase mobile hero font sizes and spacing high
Bump H1 to minimum 24px, body to 16px, and increase line-height to 1.6 for better readability; test with zoom at 200% for accessibility compliance.
-
Add card spacing and progressive disclosure on mobile medium
Increase vertical gap between feature cards on mobile (use margin-bottom: 2rem); consider collapsing 'Explore all features' section to a 'Show more' toggle to reduce initial load.
Conversion
Clear conversion path exists (hero CTA → free trial → dashboard setup), but the funnel is hampered by muddled CTA hierarchy, weak social proof, and missing reassurance signals (risk reversal, testimonials, security badges).
Issues Found
- No visible social proof or testimonials in hero/above-fold sections—relying entirely on self-generated dashboard mockup to build trust
- Secondary CTA 'See how it works' is positioned equally to 'Start free', creating decision paralysis instead of a clear path to conversion
- No risk-reversal copy visible (e.g., 'No credit card required' is mentioned in small print below hero, not emphasized as a conversion aid)
Recommendations
-
Add social proof badges above hero fold high
Include a brief testimonial carousel, user count ('1,000+ teams'), or G2/Capterra ratings badge near the top fold to build immediate credibility before CTA.
-
Restructure CTA hierarchy with risk reversal high
Make 'Start free' the sole hero CTA; move 'See how it works' to a secondary position; emphasize 'No credit card required' in bold near CTA button.
-
Add conversion micro-funnel tracking medium
Implement event tracking on CTA clicks, form submissions, and sign-up completions to identify where drop-off occurs and optimize accordingly.
Design & UX
Clean, modern design with excellent visual hierarchy and a cohesive dark/light palette split. The hero is crisp, the feature cards are well-organized, and the dashboard mockup is instantly compelling—but some micro-interactions feel static and there's zero visual differentiation between sections.
Issues Found
- Cookie consent banner is intrusive and appears repeatedly in multiple screenshots, breaking UX flow and suggesting it wasn't properly tested
- Navigation lacks visual feedback or hover states; the top nav feels inert despite being a key wayfinding element
- Feature card section ("How it works") is dense with six cards in a 3x2 grid but no clear progressive disclosure or filtering to guide user attention
Recommendations
-
Simplify cookie banner implementation high
Use a sticky footer banner that persists only once per session, or integrate consent tracking to eliminate repeated displays.
-
Add subtle hover/active states to nav medium
Implement underlines, background colors, or shadow effects on top navigation links to signal interactivity and current page context.
-
Prioritize feature cards with visual hierarchy low
Highlight top 3 features with larger cards or badges, then collapse remaining features into a 'Explore all' section to reduce cognitive load.
Copy & Messaging
Copy is crisp, benefit-driven, and deeply understand the pain point ('Your best numbers are hidden in a tab nobody opens'). Headlines are punchy and the value prop is crystal clear—but some CTAs bury the ask and the AI agent story could use sharper narrative.
Issues Found
- Primary CTA hierarchy is muddled: 'Start free' and 'See how it works' are visually equal weight, splitting conversion intent
- The AI agents feature is mentioned early but never fully contextualized—readers may not grasp why this is a differentiator vs. manual setup
- Copy in the 'How it works' section is passive ('Dashwall is built around...') rather than active/imperative, reducing urgency
Recommendations
-
Establish clear CTA hierarchy in hero high
Make 'Start free' prominent (bright, solid button) and downgrade 'See how it works' to a secondary ghost button or link to eliminate decision paralysis.
-
Tell the AI agent story upfront high
Add 1-2 sentences in the hero subheading explaining that agents auto-build dashboards (e.g., 'Tell Claude what to track, we build the wall'), not just manual webhooks.
-
Reframe 'How it works' with imperative language medium
Change 'Dashwall is built around...' to 'Create a tile. Send a value. Watch it update.' to feel more action-oriented and urgent.
Think you can beat 58/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.