bloomington.iu.edu speed test — 20 Oct 2026

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

https://bloomington.iu.edu/

20 October 2026 at 13:34 UTC · Free test · report pt_5e704c90718a

Re-test this page Test your own site

Grade

70/100

Performance78/100

Structure59/100

8 audit(s) passed, 8 need work

First byte (TTFB)518 msmeasured from this server

Fully loaded1.64 sfirst byte + slowest asset

Requests26document + assets

Page weight2.42 MBcompressed transfer

HTML document22.6 KBgzip

ProtocolHTTP/2Apache

Third-party1.34 MBother hosts

Where the first byte went

DNS lookup 126 ms 24%
TCP connect 56 ms 11%
Server wait 336 ms 65%

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 57% of 4,999 pages tested here518 ms against a median of 448 ms

Page weightheavier than 85% of 4,999 pages tested here2.42 MB against a median of 650.3 KB

Fully loadedfaster than 61% of 4,999 pages tested here1.64 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 518 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 2.42 MB over 26 request(s). Images files are 95% 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.
56% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.10 s, inside the 2.5 s Google calls good.
Layout shift is 0.361 (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 470 ms, so taps and scrolling wait while scripts run.

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 bloomington.iu.edu — **Mobile** 390 × 844 · 153.9 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 paint1.10 sgood is under 2.5 s

Cumulative layout shift0.361under 0.1 is stable

Total blocking time470 mslong tasks during load

First contentful paint996 msfirst content on screen

Browser page weight4.35 MB171 request(s), scripts included

Failed requests11blocked or unreachable

Largest contentful paint1.10 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.361

Poorgood under 0.1, poor over 0.25

Total blocking time470 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 24 requests

2.30 MB 95%

Javascript 1 request

92.2 KB 4%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 518 ms. Of that, 336 ms was the server thinking and 182 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

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

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

Image delivery and format

medium impact

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

Cache static assets

medium impact

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