www.jimdo.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:37 UTC. Grade D (67/100), with the screenshots, the timings and the fixes that matter.

https://www.jimdo.com/

20 October 2026 at 12:37 UTC · Free test · report pt_616fee6970a1

Re-test this page Test your own site

Grade

67/100

Performance63/100

Structure73/100

11 audit(s) passed, 5 need work

First byte (TTFB)726 msmeasured from this server

Fully loaded1.86 sfirst byte + slowest asset

Requests26document + assets

Page weight3.44 MBcompressed transfer

HTML document56.4 KBbr

ProtocolHTTP/3cloudflare

Third-party3.39 MBother hosts

Where the first byte went

DNS lookup 44 ms 6%
TCP connect 9 ms 1%
Server wait 673 ms 93%

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 byteslower than 71% of 4,999 pages tested here726 ms against a median of 448 ms

Page weightheavier than 90% of 4,999 pages tested here3.44 MB against a median of 650.3 KB

Fully loadedslower than 51% of 4,999 pages tested here1.86 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 took 726 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 3.44 MB over 26 request(s). Images files are 98% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
98% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 948 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 138 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Mobile screenshot of www.jimdo.com — **Mobile** 390 × 844 · 154.7 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 paint948 msgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time138 mslong tasks during load

First contentful paint948 msfirst content on screen

Browser page weight2.22 MB152 request(s), scripts included

Failed requests7blocked or unreachable

Largest contentful paint948 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time138 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

3.39 MB 98%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 726 ms. Of that, 673 ms was the server thinking and 53 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Image delivery and format

high impact

3 image(s) over 200 KB and 0 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 3.44 MB across 26 request(s), with the document itself at 56.4 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 3.39 MB 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.

Avoid extra redirects

medium impact

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