www.mcmaster.ca speed test — 20 Oct 2026

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

https://www.mcmaster.ca/

20 October 2026 at 16:09 UTC · Free test · report pt_cda4c580f70e

Re-test this page Test your own site

Grade

79/100

Performance91/100

Structure62/100

9 audit(s) passed, 7 need work

First byte (TTFB)415 msmeasured from this server

Fully loaded1.28 sfirst byte + slowest asset

Requests26document + assets

Page weight1.32 MBcompressed transfer

HTML document15.4 KBgzip

ProtocolHTTP/2Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k

Third-party44 Bother hosts

Where the first byte went

DNS lookup 65 ms 16%
TCP connect 100 ms 24%
Server wait 250 ms 60%

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 weightheavier than 71% of 4,999 pages tested here1.32 MB against a median of 650.3 KB

Fully loadedfaster than 84% of 4,999 pages tested here1.28 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 415 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.32 MB over 26 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 980 ms, inside the 2.5 s Google calls good.
Layout shift is 0.422 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 42 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.mcmaster.ca — **Mobile** 390 × 844 · 213.3 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 paint980 msgood is under 2.5 s

Cumulative layout shift0.422under 0.1 is stable

Total blocking time42 mslong tasks during load

First contentful paint948 msfirst content on screen

Browser page weight9.14 MB127 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint980 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.422

Poorgood under 0.1, poor over 0.25

Total blocking time42 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

1.31 MB 99%

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

Top issues

Server response time (TTFB)

high impact

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

5 image(s) over 200 KB and 6 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

14 render-blocking resource(s) in the document head (6 script(s), 8 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 1.32 MB across 26 request(s), with the document itself at 15.4 KB.

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

Cache static assets

medium impact

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