WebSpeed

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

Speed up Tilda without rebuilding your pages

You rebuild nothing and you stay on Tilda: traffic routes through WebSpeed with a DNS change, and nothing is installed in the editor. Tilda builds clean pages, then hands the browser a head assembled for every block the editor supports rather than the ones you used. Across 214 Tilda sites the pattern was remarkably consistent, and almost none of it is visible in the editor.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

  • Nothing to install
  • Your site stays where it is
  • Any optimization can be switched off
Screen filled · mobile

How fast 71 Tilda sites fill the screen

Speed Index of the original sites, as they are, without our optimization.

Fastest quarter: 5.0 s or less

Where does yours land? The free check puts your site on this chart.

Updated 24 Sep 2026.

What WebSpeed does on Tilda

Each one is independent and can be switched off for your domain — nothing here is all-or-nothing.

The head stops carrying dead weight

Assets the page does not actually use are dropped, and the ones it does use stop queueing behind them.

Render-blocking resources FCP

Analytics and widgets load after the page is usable

Counters, pixels, chat and callback widgets are held until the page has drawn and the visitor interacts, then run in order — same behaviour, off the critical path.

TBT INP

The first paint stops waiting on CSS

Small stylesheets are inlined and the rest stop blocking, so the browser paints on the first response instead of waiting out a chain of requests.

Critical CSS Render-blocking resources FCP

Connections open before they're needed

The origins your page genuinely uses get their DNS, TCP and TLS work started early, so the fetch itself is all that's left when the browser gets there.

TTFB

The hero image arrives first

The first-screen image — or the background standing in for one — is preloaded at high priority, so the content that defines the page is not queued behind assets nobody can see yet.

LCP SI

Text is readable while fonts load

Fonts are inlined where that helps and given matched fallback metrics, so the page shows its words immediately instead of holding them back invisible.

FCP CLS

Your controls

What stays under your control

An optimization you cannot undo is a risk, not a feature. Each of these is a decision you keep after the site is live on WebSpeed.

  • Switch any optimization off

    Each one is independent. If something doesn't suit your Tilda theme, it can be disabled for your domain alone and everything else keeps working.

  • Keep only what measurably helps

    On a tuned profile we measure each optimization against your own pages and drop the ones that do not earn their place there.

  • Re-check whenever you want

    Your audit page re-runs both measurements on demand, so "did it help" stays a number you can pull rather than a claim you have to take.

  • Turn it off entirely

    WebSpeed sits in front of your site, not inside it. Revert the DNS record and your original site serves again, unchanged — nothing to uninstall.

In progress: a dashboard where you flip these yourself and follow each page's scores over time. Today it is a message to us and we apply it to your domain.

Why Tilda sites are slow

What the filter logs of our Tilda audits recorded, with the count behind each card: a share of sites, or a total of individual fixes where the volume says more.

Measured across 214 Tilda audits · snapshot 2026-10-19

99%of sites

Third-party scripts load eagerly

Every single site we audited. Analytics, pixels, chat widgets and callback services start loading with the page instead of after it, competing for bandwidth and main thread with the content the visitor came for.

4413fixes on 207 sites

The head carries assets the page never uses

Our highest-volume correction on this platform by a wide margin. Tilda's head is assembled to cover every block type the editor offers; a page that uses six of them still pays for the rest in requests and parse time.

100%of sites

Connections to other origins open too late

Tilda serves your page, its own static assets, your fonts and your third parties from different origins. The browser meets each one only when it needs it, then pays for DNS, TCP and TLS before any useful byte moves.

81%of sites

Stylesheets block the first paint

Each block family brings its own stylesheet, and the browser must fetch and parse the whole set before it can paint anything. On a phone that is the difference between a page that draws and one that sits blank.

The research behind these numbers

Worked example

Real results

Measured on real Tilda pages

Stored audits — the original page against the same page served through WebSpeed, on mobile and desktop. Not a demo build: these are the sites as they ship.

Tilda plastcor.ru
Measured with WebSpeed on
Screen filled · mobile
4.2s
was 5.2 s−1.0 s
Page weight
1.3MB
was 1.7 MB−26%
Mobile · PageSpeed
72
was 46+26
Main content (LCP) · mobile
6.7s
was 8.2 s−1.4 s
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +11%Conversion +7%Bounce −12%CO₂ −26%
46 optimizations applied
  • Stripped head assets the page never used
  • Inlined small stylesheets to cut round-trips
  • Inlined @font-face CSS with font-display: swap
  • Deferred third-party scripts & widgets
Tilda crisis-center.ru
Measured with WebSpeed on
Screen filled · mobile
4.3s
was 11.2 s−6.9 s
Page weight
773KB
was 2.5 MB−70%
Mobile · PageSpeed
87
was 56+31
Desktop · PageSpeed
86
was 77+9
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +40%Conversion +30%Bounce −20%CO₂ −70%
47 optimizations applied
  • JavaScript — 28 changes
  • CSS delivery — 16 changes
  • Embeds — 1 change
  • Fonts — 1 change
  • Resource hints — 1 change
Tilda nurini.ru
Measured with WebSpeed on
Screen filled · mobile
2.5s
was 7.4 s−4.9 s
Page weight
571KB
was 12.9 MB−96%
Main content (LCP) · mobile
3.8s
was 9.4 s−5.6 s
Why only this

The rest stayed inside measurement noise.

Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +40%Conversion +16%Bounce −20%CO₂ −96%
50 optimizations applied
  • JavaScript — 28 changes
  • CSS delivery — 20 changes
  • Fonts — 1 change
  • Resource hints — 1 change
Tilda ligandpro.ru
Measured with WebSpeed on
Main content (LCP) · mobile
8.6s
was 12.7 s−4.1 s
Why only this

Only this moved on this check. The rest stayed inside measurement noise, and we do not call noise a win.

Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +26%Conversion +11%Bounce −18%
42 optimizations applied
  • JavaScript — 25 changes
  • CSS delivery — 16 changes
  • Resource hints — 1 change

Real Google Lighthouse audits, original vs. WebSpeed Fast. The filled tiles are measured: the score is shown per device only where it moved beyond the ±5 the audit counts as noise, “screen filled” is Speed Index, and page weight is transferred bytes. The outlined pills are projections from those measurements — not guarantees. Scores are per-page; yours will differ.

Google traffic Core Web Vitals are a Google ranking signal; the biggest lift is leaving the “Poor” zone (score < 50), scaled here by device search share.

Conversion Akamai / SOASTA (2017): a 100 ms delay cost 7% of conversions across ~10 billion retail visits; scaled here to the measured improvement.

Bounce Akamai / SOASTA (2017): a two-second delay raised bounce rate by 103%; scaled to the measured improvement, site-specific.

CO₂ The measured byte reduction at ≈0.15 g per MB per visit (Sustainable Web Design v4) — a model of the network and devices, not a measurement of them.

Why it's worth doing

What a faster Tilda site is worth

SEO Rank ↑ out of the “Poor” band

Search sees a faster page

Core Web Vitals have been a confirmed Google ranking signal since 2021. The biggest win is leaving the "Poor" band, where faster competitors get preferred.

— Google Search Central
Conversion +7% per 100 ms you cut

More visitors finish what they started

Conversion tracks load time closely — on Akamai’s retail numbers a delay of just 100 ms cost 7% of conversions. Shaving seconds is the cheapest funnel work available.

— Akamai / SOASTA, 2017
Bounce ≈ ½ cutting a 2 s delay

Fewer people leave before it loads

Close a two-second gap and bounce rate roughly halves — Akamai measured those same two seconds raising it by 103%. A page that paints early keeps the visit a slow one loses outright.

— Akamai / SOASTA, 2017
CO₂ ≈ 0.15 g saved per MB you cut

Lighter pages, less energy

Transfer weight maps to emissions at roughly 0.15 g of CO₂ per MB. Cutting bytes is the one optimization that shows up on a sustainability report.

— Sustainable Web Design v4

Each figure links to the page that publishes it. The studies measure what delay costs; read here as what speed returns. Industry benchmarks, not a guarantee for a specific site — the per-site numbers are the audits above, and yours is a free check away.

The price of an editor-first head

Tilda has a better reputation for speed than most builders, and it partly earns it: the markup it produces is orderly, and the platform serves it from its own infrastructure. The audits do not contradict that. What they show is a cost that comes from the same design decision that makes Tilda pleasant to use.

The head is built for the editor, not for your page. On 97% of the 214 sites we audited we found head assets the page never used, and it is our highest-volume correction on this platform by a wide margin — more individual fixes than every other Tilda correction we make put together. Tilda has to support every block type in its library; a page that uses a handful of them still receives the scaffolding for the rest.

Third parties are eager on nearly every site. Not most: 212 of the 214. Analytics, pixels, chat and callback widgets begin loading alongside the content rather than after it. This is the one item on the list that is partly yours, not the platform’s, and it is also the one where deferral is nearly free: none of these need to run before the page is drawn.

Why you can’t fix it from inside the editor

Tilda gives you a head-injection field, which is more access than most builders offer. It is genuinely useful and it is also the wrong shape of tool for the biggest item here.

Adding code is not the operation that speeds a page up. The operations that matter are deferring, reordering and dropping things the platform already emitted — and that markup belongs to Tilda. You can add a preload from the head; you cannot remove a stylesheet the block library queued, because by the time your code runs the browser has already met it.

A reverse proxy changes where the work happens instead. Your Tilda site keeps serving the page it always did; WebSpeed receives that page, rewrites its critical path, and hands the result to the visitor. Nothing inside Tilda changes, so there is nothing for a platform update to undo and nothing for your team to relearn.

What you get from the audit

It needs nothing but the URL:

  1. Your score, both devices — mobile and desktop, original vs the WebSpeed-served page.
  2. The individual metrics — LCP, CLS, TBT and the rest, side by side rather than rolled into one number.
  3. What actually changed — the itemised list of optimizations behind the result.
  4. A before/after video of your page loading, if the gain is big enough to see.

Tilda speed — questions

Do I have to move my site off Tilda?

No — that is the point. WebSpeed runs in front of your existing site. You keep the editor, the hosting and your workflow; only what the browser receives changes.

Will publishing from Tilda still work?

Yes. We never modify the site inside the platform. Your team keeps editing and publishing in Tilda exactly as before, and every publish flows through unchanged.

What about members areas, payments and the editor?

The editor runs on tilda.cc, not on your domain, so it never passes through us. On your domain, /members/, /payment/ and the usual sign-in addresses (/login, /account/ and the like) reach Tilda untouched: not cached, not rewritten. A request that carries a session cookie still gets the optimized page, but never one stored in the shared cache.

My Tilda site has a second language. How is that handled?

On Tilda a second language is a separate set of pages, usually under a folder such as /en/ or in its own project on a subdomain. Each of those addresses is a page of its own for us, optimized and cached separately, so one language is never served in place of another.

Can I do this with Tilda's own head code injection instead?

Only a small part of it. Code in Site Settings → Head can add things, such as a preload, but it cannot remove markup Tilda already emitted, which is where the largest single correction on this platform lives. We built a head-only version ourselves and switched it off for that reason: by the time code at the end of the head runs, the browser has already met the stylesheets and scripts that decide how fast the page draws.

Do external services and widgets slow a Tilda site down?

On nearly every site we audited, yes: 212 of 214 started analytics, pixels, chat or callback widgets together with the page, so they competed with the content for bandwidth and the main thread. None of them needs to run before the page is drawn. WebSpeed holds them until the page has drawn or the visitor interacts, then runs them in order. The trade-off: a visitor who leaves in the first seconds without touching the page may not reach your counters.

I moved my custom code to the footer. Is that enough?

It helps the first paint: a script at the end of the page no longer holds back drawing the way one in the head does. It still downloads and runs while the page is loading, though, so it competes with the page for the main thread and still shows up in Total Blocking Time — and a widget loader placed there usually pulls in more scripts of its own. WebSpeed recognises the common counters, pixels and widgets wherever they sit in the page, head or footer.

Will it change how my site looks?

It should not — every optimization here is about when and in what order things load, not about what they are. The audit shows you the before and after so you can check the result yourself before deciding anything.

Do I have to install anything?

No. Traffic is routed through WebSpeed with a DNS change, and nothing is installed in Tilda or anywhere else.

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 popular
SaaS 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
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.

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 audit See 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.

See your own before / after

Paste your URL for a free PageSpeed comparison on mobile and desktop. No signup, about a minute.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Other platforms: WordPress Duda WooCommerce Divi Wix Bitrix Squarespace