Speed is revenue.

Google / SOASTA+90% at 5 seconds+32% more likely to bounce when load time rises from 1 to 3 seconds.more bounce when load hits 3s
All case studies

Confidential · B2B SaaSSaaSHome page · performanceSep 2026

From a 4.4-second wait to a page that reacts instantly

A marketing home page that looked fast on a fast laptop and felt broken on a phone. The audit traced 1.24 MB of JavaScript and a 1.4 MB hero image; the rebuild shipped a 480 KB page and moved every Core Web Vital into the good band.

  • Core Web Vitals
  • JavaScript
  • Images
  • Caching

Largest Contentful Paint

5.80 s1.40 s

−76%

Total Blocking Time

814 ms120 ms

−85%

JavaScript shipped

1.24 MB190 KB

−85%

Lighthouse performance

3899

+61 pts

Before and after

What was slowing it down → what changed

  1. Before

    The hero image shipped as a single 2400 px PNG at 1.4 MB to every device, including phones.

    After

    Generated responsive AVIF and WebP derivatives, served the right width per viewport, and preloaded only the hero candidate.

  2. Before

    1.24 MB of JavaScript, because a component library was imported site-wide for a handful of components.

    After

    Imported per-component, split routes, and removed two unused dependencies. JavaScript dropped to 190 KB.

  3. Before

    Analytics and chat widgets loaded synchronously before first paint, blocking the main thread for over 800 ms.

    After

    Deferred both until the page was interactive. Analytics still records the visit, just not before the visitor can read.

  4. Before

    Custom fonts loaded without preload, so the headline re-rendered after the first paint.

    After

    Preloaded the two font files actually used, with metric-tuned fallbacks and font-display: swap.

  5. Before

    HTML was rebuilt on every request with no cache headers: TTFB sat at 320 ms.

    After

    Pre-rendered the marketing pages, served them from the edge, and cached static assets with hashed filenames. TTFB: 160 ms.

The numbers

Lighthouse, same local production build, median of five runs

Performance

3899

Accessibility

92100

Best practices

83100

SEO

91100

Confidential · B2B SaaS: metrics before and after optimization
MetricBeforeAfterGood threshold
LCPCWV5.80 s1.40 s≤ 2.5 s
INP (lab: TBT)CWV814 ms120 ms≤ 200 ms
CLSCWV0.000.00≤ 0.10
FCP1.20 s0.60 s≤ 1.8 s
TTFB320 ms160 ms≤ 800 ms
Page size1.41 MB480 KB≤ 2 MB
JavaScript1.24 MB190 KB≤ 500 KB
Requests5424≤ 80
DOM nodes2,6941,420≤ 1,500

Lab data, not a promise: field results depend on your visitors' devices and networks. The thresholds above are the 75th-percentile targets Google uses.

The playbook

The same order of work applies to most sites

  1. Measure the same thing twice

    Run the same page on the same local production build, five times, and report the median. Changing tools or conditions between runs is how before/after tables end up meaningless.

  2. Fix the LCP element first

    Lighthouse names the element that paints last. Optimizing anything else before that one image or heading is guessing.

  3. Cut JavaScript before writing more

    Coverage reports show which bytes actually run. Every unused import in the first-load bundle is a direct tax on INP.

  4. Reserve space for everything

    Width and height on media, fixed slots for injected banners. CLS is almost always about space that was not reserved.

  5. Defer third parties, do not delete them

    Marketing rarely accepts removing analytics. Loading it after interaction keeps the data and gives the visitor the page first.

  6. Verify with field data

    CrUX needs up to 28 days to catch up. Watch the PageSpeed Insights field section over time, not just the lab score on launch day.

What it changed

  • Every Core Web Vital landed in the good band on the same hardware and connection profile.
  • The page now ships 66% less weight and 85% less JavaScript than before.
  • Lighthouse performance moved from 38 to 99, measured on a local production build before and after.

Check it yourself

The tools and definitions behind every number above

Privacy settings

Choose what can load

Necessary storage keeps the site working. Everything else starts off and only runs if you turn it on.

Change this any time from the footer or the privacy policy. Turning off something that already loaded reloads the page so it stops.