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

Checked 09 Nov 2026, 08:34 UTC·A fresh check would only show measurement noise. Re-checks open 24 hours after the last one.·
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.

Domains we saw on the page we measured: sharing its brand name, used by its contact address, or linking back to it. We saw a link, not an ownership record.centrium.techSpeed Index, lowest of the last 3 checks, which ranged 2.2–10× · mobile·centriym.ruSpeed Index, desktop, single check

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.

Measured on the live site
Mobile · PageSpeed
40
poor
Desktop · PageSpeed
28
poor

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.

4.7s
Speed Index
Page weight
6.6MB
transferred
The original page at the end of loading in the PageSpeed mobile test

Your page as PageSpeed’s mobile test saw it when loading finished — the original, without WebSpeed Fast.

We can’t compare these two versions of centriym.com

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 →
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 Tilda sites
PageSpeedscore, higher is better
Desktop
050100

Fastest quarter 94+ · you 28

Screen filledSpeed Index
all platforms
Mobile
010 s20 s+

Fastest quarter ≤ 3.7 s · you 4.7 s

Desktop
02.5 s5 s+

Fastest quarter ≤ 1.0 s · you 6.4 s

Main contentLCP
all platforms
Mobile
020 s40 s+

Fastest quarter ≤ 4.4 s · you 11.5 s

Desktop
05 s10 s+

Fastest quarter ≤ 1.0 s · you 10.9 s

Page weighttransferred
all platforms
Mobile
010 MB20 MB+

Fastest quarter ≤ 1.5 MB · you 6.6 MB

Desktop
010 MB20 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 metrics

Speed

what the visitor sees
MetricNowFastΔ
PageSpeed scoreblends the five below40100+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.8s3.0 s1.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.5s11.5 s1.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.4s4.7 s1.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.≤ 200ms1,680 ms70 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.100No 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.ImageTextchanged
Time until the first byte of the HTML arrived.TTFB91 ms30 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 requested1.5 s—
Time spent downloading the LCP image itself — its weight and the connection.downloading the image11 ms—
Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted78 ms173 msNo change beyond run-to-run noise.

Page weight

loaded during the test
Now6.6 MB
Fast788 KB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
Files the browser downloaded during the test.19862−136
The page itself, before anything it references.15296 KB181 KB−73%
Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site.534.5 MB9510 KB−89%
Stylesheets downloaded during the test.241.6 MB—
Web font files downloaded during the test.257 KB4145 KB+154%
Images downloaded during the test. Images below the fold may load later, after the test.60365 KB3842 KB−88%
Third-partyother companies’ servers
Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs.2410−14
Bytes downloaded from those third-party domains.7 MB708 KB−90%

What holds the main thread

Lighthouse attribution, lab run
Now1,712 ms
Fast122 ms
Google CDNgoogle.comFacebookEverything 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
Google CDNThird-party service · CDN1,376 ms0 ms
google.comThird-party service168 ms0 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 · Social91 ms73 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, unattributed77 ms49 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
How Fast handles this site
  • 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
MetricNowFastΔ
PageSpeed scoreblends the five below28—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.8s2.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.5s10.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.4s6.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.≤ 200ms4,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.10—No change beyond run-to-run noise.

Page weight

loaded during the test
Now18.6 MB
HTMLJavaScriptCSSFontsImagesOther
MetricNowFastΔ
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
Now3,831 ms
google.comGoogle CDNEverything 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
google.comThird-party service3,242 ms—
Google CDNThird-party service · CDN589 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
How Fast handles this site
  • 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

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.