Website review, no card needed

dulux.co.uk logo

dulux.co.uk website review

Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 84 checks

This review found 41 issues worth fixing on dulux.co.uk, 18 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.6 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
128 ms120 msMay 9Oct 24122 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026125 ms
May 16, 2026125 ms
May 23, 2026125 ms
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026127 ms
Jun 20, 2026127 ms
Jun 27, 2026127 ms
Jul 4, 2026127 ms
Jul 11, 2026127 ms
Jul 18, 2026125 ms
Jul 25, 2026122 ms
Aug 1, 2026121 ms
Aug 8, 2026121 ms
Aug 15, 2026121 ms
Aug 22, 2026122 ms
Aug 29, 2026122 ms
Sep 5, 2026122 ms
Sep 12, 2026122 ms
Sep 19, 2026121 ms
Sep 26, 2026121 ms
Oct 3, 2026121 ms
Oct 10, 2026121 ms
Oct 17, 2026122 ms
Oct 24, 2026122 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of dulux.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dulux.co.uk at 1.0 s1.0 s
  2. dulux.co.uk at 1.9 s1.9 s
  3. dulux.co.uk at 2.9 s2.9 s
  4. dulux.co.uk at 3.8 s3.8 s
  5. dulux.co.uk at 4.8 s4.8 s
  6. dulux.co.uk at 5.7 s5.7 s
  7. dulux.co.uk at 6.7 s6.7 s
  8. dulux.co.uk at 7.6 s7.6 s

Speed

13 to fix22
  • Reduce unused JavaScript

    9.3 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.

  • Use efficient cache lifetimes

    9.2 s · 1.4 MB

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

  • Render-blocking requests

    9.8 s

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

  • Mobile performance score: 22

    22/100

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

  • Main-thread work: 5.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and sprinklr.com and others), adding 2.8 MB and 1.7 s of main-thread time.

  • Reduce unused CSS

    750 ms · 151 KiB

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

  • Google CDN adds 548 ms

    548 ms

    Google CDN costs a phone 548 ms of main-thread work and 1.1 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 adds 586 ms

    586 ms

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

  • Legacy JavaScript

    450 ms · 52 KiB

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

  • 20 long tasks on the main thread

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

  • 2,742 HTML elements

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

  • sprinklr.com adds 144 ms

    144 ms

    sprinklr.com costs a phone 144 ms of main-thread work and 789 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.

  • Improve image delivery

    100 ms · 53 KiB

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

  • Font display

    100 ms

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

  • Chained critical requests

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

  • Forced reflow

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 54 ms

    54 ms

    Your server sent the HTML in 54 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 24.0 s

    24.0 s

    Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “img1”.

  • Time to Interactive: 26.8 s

    26.8 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.162

    0.162

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user INP: 148 ms

    148 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 730 ms

    730 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.6 MB in 75 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 75 requests on a phone: scripts 3.1 MB (19), other files 589 KiB (19) and images 435 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    34 KiB

    1 image is downloaded at several times the size a phone draws it, for example Dulux-Life-is-what-you-paint-it.jpg at 1,900 px wide, shown at 390 px. Resized copies would save about 34 KiB.

  • 1 image in older formats

    1 image (30 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 1.3 g of CO₂ per visit

    1.31 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 8189
  • ARIA attributes must conform to valid names (8 elements)

    ARIA attributes must conform to valid names: 8 elements on the page fail this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (24 elements)

    Elements must only use permitted ARIA attributes: 24 elements on the page fail this check, rated serious by axe-core.

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (6 elements)

    ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • 41 links crawlers can't follow

    41 links have no real href, so search engines can't follow them.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 103 internal links, 21 external

    The homepage links to 103 pages on dulux.co.uk and 21 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Discover a wide range of paints, services, and ideas to help you add a splash of colour to your home. Shop today and fi…”.

  • One H1 headline

    Your main headline reads: “Life is what you paint it”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Dulux Paints - Find The Perfect Paint Colour for You | Dulux”.

  • Canonical URL set

    The canonical URL is https://www.dulux.co.uk/en.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.dulux.co.uk/en/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.dulux.co.uk/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,655 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9678
  • 6 broken images

    6 images failed to load on a phone, for example https://scontent-iad3-1.cdninstagram.com/v/t51.2885-19/364305128_1055808682051176_7524314152654652946_n.jpg?stp=dst-jpg_s200x200&_nc_cat=101&ccb=1-7&_nc_sid=8ae9d6&_nc_ohc=hSzh0hUBVzgAX_PWRa_&_nc_ht=s.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    97 of 110 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No analytics detected

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

  • A 16-field form

    Your longest form asks for 16 fields (0 required). Every extra field lowers completion.

  • No direct contact details

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

  • No risk reducer

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

  • About 336 words of copy

    The homepage carries about 336 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact us”, “Order History” and “Register here”.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 1 customer or partner logo.

Privacy and tracking

  • 1 tracker load before any consent

    1

    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.

  • 6 cookies set on arrival

    6

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

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dulux.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on dulux.co.uk, including 22 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25