Watch for changes
Speed audit for centriym.com
Measured PageSpeed for this page as it stands today. The WebSpeed run loaded different content, so there is no fair comparison to put beside it.
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.

Your page as PageSpeed’s mobile test saw it when loading finished — the original, without WebSpeed Fast.
During this check the WebSpeed version didn’t load the same content as your current page, so the two scores describe different pages. A higher number here says nothing about speed, and we don’t present it as a result. Leave your contact and this page goes to our team: we’ll find out why the content differed and measure again. If a fair comparison shows a speed-up, we’ll write to you.
Notify me of improvements →Fastest quarter 94+ · you 28
Fastest quarter ≤ 3.7 s · you 4.7 s
Fastest quarter ≤ 1.0 s · you 6.4 s
Fastest quarter ≤ 4.4 s · you 11.5 s
Fastest quarter ≤ 1.0 s · you 10.9 s
Fastest quarter ≤ 1.5 MB · you 6.6 MB
Fastest quarter ≤ 1.6 MB · you 18.6 MB
Based on 149 Tilda sites WebSpeed has measured, as they are, without our optimization. Cards marked “all platforms” compare with all 7003 sites we’ve measured, not just Tilda ones. Updated 9 Nov 2026.
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 40 | 100 | +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.8s | 3.0 s | 1.3 s | −57% |
| 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 | 11.5 s | 1.3 s | −89% |
| 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 | 4.7 s | 1.3 s | −73% |
| 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 | 1,680 ms | 70 ms | −96% |
| 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 | Text | changed |
| Time until the first byte of the HTML arrived.TTFB | 91 ms | 30 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.5 s | — | |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 11 ms | — | |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 78 ms | 173 ms | No change beyond run-to-run noise. |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 198 | 62 | −136 |
| The page itself, before anything it references. | 15296 KB | 181 KB | −73% |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 534.5 MB | 9510 KB | −89% |
| Stylesheets downloaded during the test. | 241.6 MB | — | |
| Web font files downloaded during the test. | 257 KB | 4145 KB | +154% |
| Images downloaded during the test. Images below the fold may load later, after the test. | 60365 KB | 3842 KB | −88% |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 24 | 10 | −14 |
| Bytes downloaded from those third-party domains. | 7 MB | 708 KB | −90% |
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 CDNThird-party service · CDN | 1,376 ms | 0 ms |
| google.comThird-party service | 168 ms | 0 ms |
| Facebook Pixel, the ad-tracking script. While the page loads it sets itself up and reads the page, and the browser cannot react to taps meanwhile. Fast does not remove it: tracking keeps working.Third-party service · Social | 91 ms | 73 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 | 77 ms | 49 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: −1.7 s 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
- Signed-in visitorsSign-in link to
/members/signup. A signed-in visitor never gets a page cached for someone else
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 | 28 | — | 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 | 2.1 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 | 10.9 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 | 6.4 s | — | No 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.≤ 200ms | 4,120 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 | — | No change beyond run-to-run noise. |
Page weight
loaded during the test| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 300+ | — | |
| The page itself, before anything it references. | 15424 KB | — | |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 7319 MB | — | |
| Stylesheets downloaded during the test. | 293.4 MB | — | |
| Web font files downloaded during the test. | 571 MB | — | |
| Images downloaded during the test. Images below the fold may load later, after the test. | 74593 KB | — | |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 27 | — | |
| Bytes downloaded from those third-party domains. | 24.6 MB | — | |
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.comThird-party service | 3,242 ms | — |
| Google CDNThird-party service · CDN | 589 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: −150 ms LCP
- Static files are cached in the browserMissingLighthouse estimate: −300 ms LCP
- Text stays visible while web fonts loadMissing
- CSS and JS are minifiedOK
- The page is compressed (gzip or brotli)OK
- Signed-in visitorsSign-in link to
/members/signup. A signed-in visitor never gets a page cached for someone else
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
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.