How Workspace CMS sites score 95+ on PageSpeed Insights by default
If you've ever watched a freshly-built WordPress site melt under a PageSpeed Insights run, you already know the problem: most platforms treat performance as a configuration project, not a default. Workspace CMS is built the other way around. A new site rolls out of our build pipeline already in the 95+ band across Performance, Accessibility, Best Practices, and SEO — and that's not a marketing claim, it's the only state our deploy will accept.
The four guardrails that get us to 95+ every time
The numbers on our PSI scorecards aren't the result of one optimization. They're the result of treating four specific failure modes as non-negotiable from the first commit on a project.
1. The render pipeline ships only the HTML you need
Every Workspace CMS site is server-rendered on Vercel's edge, with HTML streaming straight to the browser. There's no client-side hydration tax on the marketing surface, no “render-blocking React app” bootstrap. The page-level JavaScript budget for a typical Workspace site is under 30 KB compressed — and that includes the analytics ping, the AI-visibility tracker beacon, and the small reveal-on-scroll observer that handles section fade-ins.
For comparison: a default WordPress install with a typical theme will ship 250–600 KB of JS before you've added a single plugin. Every plugin you add pushes that number up. Our number doesn't move when you add a page.
2. Images are pre-optimized at upload, served as AVIF/WebP, and sized correctly
The image pipeline is the single biggest swing factor on Lighthouse Performance, and most CMSes get it wrong by giving editors a raw upload field and trusting them to do the right thing. We don't. When you drop an image into the Workspace CMS media library, we:
- Run it through a quality-targeted re-encode to AVIF and WebP, with a JPEG fallback for the few clients that still need it.
- Stamp width and height attributes on the rendered
<img>so the browser can reserve layout space before the bytes arrive — that's how we keep Cumulative Layout Shift at zero. - Generate a responsive
srcsettied to the actual rendered slot size, so a hero image doesn't ship a 3200-pixel original when the viewport is 768.
The result: hero images that look sharp on retina screens but weigh in at 40–80 KB on the wire. Largest Contentful Paint stays under 1.5 seconds on a typical fiber connection.
3. Fonts are subset, self-hosted, and preloaded
The third-most-common reason a marketing site falls out of the 95+ band is webfonts. Loading Google Fonts from fonts.googleapis.com costs you a DNS lookup, a TLS handshake, and a CSS round-trip before the first font byte arrives. We don't do that. Every Workspace site self-hosts its display font as a subset WOFF2, preloaded in the <head>, with a font-display: swap fallback so text stays readable while the real font lands. One font file, one round-trip, one render.
4. The deploy gate blocks regressions
None of the above survives without a guardrail. Every Workspace CMS deploy runs a Lighthouse audit on the changed routes as part of the CI step. If any of the four Lighthouse categories drops below 90, the deploy is blocked and a strategist gets paged. We've shipped this gate to every client site we run, which is why the scorecards on the homepage of workspacecms.ai aren't “we hit 95 once.” They're the steady state.
Why this matters past the bragging rights
The PSI score is a proxy. The thing it's a proxy for is what Google's Core Web Vitals team has been telling us for five years: faster sites get more traffic, more conversions, and (since 2021) a small but real ranking lift in organic search. The AI engines are even more aggressive about this — ChatGPT's web tool and Perplexity's crawler both downrank sites that take more than three seconds to first paint, which means a slow site is increasingly invisible to the search surface buyers are actually using.
If your current site sits in the 50s or 60s on mobile PageSpeed — which is where most law-firm, medspa, and B2B SaaS sites sit — the cost isn't “a slightly lower score.” It's the conversions and the citations you don't see because the AI engine timed out on the request and recommended a competitor instead.
What you'd actually run if you wanted to replicate this
If you want to get to 95+ on your existing stack without rebuilding, the cheap-and-correct moves in priority order:
- Convert your hero image to AVIF and explicitly size it. This alone usually gets you 10–15 Lighthouse points.
- Self-host your webfonts as WOFF2 subsets. Another 3–6 points.
- Audit your third-party scripts. Every
<script src="https://something-marketing.example/…">is a tax. Most of them can be moved server-side or removed entirely. - Add a CI Lighthouse gate. Without it, the score will drift back down inside three sprints.
If the list looks like a quarter of engineering work, that's because it is. The reason Workspace CMS clients get to 95+ on day one is that we've already done that work, once, and we ship it as the platform default. New site, new vertical, new design — same performance posture.
Want us to audit your current site's PageSpeed posture and walk you through what we'd change? Book a free 30-minute strategy call. A real 1Digital operator runs the Lighthouse pass live on the call.
Liked this? Talk to the team that wrote it.
Book a free 30-minute call. A real 1Digital® strategist runs a live audit of your site, your PageSpeed, your llms.txt, and your AI visibility — and tells you what we'd do.
Want the full picture? Browse more posts