Watch for changes
reftech.io loads faster with WebSpeed
Measured PageSpeed before and after WebSpeed optimization — no plugins, no migration.
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.
From the measured LCP gain: −55.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).
From the measured LCP gain: −55.1 s.
Google / Deloitte (2019): 0.1 s improvement → +8% conversions in retail. Portent: each extra second of load time reduces conversion rate ~4%.
From the measured LCP gain: −55.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.
From the measured page weight: ≈ 15 → 5 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.
Forecasts, not measurements: measured gains × published studies — tap any underlined label for the source.
Your page as PageSpeed’s desktop test saw it when loading finished — the original, without WebSpeed Fast.
Fastest quarter 71+ · you 65
Fastest quarter 92+ · you 65
Fastest quarter ≤ 3.5 s · you 15.4 s
Fastest quarter ≤ 1.0 s · you 5.2 s
Fastest quarter ≤ 4.7 s · you 145.9 s
Fastest quarter ≤ 1.1 s · you 23.8 s
Fastest quarter ≤ 1.5 MB · you 30.1 MB
Fastest quarter ≤ 1.6 MB · you 30.1 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
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 65 | 65 | No change beyond run-to-run noise. |
| 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.8s | 1.1 s | 0.9 s | No 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.5s | 145.9 s | 51.0 s | −65% |
| How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s | 15.4 s | 11.6 s | −24% |
| 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.≤ 200ms | 40 ms | 60 ms | No 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.1 | 0.048 | 0.048 | No 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. | Image | Image | same |
| Time until the first byte of the HTML arrived.TTFB | 2 ms | 14 ms | No 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 requested | 1.4 s | 177 ms | −87% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 2.0 s | 152 ms | −92% |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 369 ms | 952 ms | +158% |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 57 | 51 | −6 |
| The page itself, before anything it references. | 114 KB | 123 KB | No change beyond run-to-run noise. |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 3365 KB | 3365 KB | No change beyond run-to-run noise. |
| Stylesheets downloaded during the test. | 452 KB | 250 KB | No change beyond run-to-run noise. |
| Web font files downloaded during the test. | 25425 KB | 25425 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 1829.3 MB | 149 MB | −69% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 2 | 2 | No change beyond run-to-run noise. |
| Bytes downloaded from those third-party domains. | 430 KB | 430 KB | No change beyond run-to-run noise. |
What holds the main thread
Lighthouse attribution, lab runAlready 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 lazy-loadedHurtsThe main image waits for lazy-loading, which delays the largest paint
- Main image is marked high priorityMissing
- Images are in modern formats and sized to the screenMissingLighthouse estimate: −44.1 s LCP
- No CSS or JS holds back the first paintMissing
- Static files are cached in the browserMissingLighthouse estimate: −143.4 s LCP
- CSS and JS are minifiedMissingLighthouse estimate: −55 KB
- Text stays visible while web fonts loadMissing
- Main image is in the HTML, not added by a scriptOK
- 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| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 65 | 72 | +7 |
| 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.8s | 0.3 s | 0.3 s | No 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.5s | 23.8 s | 8.5 s | −64% |
| How quickly the visible part of the page fills in during load, averaged over time — a lab metric that rewards showing content sooner.≤ 3.4s | 5.2 s | 1.2 s | −77% |
| 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.≤ 200ms | 50 ms | 130 ms | +146% |
| 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.1 | 0.005 | 0 | No 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. | Image | Image | same |
| Time until the first byte of the HTML arrived.TTFB | 2 ms | 13 ms | No 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 requested | 1.8 s | 170 ms | −91% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 1.6 s | 144 ms | −91% |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 330 ms | 216 ms | −35% |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 57 | 52 | No change beyond run-to-run noise. |
| The page itself, before anything it references. | 114 KB | 123 KB | No change beyond run-to-run noise. |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 3365 KB | 3365 KB | No change beyond run-to-run noise. |
| Stylesheets downloaded during the test. | 452 KB | 250 KB | No change beyond run-to-run noise. |
| Web font files downloaded during the test. | 25425 KB | 25425 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 1929.3 MB | 159.2 MB | −69% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 2 | 2 | No change beyond run-to-run noise. |
| Bytes downloaded from those third-party domains. | 430 KB | 430 KB | No change beyond run-to-run noise. |
What holds the main thread
Lighthouse attribution, lab runAlready 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 lazy-loadedHurtsThe main image waits for lazy-loading, which delays the largest paint
- Main image is marked high priorityMissing
- Images are in modern formats and sized to the screenMissingLighthouse estimate: −7.9 s LCP
- No CSS or JS holds back the first paintMissing
- Static files are cached in the browserMissingLighthouse estimate: −24.5 s LCP
- CSS and JS are minifiedMissingLighthouse estimate: −50 ms LCP · −55 KB
- Text stays visible while web fonts loadMissing
- Main image is in the HTML, not added by a scriptOK
- 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
PageSpeed 65 → 72 on desktop, the screen fills in 11.6 s instead of 15.4 s on mobile, the page weighs 10 MB instead of 30.1 MB and the main content appears in 51.0 s instead of 145.9 s on mobile.
Still on the site itself: the main image is lazy-loaded, the main image is not marked high priority, images are not in modern formats or sized to the screen, and 4 more — listed under “Already on this site” in Speed metrics.
Edit the page code yourself — the report lists the changes. Get this speed for your visitors — WebSpeed Fast, 14 days free.
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.
- 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
We connect it for you.
- Everything in Fast, across multiple sites
- Priority cache — your pages stay warm
- Support with a named contact
- One invoice for the whole portfolio
Agencies and multi-site owners.
- 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
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.
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
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.