pan.pl 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: −11.4 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: −11.4 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: −11.4 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: ≈ 4.4 → 0.47 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.
Lighthouse recording of the original page under real desktop throttling. The right panel replays the same frames at the measured Speed Index ratio (4.2× faster). Cropped to the top 45% of the frame; measured to finish drawing at the same moment as the whole frame.
Fastest quarter 80+ · you 64
Fastest quarter 96+ · you 58
Fastest quarter ≤ 3.4 s · you 7.2 s
Fastest quarter ≤ 0.9 s · you 2.5 s
Fastest quarter ≤ 3.7 s · you 24.2 s
Fastest quarter ≤ 0.9 s · you 4.0 s
Fastest quarter ≤ 1.1 MB · you 8.8 MB
Fastest quarter ≤ 1.3 MB · you 8.7 MB
Based on 2818 WordPress sites WebSpeed has measured, as they are, without our optimization. Updated 8 Nov 2026.
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 64 | 81 | +17 |
| 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 | 2.6 s | 1.4 s | −47% |
| 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 | 24.2 s | 4.7 s | −81% |
| 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 | 7.2 s | 3.9 s | −46% |
| 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 | 110 ms | 40 ms | −64% |
| 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.028 | 0 | −0.03 |
| 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 | 67 ms | 17 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 | 3.8 s | 1.3 s | −66% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 101 ms | 146 ms | No 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 painted | 358 ms | 882 ms | +146% |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 61 | 32 | −29 |
| The page itself, before anything it references. | 148 KB | 135 KB | −28% |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 18596 KB | 12264 KB | −56% |
| Stylesheets downloaded during the test. | 4124 KB | 172 KB | −42% |
| Web font files downloaded during the test. | 3161 KB | 3162 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 337.8 MB | 14438 KB | −95% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 5 | 2 | −3 |
| Bytes downloaded from those third-party domains. | 440 KB | 106 KB | −76% |
What holds the main thread
Lighthouse attribution, lab run| 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. | Now | Fast |
|---|---|---|
| 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 manager | 91 ms | 0 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, unattributed | 130 ms | 39 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 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: −550 ms LCP
- No CSS or JS holds back the first paintMissing
- Static files are cached in the browserMissingLighthouse estimate: −3.4 s LCP
- Main image is in the HTML, not added by a scriptOK
- CSS and JS are minifiedOK
- The page is compressed (gzip or brotli)OK
- Text stays visible while web fonts loadOK
- Admin area
/wp-admin/and/wp-login.phppass through Fast unchanged and are never cached - 2 language versionsEN, PL-PL. Each one is sped up at its own address
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 | 58 | 100 | +42 |
| 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.5 s | 0.3 s | −33% |
| 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 | 4.0 s | 0.8 s | −80% |
| 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 | 2.5 s | 0.6 s | −76% |
| 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 | 90 ms | 50 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.291 | 0 | −0.29 |
| 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 | 55 ms | 16 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 | 3.5 s | 561 ms | −84% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 84 ms | 140 ms | No 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 painted | 350 ms | 119 ms | −66% |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 61 | 34 | −27 |
| The page itself, before anything it references. | 148 KB | 135 KB | −28% |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 18596 KB | 12264 KB | −56% |
| Stylesheets downloaded during the test. | 4124 KB | 172 KB | −42% |
| Web font files downloaded during the test. | 3161 KB | 3162 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 337.8 MB | 161 MB | −87% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 5 | 2 | −3 |
| Bytes downloaded from those third-party domains. | 440 KB | 106 KB | −76% |
What holds the main thread
Lighthouse attribution, lab run| 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. | Now | Fast |
|---|---|---|
| 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 manager | 74 ms | 0 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, unattributed | 119 ms | 52 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 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: −50 ms LCP
- No CSS or JS holds back the first paintMissing
- Static files are cached in the browserMissingLighthouse estimate: −500 ms LCP
- Main image is in the HTML, not added by a scriptOK
- CSS and JS are minifiedOK
- The page is compressed (gzip or brotli)OK
- Text stays visible while web fonts loadOK
- Admin area
/wp-admin/and/wp-login.phppass through Fast unchanged and are never cached - 2 language versionsEN, PL-PL. Each one is sped up at its own address
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 64 → 81 on mobile and 58 → 100 on desktop, the screen fills in 3.9 s instead of 7.2 s on mobile and the page weighs 971 KB instead of 8.8 MB.
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 2 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.
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.