Checked 22 Sep 2026, 16:45 UTC·
·
Watch for changes

We re-check this page and email you when the numbers actually move — the score, the page weight, or the page itself being rebuilt. No digest, no newsletter.

Today’s numbers are saved as your baseline. One click to unsubscribe, from any message.

duncanwilliams.io loads faster with WebSpeed

Measured PageSpeed before and after WebSpeed optimization — no plugins, no migration.

Measured with WebSpeed on

Speed Index from a single check. Repeat checks of the same page typically differ by around 30%, so read the two times as a direction, not a precise multiplier.

2.7s
was 3.3 s−0.6 s
Page weight
1.1MB
was 1.9 MB−41%
Main content (LCP) · desktop
0.9s
was 1.4 s−0.5 s
If your visitors get this speed

From the measured LCP gain: −1.1 s.

Core Web Vitals are a Google ranking signal, but work as a “tiebreaker” — they matter most when two pages are roughly equal in relevance and content. The biggest SEO benefit comes from moving out of the Poor zone (score < 50).

Forecast
≤ +28%

From the measured LCP gain: −1.1 s.

Google / Deloitte (2019): 0.1 s improvement → +8% conversions in retail. Portent: each extra second of load time reduces conversion rate ~4%.

Forecast
+5%

From the measured LCP gain: −1.1 s.

Based on Google data: pages loading in 3 s vs 1 s show ~32% higher bounce rate. Estimate scales proportionally to LCP improvement and is site-specific.

Forecast
−8%

From the measured page weight: ≈ 0.95 → 0.56 g per visit.

Transferred bytes × ≈0.5 g of CO₂ per MB, a common average for networks and devices. The real figure depends on the hosting and the visitor’s connection.

Forecast
−41%

Forecasts, not measurements: measured gains × published studies — tap any underlined label for the source.

Beyond the score
Stays up during outages
Cached delivery serves the last good version if your origin fails.
Absorbs traffic peaks
The proxy cache serves ready pages, so spikes don’t topple the origin.
Lighter on your hosting
Fewer origin hits and less third-party code on the critical path.
Lower CO₂ per visit
A lighter page transfers fewer bytes and burns less energy.
Compared with every site we’ve measured
PageSpeedscore, higher is better
Mobile
050100

You 71 — in the fastest quarter

Desktop
050100

You 95 — in the fastest quarter

Screen filledSpeed Index
Mobile
010 s20 s+

You 3.3 s — in the fastest quarter

Desktop
05 s10 s+

You 0.7 s — in the fastest quarter

Main contentLCP
Mobile
020 s40 s+

Fastest quarter ≤ 5.3 s · you 7.8 s

Desktop
05 s10 s+

Fastest quarter ≤ 1.1 s · you 1.4 s

Page weighttransferred
Mobile
010 MB20 MB+

Fastest quarter ≤ 1.6 MB · you 1.9 MB

Desktop
010 MB20 MB+

Fastest quarter ≤ 1.8 MB · you 2 MB

Based on 1115 sites WebSpeed has measured, across every platform, as they are, without our optimization. Updated 24 Sep 2026.

Speed metrics

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below7174+3
First Contentful Paint. The moment the browser renders the first piece of real content — the first sign to the visitor that the page is loading.≤ 1.8s2.6 s2.7 sNo change beyond run-to-run noise.
Largest Contentful Paint. The time it takes for the largest image or text block in the viewport to render — one of Google's three Core Web Vitals.≤ 2.5s7.8 s6.3 s−20%
How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s3.3 s2.7 s−19%
Total Blocking Time. The total time the main thread was blocked by long tasks during load — the lab metric that stands in for real-world responsiveness.≤ 200ms30 ms10 msNo change beyond run-to-run noise.
Cumulative Layout Shift. A score for how much visible content unexpectedly jumps around while the page loads — one of Google's three Core Web Vitals.≤ 0.100No change beyond run-to-run noise.
LCP breakdownobserved load, no throttling
What the largest visible element was — an image or a block of text. The two are sped up by different means.ImageImagesame
Time until the first byte of the HTML arrived.TTFB31 ms108 msNo change beyond run-to-run noise.
Time between the first byte and the moment the browser started downloading the LCP image. Long when the image is found late — lazy-loaded, set from CSS or JS.until the image is requested1.0 s518 ms−49%
Time spent downloading the LCP image itself — its weight and the connection.downloading the image553 ms44 ms−92%
Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted100 ms109 msNo change beyond run-to-run noise.

Page weight

loaded during the test
Now1.9 MB
Fast1.1 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.17588−87
The page itself, before anything it references.1143 KB1134 KBNo change beyond run-to-run noise.
Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site.89960 KB50525 KB−45%
Stylesheets downloaded during the test.11 KB11 KBNo change beyond run-to-run noise.
Web font files downloaded during the test.270 KB270 KBNo change beyond run-to-run noise.
Images downloaded during the test. Images below the fold may load later, after the test.21232 KB21232 KBNo change beyond run-to-run noise.
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.78No change beyond run-to-run noise.
Bytes downloaded from those third-party domains.1.6 MB1006 KB−38%

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below9598+3
First Contentful Paint. The moment the browser renders the first piece of real content — the first sign to the visitor that the page is loading.≤ 1.8s0.7 s0.9 sNo change beyond run-to-run noise.
Largest Contentful Paint. The time it takes for the largest image or text block in the viewport to render — one of Google's three Core Web Vitals.≤ 2.5s1.4 s0.9 s−36%
How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s0.7 s0.9 sNo change beyond run-to-run noise.
Total Blocking Time. The total time the main thread was blocked by long tasks during load — the lab metric that stands in for real-world responsiveness.≤ 200ms20 ms0 msNo change beyond run-to-run noise.
Cumulative Layout Shift. A score for how much visible content unexpectedly jumps around while the page loads — one of Google's three Core Web Vitals.≤ 0.10.010.027No change beyond run-to-run noise.
LCP breakdownobserved load, no throttling
What the largest visible element was — an image or a block of text. The two are sped up by different means.ImageTextchanged
Time until the first byte of the HTML arrived.TTFB18 ms110 msNo change beyond run-to-run noise.
Time between the first byte and the moment the browser started downloading the LCP image. Long when the image is found late — lazy-loaded, set from CSS or JS.until the image is requested407 ms—
Time spent downloading the LCP image itself — its weight and the connection.downloading the image372 ms—
Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted38 ms488 ms+450 ms

Page weight

loaded during the test
Now2 MB
Fast1.2 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.17587−88
The page itself, before anything it references.1142 KB1134 KBNo change beyond run-to-run noise.
Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site.89959 KB50525 KB−45%
Stylesheets downloaded during the test.11 KB11 KBNo change beyond run-to-run noise.
Web font files downloaded during the test.5276 KB4236 KB−15%
Images downloaded during the test. Images below the fold may load later, after the test.20161 KB18159 KBNo change beyond run-to-run noise.
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.78No change beyond run-to-run noise.
Bytes downloaded from those third-party domains.1.7 MB1.1 MB−37%

PageSpeed scores are measured by Google PageSpeed Insights and are not guaranteed: they vary run to run and depend on network, device and third-party code.

Pricing

Pick how hands-off you want it

The before/after check is free to run; it isn’t one of these plans. Choose a plan when you’re ready to make the speed-up permanent — or buy the report once and apply it yourself.

Most popularSaaS subscription
Fast
from €10 · /mo
Zero-code, automatic
14-day free trial
  • The whole optimization pipeline, live
  • One site
  • Proxy or on-site SDK, no code changes
  • Cached delivery keeps your site up during origin outages
  • Priced by monthly visits, scales with you
Request access

We connect it for you.

SaaS subscription
Growth
from €79 · /mo
For several sites at once
14-day free trial
  • Everything in Fast, across multiple sites
  • Priority cache — your pages stay warm
  • Support with a named contact
  • One invoice for the whole portfolio
Request access

Agencies and multi-site owners.

SaaS + hands-on service
Custom
from €179 · /mo
Hand-tuned for your site
  • Everything in Growth
  • A config built by hand for your site
  • What only you can change, written up for your team
  • Set up, measured and maintained by us
Get a plan for my site

We look at your site by hand first, then keep it tuned. Six months minimum.

Subscriptions start with a 14-day free trial (Fast and Growth), then run for a minimum of 6 months — you commit only after the trial. Fast is priced by monthly visits; indicative launch pricing.

Recommended
Downloadable report

Not ready for a subscription?

Buy the Audit once and apply it yourself — the same findings the pipeline acts on, written up as instructions.

  • One site, up to 5 pages you choose
  • The same fixes Fast applies, written up as a guide you run yourself
  • Server settings, code changes and ready-to-paste head snippets
  • Before/after PageSpeed from the free check (PDF / HTML / MD)
  • Re-issued free for a year as your site changes
€149 · one-time
DIY: you apply it
Get the auditSee an example report →

Not useful? Email us within 14 days and we refund it. A document, not a service — you apply it; Custom is the same work done for you.

About these numbers
How do we measure?
We test each configuration of your site — the original and with our optimizations — 2–3 times for mobile and desktop, and take the median rather than a single run, which filters out random spikes.
Why does my PageSpeed show different numbers?
We use Google Lighthouse — the same engine behind PageSpeed Insights. Differences come from the test server location, CDN cache state and Lighthouse version. Compare columns with each other here: the relative improvement is what matters.
Does speed affect Google rankings?
Core Web Vitals are a ranking factor since May 2021, but Google calls them a tiebreaker. The clearest gain is moving out of the Poor zone (score < 50); if you are already Good, further speed still cuts bounce and lifts conversion.