Skip to main content
DeLuxeStudio
Performance6 min read

Why Lighthouse 100 Isn't Magic — It's a Deliberate Choice

Run a free Lighthouse audit on the next ten small-business websites you visit. You'll find scores between 30 and 60 on mobile. Run it on the sites that actually rank on Google's first page — you'll see 70 to 90. Hitting 100 is rare, and not by accident. It's a deliberate choice that most agencies skip because the work isn't glamorous and the client can't see it. Here's what hitting 100 actually requires, and what it does for you when you get there.

What Lighthouse 100 actually means

Lighthouse measures four things: Performance (how fast it loads), Accessibility (how usable it is for people with disabilities), Best Practices (security + code health), and SEO (whether Google can crawl + understand it). Each scored 0–100. The Performance score on mobile is where almost everyone fails.

Performance specifically tracks Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift. Google uses these AS RANKING FACTORS. Not "we'll consider them" — they're weighted into your search position.

The four things that crush mobile scores

Almost every slow website fails one (or several) of the same four things:

  • Heavy JavaScript — 500KB+ of jQuery, sliders, "page builder" runtime. Each KB delays interactivity.
  • Blocking fonts — Google Fonts requests that pause rendering until the font downloads.
  • Unoptimized images — 4MB JPEGs served at 200x200 display size. Mobile data caps choke.
  • Layout shift — content jumping as ads/images/widgets load late. Hurts CLS score AND user experience.

Why most agencies skip performance work

Performance optimization is invisible until you compare numbers. Clients don't see "300ms LCP" — they see colors and fonts. Agency sales teams sell what clients can see. Engineering teams build what the brief says. Performance gets the leftover.

For a Montreal agency billing $15k for a site, spending an extra 8 hours on performance work cuts margin. Most don't. They ship the site, the client is happy with how it LOOKS, and three months later the owner wonders why nobody finds it on Google.

Performance is the cheapest, highest-impact SEO work you can do. It also requires no copy changes, no design changes, no client approval. If your developer didn't do it, you got short-changed.

The trade-offs hitting 100 requires

You can't hit 100 and also have:

  • Autoplay hero videos — even compressed, they tank LCP.
  • jQuery + 8 jQuery plugins — too much JS overhead.
  • WordPress with 12 plugins — page builders especially.
  • Stock-photo libraries with 50+ uncompressed images.
  • "Live chat" widgets that load 200KB of JS — most are useless anyway.

You CAN hit 100 and still have a beautiful, brand-rich site. The constraints force you to be intentional: instead of an autoplay hero video, use a single optimized image. Instead of 12 plugins, write the 50 lines of code each plugin replaced. Instead of jQuery sliders, use CSS.

What hitting 100 does for you

Three measurable outcomes:

  • Google ranking boost — Core Web Vitals are a direct ranking factor. Faster sites rank higher.
  • Mobile bounce rate drop — every 1-second delay in mobile load time loses ~10% of users. Sites that load in <1s have bounce rates 30–40% lower than sites loading in 3s.
  • Conversion lift — Amazon famously measured 1% conversion increase per 100ms of speed. The pattern holds at small-business scale: faster site, higher conversion, more leads/sales.

Key takeaways

  • Lighthouse 100 isn't magic — it's avoiding four common mistakes: heavy JS, blocking fonts, big images, layout shift.
  • Performance work is invisible to clients but is a direct Google ranking factor.
  • Hitting 100 requires deliberate trade-offs: no autoplay videos, no jQuery, no plugin spaghetti.
  • Every site we ship at DeLuxe Studio targets Lighthouse 100 on mobile by default — not as an upsell.

See the work

Every site we ship gets a real Lighthouse score. Browse the portfolio and verify yourself.

See the work

Read next