www.utexas.edu speed test — 20 Oct 2026

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

https://www.utexas.edu/

20 October 2026 at 12:57 UTC · Free test · report pt_9bf3e1f48d9a

Re-test this page Test your own site

Grade

77/100

Performance75/100

Structure79/100

12 audit(s) passed, 4 need work

First byte (TTFB)161 msmeasured from this server

Fully loaded1.27 sfirst byte + slowest asset

Requests26document + assets

Page weight25.57 MBcompressed transfer

HTML document13.2 KBgzip

ProtocolHTTP/3nginx

Third-party1.7 KBother hosts

Where the first byte went

DNS lookup 47 ms 29%
TCP connect 23 ms 14%
Server wait 91 ms 57%

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

Page weightheavier than 99% of 4,999 pages tested here25.57 MB against a median of 650.3 KB

Fully loadedfaster than 84% of 4,999 pages tested here1.27 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 server answered in 161 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 25.57 MB over 26 request(s). Media files are 88% of it, so let video load on demand instead of on first paint.
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 452 ms, inside the 2.5 s Google calls good.
Layout shift is 0.908 (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 186 ms in total, which is not enough to feel.

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.utexas.edu — **Mobile** 390 × 844 · 293.2 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 paint452 msgood is under 2.5 s

Cumulative layout shift0.908under 0.1 is stable

Total blocking time186 mslong tasks during load

First contentful paint452 msfirst content on screen

Browser page weight1.92 MB78 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint452 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.908

Poorgood under 0.1, poor over 0.25

Total blocking time186 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Media 1 request

22.47 MB 88%

Images 16 requests

3.00 MB 12%

Javascript 7 requests

87.1 KB 0%

Html 1 request

92 B 0%

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

Top issues

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

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 25.57 MB across 26 request(s), with the document itself at 13.2 KB.

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

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.