Checked 24 Sep 2026, 13:23 UTC··
Watch for changes
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.dexe.io
Speed audit for dexe.network
Measured PageSpeed before and after WebSpeed optimization — including the places where our automatic pipeline did not come out ahead.
Measured with WebSpeed on
Mobile · PageSpeed
63
was 79−16
Desktop · PageSpeed
99
was 93+6
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.
5.4s
was 3.2 s+2.2 s
Page weight
2.6MB
was 2.4 MB+12%
We didn’t beat your current setup — so we’ve taken this site on
Our automatic pipeline didn’t find a speed-up worth showing for this page, so it goes to us as a separate job: we work through every site the pipeline can’t speed up by itself. Leave your email and we’ll tell you as soon as we have an improvement for it.
Leave your contact →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 every site we’ve measured
PageSpeedscore, higher is better
Mobile
You
050100
You 79 — in the fastest quarter
Desktop
You
050100
You 93 — in the fastest quarter
Screen filledSpeed Index
Mobile
You
010 s20 s+
You 3.2 s — in the fastest quarter
Desktop
You
05 s10 s+
You 0.8 s — in the fastest quarter
Main contentLCP
Mobile
You
020 s40 s+
You 3.6 s — in the fastest quarter
Desktop
You
05 s10 s+
Fastest quarter ≤ 1.1 s · you 1.2 s
Page weighttransferred
Mobile
You
010 MB20 MB+
Fastest quarter ≤ 1.5 MB · you 2.4 MB
Desktop
You
010 MB20 MB+
Fastest quarter ≤ 1.8 MB · you 2.1 MB
Based on 1177 sites WebSpeed has measured, across every platform, as they are, without our optimization. Updated 25 Sep 2026.
Speed metrics
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 79 | 63 | −16 |
| 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.2 s | 5.0 s | +54% |
| 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 | 3.6 s | 7.0 s | +95% |
| 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 | 3.2 s | 5.4 s | +68% |
| 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 | 250 ms | 30 ms | −88% |
| 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 | 2 ms | 13 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 | 224 ms | 552 ms | +147% |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 140 ms | 17 ms | −88% |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 157 ms | 1.7 s | +1.6 s |
Page weight
loaded during the testNow
2.4 MB
Fast
2.6 MB
HTMLJavaScriptCSSFontsImagesOther
| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 55 | 45 | −10 |
| The page itself, before anything it references. | 117 KB | 119 KB | No change beyond run-to-run noise. |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 151 MB | 9528 KB | −49% |
| Stylesheets downloaded during the test. | 431 KB | 350 KB | +64% |
| Web font files downloaded during the test. | 389 KB | 6182 KB | +104% |
| Images downloaded during the test. Images below the fold may load later, after the test. | 22531 KB | 21531 KB | No change beyond run-to-run noise. |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 16 | 7 | −9 |
| Bytes downloaded from those third-party domains. | 2.3 MB | 2.6 MB | +13% |
Speed
what the visitor sees| Metric | Now | Fast | Δ |
|---|---|---|---|
| PageSpeed scoreblends the five below | 93 | 99 | +6 |
| 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.6 s | −24% |
| 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 | 1.2 s | 0.8 s | −31% |
| 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 | 0.8 s | 0.6 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 | 160 ms | 20 ms | −88% |
| 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.03 | +0.03 |
| 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 | 2 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 | 194 ms | 272 ms | No change beyond run-to-run noise. |
| Time spent downloading the LCP image itself — its weight and the connection.downloading the image | 21 ms | 35 ms | No change beyond run-to-run noise. |
| Time between the resource being ready and the element being painted — blocked by CSS, fonts or scripts.until it is painted | 190 ms | 159 ms | No change beyond run-to-run noise. |
Page weight
loaded during the testNow
2.1 MB
Fast
1.7 MB
HTMLJavaScriptCSSFontsImagesOther
| Metric | Now | Fast | Δ |
|---|---|---|---|
| Files the browser downloaded during the test. | 42 | 32 | −10 |
| The page itself, before anything it references. | 117 KB | 119 KB | No change beyond run-to-run noise. |
| Scripts downloaded during the test. Fewer can mean deferred past the test window, not removed from the site. | 151 MB | 9527 KB | −49% |
| Stylesheets downloaded during the test. | 431 KB | 350 KB | +63% |
| Web font files downloaded during the test. | 389 KB | 6182 KB | +104% |
| Images downloaded during the test. Images below the fold may load later, after the test. | 11276 KB | 10275 KB | No change beyond run-to-run noise. |
| Third-partyother companies’ servers | |||
| Distinct third-party domains the page downloaded from — analytics, chat, embeds, fonts, CDNs. | 16 | 7 | −9 |
| Bytes downloaded from those third-party domains. | 2.1 MB | 1.7 MB | −19% |
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.
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
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
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
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
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.
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
- 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
€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.