www.ontario.ca speed test — 20 Oct 2026

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

https://www.ontario.ca/

20 October 2026 at 15:26 UTC · Free test · report pt_c76e83d39e24
Grade
B
88/100
Performance92/100
Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)452 msmeasured from this server
Fully loaded1.83 sfirst byte + slowest asset
Requests26document + assets
Page weight375.1 KBcompressed transfer
HTML document26.5 KBgzip
ProtocolHTTP/3server not sent
Third-party1.4 KBother hosts

Where the first byte went

  • DNS lookup 52 ms 12%
  • TCP connect 83 ms 18%
  • Server wait 318 ms 70%

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 51% of 4,999 pages tested here452 ms against a median of 448 ms
Page weightlighter than 67% of 4,999 pages tested here375.1 KB against a median of 650.5 KB
Fully loadedfaster than 50% of 4,999 pages tested here1.83 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 452 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 375.1 KB over 26 request(s). Javascript files are 91% 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.
  • The largest element painted at 860 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 98 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.ontario.ca
Mobile 390 × 844 · 514.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 paint860 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time98 mslong tasks during load
First contentful paint860 msfirst content on screen
Browser page weight1.33 MB57 request(s), scripts included
Largest contentful paint860 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time98 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 22 requests
340.5 KB 91%
Images 3 requests
8.1 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 452 ms. Of that, 318 ms was the server thinking and 135 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

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

Cache static assets

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: index.js (264.0 KB)

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

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.

Waterfall

Slowest requests

JAVASCRIPTwww.ontario.ca/libraries/ontario-search-autosuggest/d…
1.38 s
JAVASCRIPTwww.ontario.ca/core/misc/ajax.js
1.31 s
JAVASCRIPTwww.ontario.ca/modules/custom/onesite_datalayer/js/da…
1.31 s
JAVASCRIPTwww.ontario.ca/core/assets/vendor/loadjs/loadjs.min.js
1.31 s
JAVASCRIPTwww.ontario.ca/core/misc/debounce.js
1.31 s
JAVASCRIPTwww.ontario.ca/core/misc/drupal.init.js
1.30 s
JAVASCRIPTwww.ontario.ca/core/misc/announce.js
1.30 s
JAVASCRIPTwww.ontario.ca/core/misc/message.js
1.30 s
JAVASCRIPTwww.ontario.ca/modules/custom/onesite_ontario_search_…
1.29 s
JAVASCRIPTwww.ontario.ca/modules/contrib/google_tag/js/gtag.aja…
1.29 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://www.ontario.ca/libraries/ontario-search-autosuggest/dist/index.js?v=1.xjavascript2001.38 s264.0 KB
https://www.ontario.ca/core/misc/ajax.js?v=11.3.19javascript2001.31 s20.1 KB
https://www.ontario.ca/modules/custom/onesite_datalayer/js/datalayer.js?tmytjdjavascript2001.31 s1.2 KB
https://www.ontario.ca/core/assets/vendor/loadjs/loadjs.min.js?v=4.3.0javascript2001.31 s969 B
https://www.ontario.ca/core/misc/debounce.js?v=11.3.19javascript2001.31 s697 B
https://www.ontario.ca/core/misc/drupal.init.js?v=11.3.19javascript2001.30 s508 B
https://www.ontario.ca/core/misc/announce.js?v=11.3.19javascript2001.30 s1.8 KB
https://www.ontario.ca/core/misc/message.js?v=11.3.19javascript2001.30 s2.7 KB
https://www.ontario.ca/modules/custom/onesite_ontario_search_autosuggest/js/search-autosuggest-config.js?v=1.xjavascript2001.29 s311 B
https://www.ontario.ca/modules/contrib/google_tag/js/gtag.ajax.js?tmytjdjavascript2001.29 s285 B
https://www.ontario.ca/core/assets/vendor/tabbable/index.umd.min.js?v=6.3.0javascript2001.29 s2.6 KB
https://www.ontario.ca/modules/contrib/google_tag/js/gtm.js?tmytjdjavascript2001.28 s576 B
https://www.ontario.ca/themes/ontario_2021/design_system/scripts/back-to-top.js?tmytjdjavascript2001.28 s202 B
https://www.ontario.ca/modules/contrib/google_tag/js/gtag.js?tmytjdjavascript2001.28 s661 B
https://www.ontario.ca/core/assets/vendor/jquery/jquery.min.js?v=4.0.0javascript2001.28 s31.4 KB
https://www.ontario.ca/core/misc/drupal.js?v=11.3.19javascript2001.28 s7.0 KB
https://www.ontario.ca/core/assets/vendor/once/once.min.js?v=1.0.1javascript2001.28 s718 B
https://www.ontario.ca/themes/ontario_2021/js/onesite_language_cookie.jsjavascript2001.28 s398 B
https://www.ontario.ca/core/misc/drupalSettingsLoader.js?v=11.3.19javascript2001.28 s392 B
https://www.ontario.ca/themes/ontario_2021/design_system/scripts/ontario-a11y.js?tmytjdjavascript2001.27 s858 B
https://www.ontario.ca/core/misc/progress.js?v=11.3.19javascript2001.27 s1.9 KB
https://www.ontario.ca/themes/ontario_2021/assets/[email protected]images2001.27 s4.1 KB
https://www.ontario.ca/themes/ontario_2021/assets/ontario-logo--desktop.svgimages2001.26 s2.5 KB
https://www.ontario.ca/themes/ontario_2021/assets/ontario-logo--mobile.svgimages2001.26 s1.4 KB
https://designsystem.ontario.ca/scripts/svgxuse.js 3rd partyjavascript2001.24 s1.4 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.