www.callofduty.com speed test — 20 Oct 2026

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

https://www.callofduty.com/

20 October 2026 at 15:10 UTC · Free test · report pt_68ce6d578c32

Re-test this page Test your own site

Grade

72/100

Performance71/100

Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)331 msmeasured from this server

Fully loaded1.45 sfirst byte + slowest asset

Requests26document + assets

Page weight5.11 MBcompressed transfer

HTML document16.8 KBgzip

ProtocolHTTP/2Apache/2.4.6 (CentOS) Communique/4.3.3

Third-party30.6 KBother hosts

Where the first byte went

DNS lookup 58 ms 18%
TCP connect 55 ms 17%
Server wait 218 ms 66%

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 68% of 4,999 pages tested here331 ms against a median of 449 ms

Page weightheavier than 94% of 4,999 pages tested here5.11 MB against a median of 650.3 KB

Fully loadedfaster than 74% of 4,999 pages tested here1.45 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 331 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 5.11 MB over 26 request(s). Other files are 65% of it, so that one type is worth a look on its own.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.

Fix first: Image delivery and format - 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.

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

Other 8 requests

3.32 MB 65%

Images 17 requests

1.77 MB 35%

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

Top issues

Image delivery and format

high impact

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

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (3 script(s), 2 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

high impact

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

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

Cache static assets

medium impact

2 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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.