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

Measured from the wfix.shop server on 20 October 2026 at 14:06 UTC. Grade A (92/100), with the screenshots, the timings and the fixes that matter.

https://www.joom.com/en

20 October 2026 at 14:06 UTC · Free test · report pt_0387b85b25aa
Grade
A
92/100
Performance94/100
Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)415 msmeasured from this server
Fully loaded1.50 sfirst byte + slowest asset
Requests11document + assets
Page weight323.5 KBcompressed transfer
HTML document2.1 KBbr
ProtocolHTTP/3server not sent
Third-party321.4 KBother hosts

Where the first byte went

  • DNS lookup 82 ms 20%
  • TCP connect 34 ms 8%
  • Server wait 299 ms 72%

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 54% of 4,999 pages tested here415 ms against a median of 449 ms
Page weightlighter than 70% of 4,999 pages tested here323.5 KB against a median of 650.5 KB
Fully loadedfaster than 70% of 4,999 pages tested here1.50 s against a median of 1.84 s
Requestssends fewer requests than 87% of 4,999 pages tested here11 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 415 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 323.5 KB over 11 request(s), which is lean. Javascript files are 99% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 5.10 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • The main thread was blocked for 205 ms, so taps and scrolling wait while scripts run.

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.joom.com
Mobile 390 × 844 · 3.1 KB · page is 844 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 paint5.10 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time205 mslong tasks during load
First contentful paint3.66 sfirst content on screen
Browser page weight4.14 MB222 request(s), scripts included
Failed requests3blocked or unreachable
Largest contentful paint5.10 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time205 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
320.7 KB 99%
Css 1 request
755 B 0%
Html 5 requests
5 B 0%

Transfer size, compressed as sent. 11 request(s) in total, 323.5 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 415 ms. Of that, 299 ms was the server thinking and 116 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.

Third-party weight

medium impact

2 third-party host(s) serve 321.4 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.

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.

Waterfall

Slowest requests

JAVASCRIPTweb-client.joomcdn.net/web-client/bootstrap.66962f2b.js
1.09 s
JAVASCRIPTweb-client.joomcdn.net/web-client/polyfills.2b156a01.js
1.08 s
JAVASCRIPTweb-client.joomcdn.net/web-client/__dynamic__.7f5bb713.js
1.07 s
CSSweb-client.joomcdn.net/web-client/bootstrap.3eb08db3.css
1.06 s
HTMLwww.joom.com/en/ico/apple-touch-icon.png
1.04 s
HTMLwww.joom.com/en/ico/favicon.svg
1.00 s
HTMLwww.joom.com/en/ico/favicon-96x96.png
979 ms
HTMLwww.joom.com/en/ico/favicon.ico
652 ms
HTMLwww.joom.com/en/ico/site.webmanifest
571 ms
JAVASCRIPTwww.googletagmanager.com/gtm.js
450 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://web-client.joomcdn.net/web-client/bootstrap.66962f2b.js 3rd partyjavascript2001.09 s118.5 KB
https://web-client.joomcdn.net/web-client/polyfills.2b156a01.js 3rd partyjavascript2001.08 s5.0 KB
https://web-client.joomcdn.net/web-client/__dynamic__.7f5bb713.js 3rd partyjavascript2001.07 s18.9 KB
https://web-client.joomcdn.net/web-client/bootstrap.3eb08db3.css 3rd partycss2001.06 s755 B
https://www.joom.com/en/ico/apple-touch-icon.pnghtml4041.04 s1 B
https://www.joom.com/en/ico/favicon.svghtml4041.00 s1 B
https://www.joom.com/en/ico/favicon-96x96.pnghtml404979 ms1 B
https://www.joom.com/en/ico/favicon.icohtml404652 ms1 B
https://www.joom.com/en/ico/site.webmanifesthtml404571 ms1 B
https://www.googletagmanager.com/gtm.js?id=GTM-57VG9N7 3rd partyjavascript200450 ms178.3 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.