www.instructure.com speed test — 20 Oct 2026

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

https://www.instructure.com/

20 October 2026 at 12:38 UTC · Free test · report pt_082d52a1bc5d

Re-test this page Test your own site

Grade

73/100

Performance74/100

Structure71/100

11 audit(s) passed, 5 need work

First byte (TTFB)234 msmeasured from this server

Fully loaded1.16 sfirst byte + slowest asset

Requests26document + assets

Page weight4.30 MBcompressed transfer

HTML document35.0 KBgzip

ProtocolHTTP/3nginx

Third-party67.8 KBother hosts

Where the first byte went

DNS lookup 48 ms 21%
TCP connect 47 ms 20%
Server wait 139 ms 59%

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

Page weightheavier than 92% of 4,999 pages tested here4.30 MB against a median of 650.3 KB

Fully loadedfaster than 89% of 4,999 pages tested here1.16 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 234 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 4.30 MB over 26 request(s). Images files are 98% of it, so resize and recompress the largest images before anything else.
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 780 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 340 ms, so taps and scrolling wait while scripts run.

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.

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.instructure.com — **Mobile** 390 × 844 · 40.8 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 paint780 msgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time340 mslong tasks during load

First contentful paint684 msfirst content on screen

Browser page weight4.45 MB269 request(s), scripts included

Failed requests4blocked or unreachable

Largest contentful paint780 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time340 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 20 requests

4.20 MB 98%

Javascript 5 requests

69.3 KB 2%

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

Top issues

Image delivery and format

high impact

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

72 render-blocking resource(s) in the document head (6 script(s), 66 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 4.30 MB across 26 request(s), with the document itself at 35.0 KB.

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

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.

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.instructure.com/core/misc/drupalSettingsLoader.js

930 ms

JAVASCRIPTpages.instructure.com/js/forms2/js/forms2.min.js

922 ms

IMAGESwww.instructure.com/sites/default/files/image/2025-07/bann…

917 ms

IMAGESwww.instructure.com/sites/default/files/image/2021-06/Clea…

908 ms