www.zillow.com speed test — 20 Oct 2026

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

https://www.zillow.com/

20 October 2026 at 12:29 UTC · Free test · report pt_a315be0607fd

Re-test this page Test your own site

Grade

67/100

Performance65/100

Structure70/100

10 audit(s) passed, 6 need work

First byte (TTFB)475 msmeasured from this server

Fully loaded2.22 sfirst byte + slowest asset

Requests26document + assets

Page weight4.02 MBcompressed transfer

HTML document50.0 KBbr

ProtocolHTTP/3CloudFront

Third-party3.73 MBother hosts

Where the first byte went

DNS lookup 47 ms 10%
TCP connect 12 ms 3%
Server wait 416 ms 88%

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

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

Fully loadedslower than 65% of 4,999 pages tested here2.22 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 475 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 4.02 MB over 26 request(s). Images files are 75% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
93% 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 980 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 2.54 s, 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 www.zillow.com — **Mobile** 390 × 844 · 16.5 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 paint980 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time2.54 slong tasks during load

First contentful paint980 msfirst content on screen

Browser page weight869.3 KB25 request(s), scripts included

Largest contentful paint980 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time2.54 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 8 requests

3.03 MB 75%

Other 3 requests

613.8 KB 15%

Javascript 14 requests

344.4 KB 8%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 475 ms. Of that, 416 ms was the server thinking and 59 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.

Image delivery and format

high impact

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

Total page weight

high impact

The page transfers 4.02 MB across 26 request(s), with the document itself at 50.0 KB.

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

Cache static assets

medium impact

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

Third-party weight

medium impact

3 third-party host(s) serve 3.73 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Waterfall

Slowest requests

OTHERwww.zillow.com/HYx10rg3/xhr/api/v1/collector/noScript…

1.75 s

IMAGESwww.zillowstatic.com/s3/pfs/static/z-logo-default-visual-re…

1.14 s

JAVASCRIPTwww.zillowstatic.com/s3/pfs/core-d900c28bb521cb862406.js

1.13 s