The Home Depot

Mobile Usability



Mobile Speed



Last tested: 2017-08-27

Rescan Mobile Usability: 99/100 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 <p id="modalApp"></p> is close to 1 other tap targets.
The tap target <a href="/SpecialBuy/SpecialBuyOfTheDay" class="text-primary normal">View All</a> is close to 1 other tap targets. Mobile Speed: 46/100 Mobile Speed Test Quick Overview

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

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.…ferrer=&mboxVersion=53
Optimize CSS Delivery of the following:
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: (expiration not specified)…lue&cb=lpZonesStaticCB (56 seconds) (5 minutes) (5 minutes)…p?df=2&s=THDMobile&b=1 (10.5 minutes) (20 minutes) (20 minutes) (30 minutes) (60 minutes) (60 minutes)…ase_20170420&Version=2 (60 minutes) (60 minutes) (60 minutes) (2 hours)…b-3ddcb9c5de9a_145.jpg (2 hours)…b-ab4a20c08cf2_145.jpg (2 hours)…5-829b4504a8e1_145.jpg (2 hours) (2 hours) (2 hours) (2 hours)…ecial-buy.js?v=836649a (2 hours) (2 hours)…ount.list.js?v=836649a (2 hours)…analytics.js?v=836649a (2 hours)…h.service.js?v=836649a (2 hours)…uth.modal.js?v=836649a (2 hours)…alidation.js?v=836649a (2 hours)…steration.js?v=836649a (2 hours)…th.signin.js?v=836649a (2 hours)…alidation.js?v=836649a (2 hours)…constants.js?v=836649a (2 hours)…th.helper.js?v=836649a (2 hours)…wordMeter.js?v=836649a (2 hours)…ordToggle.js?v=836649a (2 hours)…analytics.js?v=836649a (2 hours)…st.create.js?v=836649a (2 hours)… (2 hours)…t.service.js?v=836649a (2 hours)…ist.model.js?v=836649a (2 hours)…constants.js?v=836649a (2 hours)…st.helper.js?v=836649a (2 hours)…t.message.js?v=836649a (2 hours)…e.utility.js?v=836649a (2 hours)…ity/modal.js?v=836649a (2 hours)…y/tooltip.js?v=836649a (2 hours)…y/utility.js?v=836649a (2 hours)…dings.amd.js?v=836649a (2 hours)…d-overlay.js?v=836649a (2 hours)…page/Fencing-05-04.jpg (2 hours)…OB-CTA-Shop-Online.gif (2 hours)…/MothersDay-2017-4.jpg (2 hours) (2 hours)…atio-05-04-FW14-15.jpg (2 hours)…Ryobi-Mowers-05-04.jpg (2 hours)…Weber-Grills-05-04.jpg (2 hours)…-gardensoil-visnav.jpg (2 hours)…nue-to-mobile-site.png (2 hours)…load-the-app-white.png (2 hours)…/orange-background.png (2 hours)…get/white-close-ic.png (2 hours) (6.7 hours) (6.7 hours) (6.7 hours) (6.7 hours) (6.7 hours) (6.7 hours) (6.7 hours)
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 141.9KiB (24% reduction).
Compressing…/MothersDay-2017-4.jpg could save 56.5KiB (28% reduction).
Compressing…Weber-Grills-05-04.jpg could save 18.9KiB (23% reduction).
Compressing…-gardensoil-visnav.jpg could save 18.5KiB (21% reduction).
Compressing could save 17.3KiB (25% reduction).
Compressing…Ryobi-Mowers-05-04.jpg could save 15.6KiB (19% reduction).
Compressing…page/Fencing-05-04.jpg could save 12.3KiB (19% reduction).
Compressing…load-the-app-white.png could save 991B (28% reduction).
Compressing…OB-CTA-Shop-Online.gif could save 913B (47% reduction).
Compressing…nue-to-mobile-site.png could save 910B (28% reduction).
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 42% of the final above-the-fold content could be rendered with the full HTML response.
Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 20.2KiB (31% reduction).
Minifying…wordMeter.js?v=836649a could save 2.8KiB (44% reduction) after compression.
Minifying…d-overlay.js?v=836649a could save 1.9KiB (23% reduction) after compression.
Minifying…steration.js?v=836649a could save 1.8KiB (27% reduction) after compression.
Minifying…h.service.js?v=836649a could save 1.4KiB (46% reduction) after compression.
Minifying…uth.modal.js?v=836649a could save 1.3KiB (19% reduction) after compression.
Minifying…ordToggle.js?v=836649a could save 1.2KiB (52% reduction) after compression.
Minifying…dings.amd.js?v=836649a could save 1.1KiB (20% reduction) after compression.
Minifying…alidation.js?v=836649a could save 1KiB (28% reduction) after compression.
Minifying…t.service.js?v=836649a could save 910B (37% reduction) after compression.
Minifying…analytics.js?v=836649a could save 840B (50% reduction) after compression.
Minifying…ount.list.js?v=836649a could save 793B (79% reduction) after compression.
Minifying… could save 787B (28% reduction) after compression.
Minifying…st.create.js?v=836649a could save 740B (35% reduction) after compression.
Minifying…y/tooltip.js?v=836649a could save 711B (43% reduction) after compression.
Minifying…th.signin.js?v=836649a could save 704B (27% reduction) after compression.
Minifying…y/utility.js?v=836649a could save 636B (31% reduction) after compression.
Minifying could save 569B (27% reduction).
Minifying…alidation.js?v=836649a could save 565B (30% reduction) after compression.
Minifying…ity/modal.js?v=836649a could save 540B (33% reduction) after compression.
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 7.5KiB (62% reduction).
Compressing could save 4.1KiB (61% reduction).
Compressing…=Y&bw=412&bh=732&AQE=1 could save 1.6KiB (66% reduction).
Compressing could save 1.3KiB (61% reduction).
Compressing could save 576B (69% reduction).
Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 811B (12% reduction).
Minifying could save 811B (12% reduction) after compression. Mobile Resources

Total Resources142
Number of Hosts50
Static Resources71
JavaScript Resources71
CSS Resources1 Mobile Resource Breakdown