dewalt.com website review

About 1,008 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 7.2 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (ZenDesk, Curalate and Google Tag Manager and others), adding 1.2 MB and 1.2 s of main-thread time.

10 images could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

16 files are served with short cache lifetimes, so returning visitors download them again (451 KiB).

ZenDesk costs a phone 351 ms of main-thread work and 428 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

20 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.

Curalate costs a phone 280 ms of main-thread work and 270 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,671 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

About 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two workers use DEWALT outdoor tools to clear grass near a …”.

The page becomes fully interactive after 21.9 s. Good is under 3.8 s.

Visually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.5 MB in 163 requests on a phone: scripts 2.6 MB (95), images 614 KiB (25) and other files 600 KiB (23). Under 2 MB keeps phones on slow connections fast.

image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements with visible text labels do not have matching accessible names. (4 elements).

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 85 pages on dewalt.com and 41 external pages.

/en-us/jobsite-solutions/solutions-by-trade/carpentry-solutions and /en-us/jobsite-solutions/solutions-trade/carpentry-solutions all use the title “Carpentry Tools & Solutions | DEWALT”. Search engines can't tell which page to show for a search, so each competes with the others.

/en-us/all-locations and /systems/cordless-platforms/20v/atomic/grinders have no meta description, so Google writes the search snippet from whatever text it finds.

/en-us/jobsite-solutions/solutions-by-trade/carpentry-solutions and /en-us/jobsite-solutions/solutions-trade/carpentry-solutions use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /en-us/jobsite-solutions/solutions-by-trade/outdoor, whose canonical is /en-us/jobsite-solutions/solutions-trade/outdoor. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

9 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,165 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 4 cookies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.