Website review, no card needed

moltonbrown.ae logo

moltonbrown.ae website review

Visit site (opens in a new tab)Reviewed 16 November 202638 issues · 83 checks

This review found 38 issues worth fixing on moltonbrown.ae, 17 of them high impact, across 83 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
3.2 s1.9 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.6 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.6 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
249 ms144 msMay 30Nov 14156 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026180 ms
Jun 6, 2026176 ms
Jun 13, 2026178 ms
Jun 20, 2026171 ms
Jun 27, 2026206 ms
Jul 4, 2026208 ms
Jul 11, 2026208 ms
Jul 18, 2026205 ms
Jul 25, 2026199 ms
Aug 1, 2026225 ms
Aug 8, 2026227 ms
Aug 15, 2026227 ms
Aug 22, 2026237 ms
Aug 29, 2026229 ms
Sep 5, 2026227 ms
Sep 12, 2026237 ms
Sep 19, 2026233 ms
Sep 26, 2026213 ms
Oct 3, 2026208 ms
Oct 10, 2026182 ms
Oct 17, 2026187 ms
Oct 24, 2026193 ms
Oct 31, 2026187 ms
Nov 7, 2026177 ms
Nov 14, 2026156 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 moltonbrown.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moltonbrown.ae at 1.2 s1.2 s
  2. moltonbrown.ae at 2.4 s2.4 s
  3. moltonbrown.ae at 3.6 s3.6 s
  4. moltonbrown.ae at 4.8 s4.8 s
  5. moltonbrown.ae at 6.0 s6.0 s
  6. moltonbrown.ae at 7.3 s7.3 s
  7. moltonbrown.ae at 8.5 s8.5 s
  8. moltonbrown.ae at 9.7 s9.7 s

Speed

12 to fix37
  • Reduce unused JavaScript

    1.4 s · 2.9 MB

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

  • powrcdn.com adds 1.6 s

    1.6 s

    powrcdn.com costs a phone 1.6 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • POWr adds 2.0 s

    2.0 s

    POWr costs a phone 2.0 s of main-thread work and 374 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 10.2 s

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

  • Mobile performance score: 37

    37/100

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

  • 3,070 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (POWr, powrcdn.com and Google Tag Manager and others), adding 5.7 MB and 4.7 s of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 2.1 MB

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

  • Improve image delivery

    800 ms · 559 KiB

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

  • Google Tag Manager adds 489 ms

    489 ms

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

  • Render-blocking requests

    500 ms

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

  • Shopify adds 120 ms

    120 ms

    Shopify costs a phone 120 ms of main-thread work and 387 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.

  • Reduce unused CSS

    150 ms · 127 KiB

    About 127 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.

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    27 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.1 s

    15.1 s

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

  • Speed Index: 19.6 s

    19.6 s

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

  • Time to Interactive: 52.8 s

    52.8 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 153 ms

    153 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 792 ms

    792 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 10.0 MB in 431 requests

    10.0 MB

    Your homepage downloads 10.0 MB in 431 requests on a phone: scripts 5.1 MB (117), images 2.2 MB (28) and stylesheets 1.1 MB (48). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    23 KiB

    3 images are downloaded at several times the size a phone draws them, for example 7QSZgI95QZ2x1k0SMnVk_5000x5000-MBC26019-uk-advent-calender-i at 1,024 px wide, shown at 320 px. Resized copies would save about 23 KiB.

  • 1 image in older formats

    1 image (146 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.

  • 5 images below the first screen load straight away

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

  • About 2.8 g of CO₂ per visit

    2.83 g

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

Accessibility

5 to fixGoogle 8492
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 60 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 33 links without text

    33 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), 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. (6 elements).

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8576
  • No H1 headline

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

  • Meta description is long (196 characters)

    Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.moltonbrown.ae/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at moltonbrown.ae/robots.txt, the first file search crawlers ask for.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 288 internal links, 4 external

    The homepage links to 288 pages on moltonbrown.ae and 4 external pages.

3 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Luxury Shower Gels & Fragrances from London | Molton Brown UAE”.

  • Canonical URL set

    The canonical URL is https://www.moltonbrown.ae/.

  • Structured data in place

    Structured data found: FAQPage.

AI search readiness

1 to fix81
  • 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.moltonbrown.ae/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.

1 checks passed
  • Text is in the HTML

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

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://www.moltonbrown.ae/.

  • 8 third-party cookies

    8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame inste…”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “POWr popup(id=38279572) cannot be rendered: The app is not active”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    49 of 55 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

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

  • 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 656 words of copy

    The homepage carries about 656 words of visible text.

4 checks passed
  • 32 calls to action

    The homepage has 32 calls to action, for example “Shop Now”, “Shop By Collection” and “Shop By”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 21 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel (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.

  • 19 cookies set on arrival

    19

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

  • No consent tool detected

    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.

  • 36 other companies contacted

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

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 moltonbrown.ae, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Product Reviews · Langify · Hulk Contact Form Builder · Gift Box Builder · Back In Stock · Powr Popup · Bundle Products By Thimatic · cart-bot.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
10 open roles
Teams
Retail (6), Marketing (2), R&D (1), Sales (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on moltonbrown.ae, including 18 speed issues, 5 SEO issues and 2 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