www.jedox.com/en speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:47 UTC. Grade C (72/100), with the screenshots, the timings and the fixes that matter.

https://www.jedox.com/en/

20 October 2026 at 13:47 UTC · Free test · report pt_0efd4e298a56

Re-test this page Test your own site

Grade

72/100

Performance64/100

Structure85/100

12 audit(s) passed, 4 need work

First byte (TTFB)319 msmeasured from this server

Fully loaded3.65 sfirst byte + slowest asset

Requests26document + assets

Page weight15.86 MBcompressed transfer

HTML document235.6 KBbr

ProtocolHTTP/3cloudflare

Third-party436.1 KBother hosts

Where the first byte went

DNS lookup 80 ms 25%
TCP connect 2 ms 1%
Server wait 237 ms 74%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 70% of 4,999 pages tested here319 ms against a median of 449 ms

Page weightheavier than 99% of 4,999 pages tested here15.86 MB against a median of 650.3 KB

Fully loadedslower than 87% of 4,999 pages tested here3.65 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte arrived in 319 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 15.86 MB over 26 request(s). Media files are 96% of it, so let video load on demand instead of on first paint.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 772 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.055), so nothing jumps under the reader's cursor.
The main thread was blocked for 113 ms in total, which is not enough to feel.

Fix first: Total page weight - Work through the heaviest assets first: images, then fonts, then third-party scripts.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of www.jedox.com — **Desktop** 1366 × 768 · 319.2 KB · page is 6000 px tall

Mobile screenshot of www.jedox.com — **Mobile** 390 × 844 · 107.6 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint772 msgood is under 2.5 s

Cumulative layout shift0.055under 0.1 is stable

Total blocking time113 mslong tasks during load

First contentful paint664 msfirst content on screen

Browser page weight16.47 MB98 request(s), scripts included

Largest contentful paint772 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.055

Goodgood under 0.1, poor over 0.25

Total blocking time113 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Media 1 request

15.20 MB 96%

Fonts 14 requests

412.5 KB 3%

Css 4 requests

20.5 KB 0%

Images 3 requests

3.2 KB 0%

Transfer size, compressed as sent. 26 request(s) in total, 15.86 MB across all of them.

Top issues

Total page weight

high impact

The page transfers 15.86 MB across 26 request(s), with the document itself at 235.6 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

1 third-party host(s) serve 436.1 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

HTML document size

medium impact

The document transfers 235.6 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.