www.southwest.com speed test — 20 Oct 2026

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

https://www.southwest.com/

20 October 2026 at 13:57 UTC · Free test · report pt_d327a735fddf

Re-test this page Test your own site

Grade

89/100

Performance92/100

Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)405 msmeasured from this server

Fully loaded2.18 sfirst byte + slowest asset

Requests26document + assets

Page weight11.3 KBcompressed transfer

HTML document1.9 KBbr

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 55 ms 14%
TCP connect 45 ms 11%
Server wait 306 ms 76%

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

Page weightlighter than 95% of 4,999 pages tested here11.3 KB against a median of 650.5 KB

Fully loadedslower than 64% of 4,999 pages tested here2.18 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 405 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 11.3 KB over 26 request(s). Html files are 80% of it, so that one type is worth a look on its own.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Html 4 requests

9.0 KB 80%

Javascript 19 requests

380 B 3%

Css 2 requests

40 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 405 ms. Of that, 306 ms was the server thinking and 100 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

7 render-blocking resource(s) in the document head (4 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.

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

HTMLwww.southwest.com/resources/3f653082b2548ff55d184615dd91…

1.77 s

HTMLwww.southwest.com/akam/13/20fe0db3

1.24 s