How fast is your site?
Enter your address and see how much faster we'd make it — measured, before and after. We check first-byte time, compression, image formats and caching in about ten seconds.
Plus roughly lighter pages with Brotli, and up to 70% smaller images. (Estimated.)
Make it real — in two minutes
Point at NordicCDN and ship these wins. 25 GB free, no card.
Supercharge my site →"After" figures are estimates based on typical NordicCDN optimizations.
A slow site is a leak, not an inconvenience
Nobody sits and waits any more. Every extra second between the click and the first pixel is a share of your visitors quietly leaving — and you never see them in your analytics as anything but a slightly lower number.
Going from a 1-second to a 3-second load makes a visitor 32% more likely to leave before seeing anything.
Google, mobile page speed research
Deloitte measured a 0.1-second improvement in load time lifting retail conversions by 8.4% and average order value by 9.2%.
Deloitte, “Milliseconds Make Millions”
Amazon’s often-cited internal finding: every 100 ms of extra latency cost roughly 1% in sales.
Amazon, widely reported
Figures are published industry research, not NordicCDN measurements — the exact numbers depend on your audience and your site. The direction never changes.
Most of the wait happens before anything is drawn
On an uncached site the browser sits idle while your server wakes up, runs code, queries a database and builds the page from scratch — for a page that hasn't changed in weeks. Only then does the download start.
Six things that decide how fast your site feels
We request your page once, exactly as a browser would, and read what came back. Here's what each result means and what "good" looks like.
Time to first byte
How long the browser waits before a single byte arrives. It is dead time — nothing is on screen — and it sits underneath every other metric.
Good looks like: Under 200 ms; cached edge responses land around 15 ms.
Compression
Whether HTML, CSS and JavaScript are compressed in transit. Uncompressed text is typically three to four times bigger than it needs to be.
Good looks like: Brotli, with gzip as the fallback for old clients.
CDN in front
Whether anything is serving copies close to your visitors, or whether every request travels all the way back to one server.
Good looks like: A cache hit from an edge in the visitor’s own region.
HTTP version
Newer protocols open connections faster and multiplex requests instead of queuing them, which matters most on mobile networks.
Good looks like: HTTP/2 at minimum, HTTP/3 (QUIC) ideally.
Modern image formats
How many images are still JPEG or PNG. Images are usually the heaviest thing on a page by a wide margin.
Good looks like: WebP, sized to the slot they are actually displayed in.
Browser caching headers
Whether returning visitors have to download your assets all over again, or can reuse what they already have.
Good looks like: Long max-age on static assets, with versioned filenames.
Speed is a ranking signal, measured on real visits
Core Web Vitals are collected from actual Chrome users on your site — not from a lab test you can game. Three numbers, with thresholds Google publishes openly.
How long until the biggest thing on screen — usually the hero image or headline — has actually appeared.
What moves it: Cutting first-byte time and shrinking the hero image move this more than anything else.
How quickly the page reacts when someone taps or clicks. Replaced FID in 2024 as the responsiveness metric.
What moves it: Lighter pages and less blocking JavaScript; minification at the edge helps.
How much the layout jumps around while loading — the reason you tap the wrong button.
What moves it: Mostly a markup fix, but late-arriving images make it worse.
You don't rebuild the site. You stop rebuilding the page.
Almost every slow site is slow for the same boring reason: the same page is generated from scratch for every visitor, from one server, far away. Fixing that is a configuration change, not a project.
Build the page once, not once per visitor
The finished HTML is cached at the edge. The next visitor gets it straight from memory — your server never hears about the request.
Serve it from near the visitor
A request from Copenhagen is answered in Copenhagen instead of crossing an ocean twice. That alone removes most of the first-byte time.
Send fewer bytes
Brotli on text, WebP on images, CSS and JavaScript minified on the way out — no build step, no plugin.
Keep the dynamic parts dynamic
Carts, logins, checkout and admin are detected and passed straight to your origin, uncached. Visitors get speed; customers get a correct page.
Read more: WordPress CDN · Image CDN · Site Accelerators · Live before/after demo
Questions, answered
Stop losing visitors to the loading spinner
Start free in two minutes — 25 GB free every month, no card required.
Start free