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

Speed audityesware.comWebflow
Checked 05 Nov 2026, 16:46 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.

yesware.com loads faster with WebSpeed

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

Measured with WebSpeed on
Mobile · PageSpeed
96
was 36+60
Desktop · PageSpeed
76
was 55+21

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.3s
was 8.8 s−5.5 s
Page weight
1.9MB
was 5.6 MB−67%
If your visitors get this speed

From the measured page weight: ≈ 2.8 → 0.93 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
−67%
Original
WebSpeed Fast
0s10s20s30sOriginalFast

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

Lighthouse recording of the original page under real mobile throttling. The right panel replays the same frames at the measured Speed Index ratio (2.7× faster). Played back 3.4× faster than real time — both panels equally.

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 Webflow sites
PageSpeedscore, higher is better
Mobile
050100

Fastest quarter 71+ · you 36

Desktop
050100

Fastest quarter 92+ · you 55

Screen filledSpeed Index
Mobile
010 s20 s+

Fastest quarter ≤ 3.5 s · you 8.8 s

Desktop
02.5 s5 s+

Fastest quarter ≤ 1.0 s · you 2.3 s

Main contentLCP
Mobile
020 s40 s+

Fastest quarter ≤ 4.7 s · you 11.0 s

Desktop
02.5 s5 s+

Fastest quarter ≤ 1.1 s · you 1.4 s

Page weighttransferred
all platforms
Mobile
010 MB20 MB+

Fastest quarter ≤ 1.5 MB · you 5.6 MB

Desktop
010 MB20 MB+

Fastest quarter ≤ 1.6 MB · you 6 MB

Based on 591 Webflow sites WebSpeed has measured, as they are, without our optimization. Cards marked “all platforms” compare with all 6968 sites we’ve measured, not just Webflow ones. Updated 8 Nov 2026.

Speed metrics

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below3696+60
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.4 s1.0 s−60%
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.5s11.0 s1.0 s−91%
How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s8.8 s3.3 s−63%
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.≤ 200ms1,920 ms180 ms−90%
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.030.023No 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.TTFB4 ms16 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 painted2.5 s286 ms−88%

Page weight

loaded during the test
Now5.6 MB
Fast1.9 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.203127−76
The page itself, before anything it references.360 KB230 KB−50%
Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site.723.6 MB32775 KB−79%
Stylesheets downloaded during the test.7116 KB468 KB−42%
Web font files downloaded during the test.9350 KB9360 KBNo change beyond run-to-run noise.
Images downloaded during the test. Images below the fold may load later, after the test.791.1 MB63656 KB−43%
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.4324−19
Bytes downloaded from those third-party domains.5.6 MB1.8 MB−68%

What holds the main thread

Lighthouse attribution, lab run
Now2,298 ms
Fast214 ms
apigateway.coGoogle CDNWistiaEverything else
Time a script kept the browser busy beyond 50 ms per task — the same pieces Lighthouse adds up into Total Blocking Time. While it lasts, taps and clicks wait. Counted on the recorded run, so the total can differ from the simulated TBT above.NowFast
apigateway.coThird-party service687 ms0 ms
Google CDNThird-party service · CDN467 ms0 ms
WistiaThird-party service · Video309 ms113 ms
The site’s own scripts, plugins and services not listed above (each under 50 ms or past the top three), and browser work Lighthouse could not tie to any script.Site’s own code, smaller scripts, unattributed835 ms101 ms

Fast removes nothing: every script still loads and runs, and Fast starts what it safely can after the page is ready to use.

Each number comes from one lab run. A script that ran after the run ended shows 0 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: −700 ms LCP
  • Static files are cached in the browserMissingLighthouse estimate: −1.0 s LCP
  • Text stays visible while web fonts loadMissing
  • CSS and JS are minifiedOK
  • The page is compressed (gzip or brotli)OK

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 below5576+21
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.6 s0.3 s−56%
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 s1.1 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.4s2.3 s0.7 s−70%
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.≤ 200ms2,080 ms530 ms−74%
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.1560.015−0.14
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.TTFB3 ms15 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 requested416 ms255 ms−39%
Time spent downloading the LCP image itself — its weight and the connection.downloading the image26 ms37 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 painted397 ms234 ms−41%

Page weight

loaded during the test
Now6 MB
Fast2.6 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.212135−77
The page itself, before anything it references.360 KB230 KB−50%
Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site.713.9 MB30741 KB−81%
Stylesheets downloaded during the test.7116 KB467 KB−42%
Web font files downloaded during the test.10397 KB9360 KB−9%
Images downloaded during the test. Images below the fold may load later, after the test.881.4 MB72966 KB−34%
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.4425−19
Bytes downloaded from those third-party domains.6.3 MB2.1 MB−67%

What holds the main thread

Lighthouse attribution, lab run
Now2,400 ms
Fast599 ms
apigateway.coGoogle CDNGoogle Tag ManagerEverything else
Time a script kept the browser busy beyond 50 ms per task — the same pieces Lighthouse adds up into Total Blocking Time. While it lasts, taps and clicks wait. Counted on the recorded run, so the total can differ from the simulated TBT above.NowFast
apigateway.coThird-party service770 ms0 ms
Google CDNThird-party service · CDN339 ms0 ms
Google Tag Manager, plus the tags it loads: analytics, ads, chat. Time counts here when it runs inside GTM’s own script. Fast does not remove it: every tag still fires.Third-party service · Tag manager291 ms163 ms
The site’s own scripts, plugins and services not listed above (each under 50 ms or past the top three), and browser work Lighthouse could not tie to any script.Site’s own code, smaller scripts, unattributed1,000 ms436 ms

Fast removes nothing: every script still loads and runs, and Fast starts what it safely can after the page is ready to use.

Each number comes from one lab run. A script that ran after the run ended shows 0 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
  • Main image is in the HTML, not added by a scriptMissing
  • Main image is marked high priorityMissing
  • Images are in modern formats and sized to the screenMissing
  • No CSS or JS holds back the first paintMissing
  • Static files are cached in the browserMissingLighthouse estimate: −200 ms LCP
  • Text stays visible while web fonts loadMissing
  • Main image is not lazy-loadedOK
  • CSS and JS are minifiedOK
  • The page is compressed (gzip or brotli)OK

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 36 → 96 on mobile and 55 → 76 on desktop, the screen fills in 3.3 s instead of 8.8 s on mobile and the page weighs 1.9 MB instead of 5.6 MB.

Still on the site itself: the main image is added by a script, the main image is not marked high priority, images are not in modern formats or sized to the screen, and 3 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.