Back to feed
Dev.to
Dev.to
7/4/2026
How I got LCP under 2s on a 38-page Blazor WebAssembly site (Cloudflare Pages)

How I got LCP under 2s on a 38-page Blazor WebAssembly site (Cloudflare Pages)

Short summary

Blazor WebAssembly performance engineer reduced Largest Contentful Paint (LCP) from 6–8s to under 2s through six mechanical fixes: removing unnecessary service worker registration, eliminating self-reload logic, adding preconnect hints, and proper cache busting. Real commits and metrics demonstrate Blazor viability with correct architecture—performance depends on engineering choices, not framework limitations. Techniques apply to single-page applications broadly.

  • •Six specific optimizations reduced LCP from 6–8s to under 2s on a 38-page site with measured impact per fix
  • •Removed service worker registration (200ms) and self-reload function (2000ms) as largest wins
  • •Added preconnect hints and cache versioning for cold pageview optimization

Generated with AI, which can make mistakes.

Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

The original title is: "Using <link rel=preload> to reduce Blazor WASM LCP by 467ms"
Dev.to
The original title is "How We Turned a High-Traffic News Site's Core Web Vitals from Red to Green"
Dev.to
The original title is "The 3-Second Rule of Web Performance — And How to Beat It"
Dev.to
How I get marketing sites to 100/100 on mobile Lighthouse (the exact Astro setup)
Dev.to