Website speed: why every second matters

Speed isn't a technical detail. When a page is slow to load, some visitors leave before they even see the content — and Google factors loading experience into how it ranks your site. A fast site converts more and shows up better in search.

What Google actually measures

Google evaluates loading experience through three official metrics, the Core Web Vitals. These are the numbers that truly matter:

Metric	What it measures	Target (good)
LCP (Largest Contentful Paint)	time for the largest element to appear	up to 2.5s
INP (Interaction to Next Paint)	responsiveness to the first interaction	up to 200ms
CLS (Cumulative Layout Shift)	visual stability (the layout doesn't "jump")	up to 0.1

These thresholds are set by Google itself and are part of the page experience signals used in ranking.

Why this affects sales

Every extra second of waiting raises the chance a visitor gives up — especially on mobile, where connections vary and patience is shorter. A slow site loses the visit before showing the product; a fast site keeps the person on the page and improves conversion.

How to measure yours

Use Google PageSpeed Insights (pagespeed.web.dev). It's free, runs on any URL, and shows exactly what's slow and how to fix it — based on the Core Web Vitals above.

What makes a site slow

Unoptimized images — the most common cause. Use modern formats (WebP/AVIF), compression, and the right size for each screen.

Poor hosting — cheap shared plans are often slow. Modern platforms like Vercel and Netlify serve your site from servers around the world, close to the visitor.

Heavy code — too many plugins, unnecessary JavaScript, unused CSS. A well-built site loads only what's needed.

No caching — the visitor's browser should keep static files so it doesn't re-download everything on each visit.

Quick fixes

Compress images (squoosh.app), enable lazy loading, minimize CSS and JavaScript, and use a CDN. These are gains you see directly in PageSpeed.

Performance as an investment

Dilevate sites are built with Next.js: automatic image optimization, server-side rendering, and smart caching — an architecture designed to pass Core Web Vitals. Speed isn't technical polish: it's a direct return in conversion, SEO, and visitor experience.

Frequently asked questions

What's the ideal website speed?

There's no single number in "seconds" — what matters are Google's Core Web Vitals: LCP up to 2.5s, INP up to 200ms, and CLS up to 0.1. When all three are within target, the experience is considered good.

How do I know if my site is slow?

Run the URL through Google PageSpeed Insights (pagespeed.web.dev), which is free. It measures Core Web Vitals and lists what's weighing the page down, most critical first.

Does speed affect Google ranking?

Yes. Loading experience (Core Web Vitals) is one of the signals Google uses to rank pages, alongside content and relevance. A slow site tends to rank worse.

What slows a site down the most?

In most cases, large uncompressed images. After that come poor hosting, too many plugins and JavaScript, and lack of caching.