How fast could your site be?

Enter your address. We measure it as it is and through WebSpeed, side by side.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Checked 24 Oct 2026, 04:45 UTC·
·
Watch for changes

Monitoring that writes to you when the score or the page weight really moves is in development. Leave your email and we’ll tell you when it starts. No digest, no newsletter.

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

aift.io loads faster with WebSpeed

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

Measured with WebSpeed on
Mobile · PageSpeed
76
was 65+11
Desktop · PageSpeed
97
was 75+22

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.

3.8s
was 4.1 s−0.3 s
Page weight
1.4MB
was 12 MB−89%
If your visitors get this speed

From the measured LCP gain: −18.2 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
≤ +40%

From the measured LCP gain: −18.2 s.

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

Forecast
+30%

From the measured LCP gain: −18.2 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
−20%

From the measured page weight: ≈ 6 → 0.68 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
−89%

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

Get this speed — try free14 days free, then from €10/mo, billed yearly · priced by visits
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 other WordPress sites
PageSpeedscore, higher is better
Mobile
050100

Fastest quarter 80+ · you 65

Desktop
050100

Fastest quarter 96+ · you 75

Screen filledSpeed Index
Mobile
010 s20 s+

Fastest quarter ≤ 3.4 s · you 4.1 s

Desktop
02.5 s5 s+

Fastest quarter ≤ 0.9 s · you 0.9 s

Main contentLCP
Mobile
020 s40 s+

Fastest quarter ≤ 3.7 s · you 35.3 s

Desktop
05 s10 s+

Fastest quarter ≤ 0.9 s · you 6.6 s

Page weighttransferred
Mobile
010 MB20 MB+

Fastest quarter ≤ 1.1 MB · you 12 MB

Desktop
020 MB40 MB+

Fastest quarter ≤ 1.3 MB · you 14.1 MB

Based on 2844 WordPress sites WebSpeed has measured, as they are, without our optimization. Updated 9 Nov 2026.

Speed metrics

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below6576+11
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.8s4.1 s3.8 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.5s35.3 s4.4 s−88%
How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s4.1 s3.8 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.≤ 200ms10 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.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.TextTextsame
Time until the first byte of the HTML arrived.TTFB7 ms17 msNo change beyond run-to-run noise.
Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted493 ms193 ms−61%

Page weight

loaded during the test
Now12 MB
Fast1.4 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.6034−26
The page itself, before anything it references.135 KB138 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.12102 KB11102 KBNo change beyond run-to-run noise.
Stylesheets downloaded during the test.530 KB325 KBNo change beyond run-to-run noise.
Web font files downloaded during the test.5520 KB5520 KBNo change beyond run-to-run noise.
Images downloaded during the test. Images below the fold may load later, after the test.3611.2 MB11661 KB−94%
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.75−2
Bytes downloaded from those third-party domains.5.2 MB616 KB−88%

What holds the main thread

Lighthouse attribution, lab run
No plugin or third-party script blocked the main thread for more than 50 ms. The 9 ms of blocking time on this page comes from the site’s own code and from smaller scripts, none over 50 ms.

Already on this site

Original page, before Fast
  • No speed tools recognisedNo caching plugin, CDN or speed host left a trace in the page’s code or headers
  • Images are in modern formats and sized to the screenMissing
  • No CSS or JS holds back the first paintMissingLighthouse estimate: −600 ms LCP
  • CSS and JS are minifiedMissingLighthouse estimate: −150 ms LCP · −3 KB
  • Text stays visible while web fonts loadMissing
  • Static files are cached in the browserOK
  • The page is compressed (gzip or brotli)OK
How Fast handles this site
  • Admin area/wp-admin/ and /wp-login.php pass through Fast unchanged and are never cached

Tools are recognised from the page’s code and response headers. A tool that leaves no trace there is not listed.

“OK” means Lighthouse found nothing to fix on the original page — not that someone switched it on.

Savings are Lighthouse’s own estimates for the original page, not measured by us.

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below7597+22
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.9 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.5s6.6 s1.2 s−82%
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.9 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.≤ 200ms0 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.100.001No 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.TextTextsame
Time until the first byte of the HTML arrived.TTFB8 ms17 msNo change beyond run-to-run noise.
Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted827 ms256 ms−69%

Page weight

loaded during the test
Now14.1 MB
Fast5.3 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.6347−16
The page itself, before anything it references.135 KB138 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.12102 KB11102 KBNo change beyond run-to-run noise.
Stylesheets downloaded during the test.530 KB325 KBNo change beyond run-to-run noise.
Web font files downloaded during the test.5520 KB5520 KBNo change beyond run-to-run noise.
Images downloaded during the test. Images below the fold may load later, after the test.3913.4 MB254.6 MB−66%
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.75−2
Bytes downloaded from those third-party domains.7.4 MB4.4 MB−41%

What holds the main thread

Lighthouse attribution, lab run
No plugin or third-party script blocked the main thread for more than 50 ms.

Already on this site

Original page, before Fast
  • No speed tools recognisedNo caching plugin, CDN or speed host left a trace in the page’s code or headers
  • Images are in modern formats and sized to the screenMissing
  • No CSS or JS holds back the first paintMissingLighthouse estimate: −100 ms LCP
  • CSS and JS are minifiedMissingLighthouse estimate: −3 KB
  • Text stays visible while web fonts loadMissing
  • Static files are cached in the browserOK
  • The page is compressed (gzip or brotli)OK
How Fast handles this site
  • Admin area/wp-admin/ and /wp-login.php pass through Fast unchanged and are never cached

Tools are recognised from the page’s code and response headers. A tool that leaves no trace there is not listed.

“OK” means Lighthouse found nothing to fix on the original page — not that someone switched it on.

Savings are Lighthouse’s own estimates for the original page, not measured by us.

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. How to read this report

Measured on this page

PageSpeed 65 → 76 on mobile and 75 → 97 on desktop, the screen fills in 3.8 s instead of 4.1 s on mobile and the page weighs 1.4 MB instead of 12 MB.

Still on the site itself: images are not in modern formats or sized to the screen, CSS or JS holds back the first paint, CSS and JS are not minified, and 1 more — listed under “Already on this site” in Speed metrics.

Get this speed for your visitors — WebSpeed Fast, 14 days free. Edit the page code yourself — the report lists the changes.

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, billed yearly
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
  • Schema, sitemap and redirect fixes on request
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). After it, Fast is billed yearly, and Growth and Custom 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
  • Fast’s changes to your page code, 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.