benjaminmoore.com website review

110 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

Your mobile performance score is 53 (desktop: 61). Pages that score under 90 lose visitors before the first paint.

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

About 465 KiB of JavaScript is downloaded but never used on this page.

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

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

7 third-party services load with your homepage (clarip.com, Wunderkind and Bazaarvoice and others), adding 566 KiB and 383 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

About 129 KiB of CSS is downloaded but never applied on this page.

1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 KiB could be saved by minifying CSS.

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.

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 page becomes fully interactive after 15.4 s. Good is under 3.8 s.

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

The layout shifts by 0.278 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “An earthy orange-brown painted wall with decorative molding…”.

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

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

Your homepage downloads 2.4 MB in 132 requests on a phone: scripts 1.2 MB (62), images 774 KiB (36) and fonts 164 KiB (5). Under 2 MB keeps phones on slow connections fast.

black-paint-wall-art-tree-fall-550x679 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).

13 images further down the page (440 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 elements have a tabindex above 0, which scrambles the keyboard order.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

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

There are 2 <h1> headlines (“Benjamin Moore Paint & Stain” and “Color of the Year 2027”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 72 pages on benjaminmoore.com and 9 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/en-us and /en-ca all use the title “Benjamin Moore Paints & Exterior Stains | Benjamin Moore”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /en-us/product/woodluxe-water-based-waterproofing-stain-sealer-sample-translucent-8-oz/CS691, whose canonical is /en-us/product/woodluxe-water-based-waterproofing-stain-sealer-sample-translucent-1-half-pint/CS691. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en-us/store-locator and /en-us/paint-colors/betty have no <h1> headline, so visitors and search engines get no clear main topic.

/en-us/store-locator and /en-us/paint-colors/betty have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/en-us/contractors took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=28000483&Ver=2&mid=23c6f4bb-9ddc-47a9-a602-f09b68da818a&bo=1&sid=e3852980c5d611f1b547ff253d8a75f5&vid=e3856630c5d611f1a019c70d2c2d982f&vids=1&msclkid=N&pi=918639831&lg.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

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

Large scripts ship without source maps.

15 links from your homepage to your own site are broken, for example https://www.benjaminmoore.com/en-us/digital-accessibility-statement (503).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://benjaminmoore.com goes through 2 redirects before the homepage loads.

3 links go through two or more redirects, for example http://www.facebook.com/benjaminmoorepaints.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

benjaminmoore.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

benjaminmoore.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 9 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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