dove.com website review

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

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

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

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

8 third-party services load with your homepage (Adobe Tag Manager, Google Tag Manager and unileversolutions.com and others), adding 3.0 MB and 2.2 s of main-thread time.

About 691 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

18 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

Adobe Tag Manager costs a phone 963 ms of main-thread work and 92 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.

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

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

unileversolutions.com costs a phone 297 ms of main-thread work and 1.6 MB 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.

Google Tag Manager costs a phone 388 ms of main-thread work and 683 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.

Facebook costs a phone 256 ms of main-thread work and 252 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.

6 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need.

Desktop scores 60 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB could be saved by minifying JavaScript.

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.

5 KiB could be saved by minifying CSS.

3 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The first text or image appears after 8.5 s on a phone. Good is under 1.8 s.

Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dove Limited Edition Holiday Treats collection”.

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 261 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 4.6 MB in 331 requests on a phone: scripts 3.0 MB (184), images 724 KiB (44) and fonts 255 KiB (3). Under 2 MB keeps phones on slow connections fast.

148047380.png 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).

1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 116 pages on dove.com and 0 external pages.

The HTML your server sends has 382 of the 778 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /us/en/washing-and-bathing/discover-your-unique-selfcare-routine.html, whose canonical is /us/en/quizzes/discover-your-unique-selfcare-routine.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/us/en/men-care.html, /us/en/baby.html, /us/en/secure/store-locator-where-to-buy.html, /us/en/products.html, /us/en/washing-and-bathing/beauty-bar.html and /us/en/washing-and-bathing/body-wash.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/us/en/washing-and-bathing/discover-your-unique-selfcare-routine.html and /us/en/campaigns/products/beauty-bar-collection.html took over 3 s to send their HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration')”.

Chrome logged issues while loading the page (“Cookie”).

1 image is served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 778 words of visible text.

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

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