Web DevelopmentPerformanceCore Web VitalsCRO

Website Performance: Why Every Second Costs You Sales

How website speed impacts user experience and conversions, plus the technical optimizations that move the biggest needles.

AR

Alex Rodriguez

Lead Engineer

May 5, 2025
9 min read
Website Performance: Why Every Second Costs You Sales

Web Development

Website Performance: Why Every Second Costs You Sales

TL;DR

  • Every 100ms of load time costs about 1% in conversion. The math compounds fast.
  • Google ranks fast sites higher. SEO and CRO converge.
  • Most slowness is not framework choice, it is image weight and third-party scripts.
  • Lighthouse 95+ is reachable for any site, with the right discipline.

Amazon famously calculated that every 100ms of latency cost them 1% in sales. Walmart found similar numbers. Yet most sites in 2025 still load in 6–8 seconds on mobile. Web performance is the silent killer, it does not show up in any single analytics view, but it sits behind every metric you care about. Here is what actually moves the needle.

Start by measuring honestly

Run your site through PageSpeed Insights on mobile (not desktop). Mobile is the only number that matters. Look at LCP (largest contentful paint), CLS (cumulative layout shift), and INP (interaction to next paint). These three numbers are the Core Web Vitals. Hit good on all three or fix what is yellow first.

Images are usually 60% of your weight

Most sites ship 3MB of images on every page load. Compress them aggressively. Use WebP or AVIF (not JPEG). Use modern image components (Next.js Image, Cloudinary, Imgix) that serve responsive sizes automatically. Lazy-load anything below the fold.

Third-party scripts are the second killer

Every tag in your tag manager is a tax. Audit them quarterly. Most sites are running 8–12 scripts they no longer need, old A/B tools, abandoned analytics, dead chat widgets. Remove what is not earning its keep.

Serve from the edge

Static rendering + edge caching is the modern web's superpower. Vercel, Cloudflare, and Netlify all make this trivial. A static page served from the edge will outperform any dynamic page on any framework, by orders of magnitude.

Fonts: subset and preload

Custom fonts are great branding and terrible performance. Subset to the characters you actually use. Preload the two faces you need above the fold. Use font-display: swap so text never blocks render.

JavaScript: ship less of it

Every kilobyte of JS is parsed and executed on the user's phone. Use server components, islands architecture, or static rendering wherever possible. A landing page should not need 500KB of React to display a marketing message.

Layout shift kills trust

A page that visibly reflows as it loads feels broken even if it loads fast. Reserve space for images with explicit width/height. Reserve space for ads and embeds. Watch your CLS score religiously.

Conclusion

Performance is not a one-time project, it is a permanent discipline. Set a Lighthouse score budget (95+) and refuse to ship features that drop you below it. Monitor real-user metrics with tools like Vercel Speed Insights or Cloudflare RUM. Every percentage point you claw back compounds, in conversion, in SEO, in customer trust.

Found this useful? Share it.

AR

Written by

Alex Rodriguez

Lead Engineer

A senior practitioner at Ace Studios. Has shipped work across hundreds of brands and channels, and writes about what is actually working, not what is fashionable.

Want help putting this into practice?

We've helped 500+ brands ship the playbooks we write about. Let's talk about yours.