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 Duda sites without a rebuild

Nothing is installed per site: a DNS change puts WebSpeed in front of the page, so adding a site is a DNS-level change rather than a project. And what it fixes is not what the speed guides tell you to look for — Duda's stylesheets are fine. Across the 154 Duda sites we audited, what held the page back was everything running while it was still drawing.

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 1,134 sites fill the screen

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

Fastest quarter: 4.3 s or less

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

Across every platform we’ve measured — not enough Duda sites yet for a chart of their own. Updated 24 Sep 2026.

What WebSpeed does on Duda

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

Scripts wait until the page has drawn

Inline body scripts and parser-blocking files are held until rendering is done, then run in order. Same behaviour, out of the way of the first paint.

TBT TTI FCP

The first screen gets priority

The hero image — or the CSS background standing in for one — is preloaded at high priority, so the content that defines the page arrives first.

LCP SI

Wasted connections are reclaimed

Resource hints that point at origins the page never uses are dropped, and the ones that matter are added.

TTFB

Off-screen media waits its turn

Background images and images below the fold load as they approach the viewport instead of competing with the first screen.

Lazy loading

The layout stops jumping

Every image gets its true aspect ratio in the markup, so the browser reserves the right box before the file arrives.

CLS

Text is readable while fonts load

Fonts get font-display: swap and 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 Duda 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 Duda sites are slow

From the filter logs of the Duda sites we have audited, not from a checklist. The number on each card is ours: the share of sites, or the count of individual fixes.

Measured across 154 Duda audits · snapshot 2026-10-19

50%of sites

Scripts run while the page is drawing

Inline scripts sitting in the body execute as the browser works through the markup, so rendering stops each time one runs. On a phone that is the difference between a page that paints and one that stalls half-drawn.

76%of sites

The first screen isn't prioritised

The image the visitor is actually waiting for is fetched at the same priority as everything else on the page, so it queues behind assets that are nowhere near the viewport yet.

1683fixes on 129 sites

The page opens connections it never uses

Our highest-volume correction on this platform: preconnect and prefetch hints for origins the page doesn't end up needing. Each one spends connection budget that the resources on the critical path could have had.

1115fixes on 129 sites

Backgrounds and images load eagerly

Duda sites lean on CSS background images, and those load whether or not anyone scrolls to them. Images also arrive without declared dimensions, so text jumps as each one lands.

The research behind these numbers

Worked example

Real results

Measured on real Duda 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.

Duda defineyoultd.com
Measured with WebSpeed on
Screen filled · mobile
5.6s
was 6.0 s−0.4 s
Mobile · PageSpeed
60
was 49+11
Main content (LCP) · mobile
4.2s
was 5.8 s−1.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 ≤ +16%Conversion +8%Bounce −13%
23 optimizations applied
  • Dropped stale resource hints the builder emitted
  • Held inline body scripts until after render
  • Preloaded the hero background image
  • Inlined @font-face CSS with font-display: swap
  • Lazy-loaded images with real aspect-ratio (anti-CLS)
Duda marksissonlaw.com
Measured with WebSpeed on
Page weight
1.3MB
was 1.8 MB−23%
Mobile · PageSpeed
72
was 62+10
Desktop · PageSpeed
78
was 60+18
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 ≤ +17%Conversion +4%Bounce −6%CO₂ −23%
47 optimizations applied
  • Dropped stale resource hints the builder emitted
  • Held inline body scripts until after render
  • Deferred parser-blocking scripts
  • Preloaded the LCP image (fetchpriority: high)
  • Lazy-loaded CSS background images
  • Deferred third-party scripts & widgets
Duda irvplumbing.com
Measured with WebSpeed on
Screen filled · mobile
2.3s
was 9.1 s−6.8 s
Page weight
1.6MB
was 2.8 MB−42%
Main content (LCP) · mobile
4.9s
was 18.8 s−14.0 s
Score not judged here

This run’s score comparison could not be read back.

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₂ −42%
43 optimizations applied
  • Resource hints — 19 changes
  • JavaScript — 15 changes
  • Images — 5 changes
  • Fonts — 3 changes
  • Embeds — 1 change
Duda bransonalpinemountaincoaster.com
Measured with WebSpeed on
Screen filled · mobile
3.2s
was 8.4 s−5.2 s
Page weight
13.1MB
was 14.5 MB−9%
Mobile · PageSpeed
56
was 33+23
Desktop · PageSpeed
67
was 55+12
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₂ −9%
58 optimizations applied
  • Images — 27 changes
  • Resource hints — 21 changes
  • JavaScript — 6 changes
  • Embeds — 3 changes
  • Fonts — 1 change
Duda wnsalt.com
Measured with WebSpeed on
Screen filled · mobile
3.6s
was 4.4 s−0.8 s
Desktop · PageSpeed
95
was 61+34
Main content (LCP) · mobile
5.0s
was 8.7 s−3.8 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 ≤ +35%Conversion +11%Bounce −17%
137 optimizations applied
  • Images — 104 changes
  • Resource hints — 19 changes
  • JavaScript — 10 changes
  • Fonts — 3 changes
  • Embeds — 1 change
Duda apollogeneralcontracting.com
Measured with WebSpeed on
Screen filled · mobile
4.0s
was 5.6 s−1.6 s
Page weight
2.5MB
was 2.7 MB−5%
Mobile · PageSpeed
63
was 51+12
Desktop · PageSpeed
76
was 69+7
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 ≤ +20%Conversion +7%Bounce −12%CO₂ −5%
39 optimizations applied
  • Resource hints — 18 changes
  • Images — 12 changes
  • JavaScript — 6 changes
  • Fonts — 3 changes

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 Duda 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.

What we found across 154 Duda sites

The advice written for Duda is the advice written for every platform: compress your images, limit your fonts, cut down on widgets. Our own numbers moved the argument somewhere else entirely.

Duda’s CSS delivery is good. Stylesheets blocked the first paint on 9% of the 154 sites we audited. The equivalent figure on WordPress is 84%. Whatever else is true, the platform is not shipping you a render-blocking head, and any guide that starts there is solving a problem your site probably doesn’t have.

What we found instead is a different bottleneck with the same effect: the page is busy while it should be drawing. Inline scripts execute mid-render, resource hints spend connection budget on origins that go unused, the hero image waits its turn behind assets nobody can see yet, and background images load whether or not anyone scrolls to them.

None of that is visible in the editor, and none of it is a mistake anyone made. It is what falls out of a template that has to work for every layout, widget and breakpoint the builder supports — plus the widgets you added.

Why you can’t fix it from inside the builder

Duda lets you inject your own code into the page. That’s genuinely useful, and it is also the wrong shape of tool for this job.

Adding code is not the operation that speeds a page up. The operations that matter here are deferring, reordering and dropping things the platform already emits — and that markup belongs to the builder. You can’t defer a script the template inlined, or remove a resource hint you didn’t write. So the advice ends where every guide about hosted builders ends: file a feature request, or rebuild the site somewhere you control.

A reverse proxy changes where the work happens instead. Your Duda 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 the builder changes, so there is nothing for a platform update to undo and nothing for your team to relearn.

How many Duda sites came out ahead

By September 2026 we had a before/after we could verify on 111 Duda sites. The median mobile gain was +7 points, and Speed Index, how quickly the page visibly fills in, came out 1.22× faster.

We count a site as a gain only when mobile goes up and desktop doesn’t lose more than two points. By that rule 66% of the 111 came out ahead. The other side of the same number: on 28% the mobile score went down. We publish it because an average is not a forecast, and because a page that gains on desktop while losing on mobile isn’t a win worth selling, whatever the average says.

What you get from the audit

It takes about a minute and 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 gain.
  4. A before/after video of your page loading, if the gain is big enough to see.

The range above is what we saw across other people’s Duda sites, not a promise about yours. That is the reason the check is free.

Duda speed — questions

Do I have to move my site off Duda?

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

Will my Duda editor still work normally?

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

What about member logins and account pages?

The editor runs in Duda's own dashboard, so it never touches your domain or us. On your domain, the common sign-in and account addresses (/login, /signin, /account/ and the like) are passed through as Duda sends them, never cached or rewritten. A request with a session cookie gets the optimized page but is never answered from the shared cache.

Does it support Duda's multilingual sites?

Yes. Duda serves each added language under its own path prefix, such as /es/, and each of those addresses is optimized and cached separately. A visitor who chose Spanish is never handed the English page out of the cache.

Does this work for agencies with many client sites?

Yes, and that is the common case for Duda. Because there is nothing to install per site, adding a client is a DNS-level change rather than a project. Run a free audit on a couple of client sites first — of the 111 Duda sites we could verify by September 2026, two in three came out ahead on mobile without losing desktop, so seeing your own range matters more than any average.

Duda already advertises good performance. What is left to gain?

Our measurements agree with them on the part they control: stylesheets blocked the first paint on only 9% of the 154 sites we audited, where on WordPress it is one of the two most common. What is left is everything layered on top — scripts running during render, eager backgrounds, an unprioritised first screen. That is where the gains in the audits below come from.

Can you optimize a Duda website?

Yes, from outside the builder. Inside Duda you can add code, but you cannot defer, reorder or drop what the template already emits, and that is where the four bottlenecks above sit. WebSpeed rewrites the page Duda publishes on its way to the visitor. Of the 111 Duda sites we could verify by September 2026, 66% came out ahead on mobile without losing desktop, with a median mobile gain of +7. On 28% the mobile score went down, which is why the free audit measures your own page before anything changes.

How do I improve Duda loading speed without leaving the builder?

You point your domain at WebSpeed and carry on working in Duda. Nothing is installed and nothing inside the site is configured — the page Duda publishes is the page we receive, and what changes is the order and priority in which the browser gets it. The four bottlenecks above are what our filter logs recorded most often across the 154 Duda sites we audited; the free check tells you which of them your own page actually has.

Do I have to install anything?

No. The usual route is the proxy: traffic is routed through WebSpeed with a DNS change and nothing is installed anywhere. If you would rather not route traffic through us, there is an on-site integration we set up together with your developer instead. Same optimizations either way.

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 WooCommerce Divi Wix Tilda Bitrix Squarespace