How We Build Fast Websites (95+ Lighthouse Every Time)

A slow website loses 53% of mobile visitors if it takes more than 3 seconds to load, according to Google research. Every additional second drops conversion rates by 4.2%. At BRAINSROOT, we build websites that load in under 1.5 seconds by starting with the right foundation, modern build tools that ship only the code your page actually needs.

The short answer: fast websites ship less code, static HTML, optimized images, and no render-blocking CSS. That’s how we hit 95+ Lighthouse on every build.

What makes a website fast?

Three things determine page speed: the amount of JavaScript sent to the browser, how images are loaded, and whether the server responds quickly. Most slow sites suffer from bloated frameworks that ship hundreds of kilobytes of unused code. We use Astro and similar modern tools that deliver zero JavaScript by default, adding interactivity only where needed. The result is sites that score 95-100 on Lighthouse without additional optimization work.

How do you optimize above-the-fold content?

The content visible before scrolling should appear in under 1 second. We achieve this by loading critical CSS inline, deferring non-essential scripts, and using responsive images with proper dimensions. Heavy page elements like carousels, videos, and third-party widgets are loaded only after the main content renders. This technique, called lazy loading, can cut initial page weight by 40-60%.

How do you test performance on real devices?

A site that loads instantly on a MacBook Pro may take 8 seconds on a mid-range Android phone. We test on actual mobile devices and simulate slow 3G connections (2 Mbps, 500ms latency) because that is what many real users experience. Google Core Web Vitals (LCP under 2.5s, FID under 100ms, CLS under 0.1) are our minimum passing threshold, not our target.

What is the biggest performance mistake agencies make?

The most common mistake is adding a performance plugin or CDN as an afterthought instead of building for speed from the start. No caching layer can fix a page that ships 500KB of JavaScript. Performance must be architected at the framework level, not patched after launch. That is why we choose tools like Astro, which generates static HTML by default, and only load client-side JavaScript for interactive islands.

The result is a site that feels quick everywhere, ranks better in search, and keeps users engaged instead of sending them to a competitor’s faster page.