What counts as a good load time?

A useful benchmark is a Largest Contentful Paint under 2.5 seconds. A page feels noticeably fast when its most important content is fully visible in under two seconds.

What slows websites down most often?

In most projects, uncompressed images and excessive JavaScript are the biggest brakes, followed by third-party scripts and a slow server response.

Which free tools measure load time?

Google PageSpeed Insights provides the official score, WebPageTest offers a detailed waterfall analysis, and Lighthouse in Chrome DevTools handles local measurement.

Load Time Optimization. Why Every Second Moves Revenue

Fast websites sell better. How to reach load times under two seconds and which eight levers make the biggest difference.

Published on September 30, 2025Updated on January 10, 20264 min read

The most expensive seconds on the internet

The link between load time and business performance is well documented. Amazon measures roughly one percent less revenue for every additional 100 milliseconds of load time. Google records about 20 percent fewer searches when delivery slows by half a second. Walmart, in turn, reports around two percent more conversions for every second the page gets faster.

For a website that earns 10,000 euros in monthly revenue, the math becomes concrete. One second less load time can mean more than 200 euros in additional revenue per month. Performance is therefore not a technical detail but an economic factor.

What Google measures

Google rates a website's load performance through three metrics, the Core Web Vitals.

Largest Contentful Paint (LCP) captures when the largest visible element has loaded. That is usually the hero image or the main heading.

Cumulative Layout Shift (CLS) measures how much the content jumps while loading. It describes the familiar effect where the layout shifts at the last moment because an image loads late, and a click lands in the wrong place.

Interaction to Next Paint (INP) captures how quickly the page responds to clicks and input.

Metric	Good	Needs improvement	Poor
LCP	under 2.5 seconds	2.5 to 4 seconds	over 4 seconds
CLS	under 0.1	0.1 to 0.25	over 0.25
INP	under 200 ms	200 to 500 ms	over 500 ms

The eight most important optimizations

1. Optimize images

In most projects, images are the biggest performance killer. Four measures reliably help.

WebP or AVIF instead of JPEG and PNG (30 to 50 percent smaller)
Lazy loading for images below the visible area
Responsive images with srcset for different screen sizes
The right dimensions, so no 4000-pixel image for a 400-pixel container

2. Minimize JavaScript

Every kilobyte of JavaScript has to be downloaded, parsed, and executed. That costs time, especially on mobile devices.

Load only what is genuinely needed
Code splitting, so each page loads only its own code
Question third-party scripts critically, since five analytics tools are rarely necessary

3. Optimize CSS

Load critical CSS inline in the <head>
Load the remaining CSS asynchronously
Remove unused CSS rules

4. Reduce server response time

Time to First Byte (TTFB) should stay under 200 milliseconds.

Use a CDN (Cloudflare, Vercel Edge)
Apply server-side rendering or static site generation
Optimize database queries

5. Configure caching correctly

Files that rarely change should stay in the cache for a long time.

Images, fonts, CSS, and JS with a one-year cache
HTML with a short cache or revalidation
Cache busting through a filename hash

6. Optimize fonts

Web fonts are often unexpectedly large.

Load only the needed font weights (such as 400, 600, and 700 rather than all of them)
Use font-display: swap for immediate text display
Self-host fonts instead of using Google Fonts, which also helps with GDPR compliance

7. Reduce third-party scripts

Every external script is a performance risk.

Google Analytics as GA4 with gtag.js, which is lightweight
Facebook Pixel only when it is truly needed
Chat widgets loaded only after the first interaction
Cookie consent through a lean solution

8. Preloading and prefetching

The browser can be told what comes next.

<link rel="preload"> for critical resources
<link rel="prefetch"> for the likely next page
<link rel="preconnect"> for external domains

How to measure load time

Four free tools cover the need in most cases.

Google PageSpeed Insights, the official Google score
WebPageTest with a detailed waterfall analysis
Lighthouse in Chrome DevTools for local measurement
GTmetrix for historical comparisons

Performance is not a nice-to-have

Load time shapes rankings, conversion rate, user satisfaction, and ultimately revenue. Every second counts, in the literal sense. That is why we treat performance not as an afterthought but as part of going further in delivery, a fixed element of any solid build.

A measurement with concrete before-and-after comparisons shows how fast a website really is. We measure and optimize.