Watch for changes
askbitrix.com 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: −0.3 s on mobile.
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: −0.3 s on mobile.
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: −0.3 s on mobile.
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.
Forecasts, not measurements: measured gains × published studies — tap any underlined label for the source.
Load recording under mobile throttling: original left, WebSpeed Fast right.
You 70 — in the fastest quarter
You 98 — in the fastest quarter
Fastest quarter ≤ 4.3 s · you 5.3 s
Fastest quarter ≤ 1.2 s · you 1.4 s
You 4.8 s — in the fastest quarter
You 0.8 s — in the fastest quarter
You 726 KB — in the fastest quarter
You 726 KB — in the fastest quarter
Based on 1115 sites WebSpeed has measured, across every platform, as they are, without our optimization. Updated 24 Sep 2026.
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 70 | 82 | +12 |
| 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 | 4.2 s | 1.2 s | −71% |
| 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.8 s | 4.5 s | No change beyond run-to-run noise. |
| 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.3 s | 4.3 s | −20% |
| 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 | 0 ms | 0 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 | 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 | 1 ms | 15 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.3 s | 1.3 s | No change beyond run-to-run noise. |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 216 ms | 1.5 s | +1.3 s |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 1.0 s | 19 ms | −98% |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 36 | 34 | No change beyond run-to-run noise. |
| The page itself, before anything it references. | 15 KB | 127 KB | +22 KB |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 17432 KB | 17433 KB | No change beyond run-to-run noise. |
| Stylesheets downloaded during the test. | 1154 KB | 324 KB | −55% |
| Web font files downloaded during the test. | 2118 KB | 4120 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 4115 KB | 9136 KB | +18% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 0 | 0 | No change beyond run-to-run noise. |
| Bytes downloaded from those third-party domains. | 0 KB | 0 KB | No change beyond run-to-run noise. |
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 98 | 100 | +2 |
| 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.8 s | 0.4 s | −43% |
| 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 | 0.8 s | 0.8 s | No change beyond run-to-run noise. |
| 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 | 1.4 s | 0.4 s | −69% |
| 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 | 0 ms | 0 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 | 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 | 1 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.6 s | 147 ms | −91% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 129 ms | 23 ms | −82% |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 80 ms | 91 ms | No change beyond run-to-run noise. |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 36 | 34 | No change beyond run-to-run noise. |
| The page itself, before anything it references. | 15 KB | 127 KB | +22 KB |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 17432 KB | 17433 KB | No change beyond run-to-run noise. |
| Stylesheets downloaded during the test. | 1154 KB | 324 KB | −55% |
| Web font files downloaded during the test. | 2118 KB | 4120 KB | No change beyond run-to-run noise. |
| Images downloaded during the test. Images below the fold may load later, after the test. | 4115 KB | 9136 KB | +18% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 0 | 0 | No change beyond run-to-run noise. |
| Bytes downloaded from those third-party domains. | 0 KB | 0 KB | No change beyond run-to-run noise. |
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.
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
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.
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
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.