zillow.com Zillow: Real Estate, Apartments, Mortgages & Home Values

Mobile Usability



Mobile Speed



Last tested: 2017-08-27

zillow.com Mobile Usability: 99/100
zillow.com Mobile Usability Test Quick Overview

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <div id="mobile-upsell-container">Pro tip:Use th…wnload the app</div> is close to 2 other tap targets.
The tap target <a href="https://app.adjust.com/8xcpyi" class="zsg-button_pri…za-track-event">Download the app</a> is close to 1 other tap targets.
The tap target <a id="register_opener_5" href="/myzillow/Upda…add&amp;ajax=false" class="zsg-lightbox-s…n-on-any-click"></a> is close to 1 other tap targets.
zillow.com Mobile Speed: 56/100
zillow.com Mobile Speed Test Quick Overview

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 59% of the final above-the-fold content could be rendered with the full HTML response.
Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://s.yimg.com/wi/ytc.js (expiration not specified)
https://tag.mtrcs.samba.tv/v3/tag/Zillow/Hompage/sambaTag.js (expiration not specified)
https://accounts.google.com/o/oauth2/iframerpc?act….googleusercontent.com (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P6HT97 (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://apis.google.com/js/client:platform.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 25.1KiB (62% reduction).
Compressing https://sync.graph.bluecava.com/js/bc.js could save 24.5KiB (62% reduction).
Compressing https://pixel.mtrcs.samba.tv/v2/tag/Zillow/Hompage…52F%3F&c=1494248850380 could save 526B (74% reduction).
Reduce server response time

zillow.com Mobile Resources

Total Resources100
Number of Hosts41
Static Resources49
JavaScript Resources42
CSS Resources4

zillow.com Mobile Resource Breakdown