www.wowhead.com speed test — 20 Oct 2026

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

https://www.wowhead.com/

20 October 2026 at 14:11 UTC · Free test · report pt_f69e32654360
Grade
B
80/100
Performance86/100
Structure70/100

9 audit(s) passed, 7 need work

First byte (TTFB)642 msmeasured from this server
Fully loaded2.10 sfirst byte + slowest asset
Requests26document + assets
Page weight893.5 KBcompressed transfer
HTML document41.7 KBgzip
ProtocolHTTP/3nginx
Third-party851.8 KBother hosts

Where the first byte went

  • DNS lookup 60 ms 9%
  • TCP connect 37 ms 6%
  • Server wait 545 ms 85%

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 66% of 4,999 pages tested here642 ms against a median of 448 ms
Page weightheavier than 59% of 4,999 pages tested here893.5 KB against a median of 650.3 KB
Fully loadedslower than 61% of 4,999 pages tested here2.10 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 642 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 893.5 KB over 26 request(s). Javascript files are 95% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 95% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 24 requests
851.8 KB 95%
Other 1 request
19 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 642 ms. Of that, 545 ms was the server thinking and 97 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.

Render-blocking resources

high impact

57 render-blocking resource(s) in the document head (40 script(s), 17 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

The page transfers 893.5 KB across 26 request(s), with the document itself at 41.7 KB.

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

Third-party weight

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: global-core.js (244.0 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

JAVASCRIPTwow.zamimg.com/js/3rd-party/jquery.2.1.3.min.js
1.46 s
JAVASCRIPTwow.zamimg.com/js/generated/game-env.js
1.45 s
JAVASCRIPTwow.zamimg.com/js/WH/News/Filter.js
1.41 s
JAVASCRIPTwow.zamimg.com/js/preamble.js
1.38 s
OTHERpixel.quantserve.com/pixel/p-80xBzMhbKolFI.gif
1.34 s
JAVASCRIPTwow.zamimg.com/js/WH/News/Card/Simple.js
1.29 s
JAVASCRIPTwow.zamimg.com/js/WH/News/PaginationUrls.js
1.29 s
JAVASCRIPTwow.zamimg.com/js/locale/terms/enus.js
1.27 s
JAVASCRIPTcdn.cookielaw.org/scripttemplates/otSDKStub.js
1.25 s
JAVASCRIPTnether.wowhead.com/data/global
1.25 s

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://wow.zamimg.com/js/3rd-party/jquery.2.1.3.min.js?fa3be9bf 3rd partyjavascript2001.46 s28.8 KB
https://wow.zamimg.com/js/generated/game-env.js?e5c1729e 3rd partyjavascript2001.45 s93 B
https://wow.zamimg.com/js/WH/News/Filter.js?6183476e 3rd partyjavascript2001.41 s2.0 KB
https://wow.zamimg.com/js/preamble.js?066f8967 3rd partyjavascript2001.38 s651 B
https://pixel.quantserve.com/pixel/p-80xBzMhbKolFI.gif?labels=_fp.event.Default 3rd partyother4051.34 s19 B
https://wow.zamimg.com/js/WH/News/Card/Simple.js?203ce52d 3rd partyjavascript2001.29 s1.4 KB
https://wow.zamimg.com/js/WH/News/PaginationUrls.js?932f8c00 3rd partyjavascript2001.29 s244 B
https://wow.zamimg.com/js/locale/terms/enus.js?6476e082 3rd partyjavascript2001.27 s46.4 KB
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js 3rd partyjavascript2001.25 s13.6 KB
https://nether.wowhead.com/data/global?dv=86&db=1791976965&versionsSig=df36d39008961fdbc42c06c7bf235699 3rd partyjavascript2001.25 s70.8 KB
https://nether.wowhead.com/menus/root?hash=ff731ef0448078943c046137c68fa554 3rd partyjavascript2001.24 s4.7 KB
https://wow.zamimg.com/global-strings/live.enus.js?hash=d2yPEwBuluRUXDJmyXpglw 3rd partyjavascript2001.24 s3.6 KB
https://nether.wowhead.com/menus?hash=ff731ef0448078943c046137c68fa554 3rd partyjavascript2001.22 s125.3 KB
https://wow.zamimg.com/js/tooltips.js?1f440611 3rd partyjavascript2001.22 s62.5 KB
https://wow.zamimg.com/js/react/main.32068f54.js 3rd partyjavascript2001.22 s5.0 KB
https://wow.zamimg.com/js/WH/Home/ContentSpotlight.js?16f4aac1 3rd partyjavascript2001.22 s2.2 KB
https://wow.zamimg.com/js/WH/News/PaginationBar.js?b5422dab 3rd partyjavascript2001.22 s698 B
https://wow.zamimg.com/js/WH/News/Card/Thin.js?731f4640 3rd partyjavascript2001.22 s606 B
https://wow.zamimg.com/js/WH/News/NewsList.js?a7327605 3rd partyjavascript2001.22 s542 B
https://wow.zamimg.com/js/WH/News/LoadingHandler.js?75c7a6de 3rd partyjavascript2001.22 s204 B
https://wow.zamimg.com/js/global-core.js?5081ad59 3rd partyjavascript2001.22 s244.0 KB
https://wow.zamimg.com/js/react/vendors-react.80ccf0e8.js 3rd partyjavascript2001.22 s113.2 KB
https://wow.zamimg.com/js/react/vendors-fontawesome.7e553640.js 3rd partyjavascript2001.22 s60.8 KB
https://wow.zamimg.com/js/global-tags.js?5b011ad6 3rd partyjavascript2001.22 s60.2 KB
https://wow.zamimg.com/js/react/runtime.7c6b9a3a.js 3rd partyjavascript2001.22 s4.2 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.