Website review, no card needed
elizabetharden.com website review
Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 80 checks
This review found 28 issues worth fixing on elizabetharden.com, 11 of them high impact, across 80 checks. The most urgent: page weight: 16.3 MB in 409 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82B- #34,648 of 124,051 reviewed websitesbeats 67%
- #22,931 of 69,761 online storesbeats 61%
- #22,142 of 63,450 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 182 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 204 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 198 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 200 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 176 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 173 ms |
| Oct 17, 2026 | 174 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 170 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
How it loaded on a phone
0.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.6 s
5.3 s
6.1 s
Speed
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 4.0 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 (Signyfyd, Shopify and Klaviyo and others), adding 2.3 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Signyfyd adds 970 ms
970 msSignyfyd costs a phone 970 ms of main-thread work and 259 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 635 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 122 KiBAbout 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 256 KiB27 files are served with short cache lifetimes, so returning visitors download them again (256 KiB).
2,307 HTML elements
The page has 2,307 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 154 ms
154 msShopify costs a phone 154 ms of main-thread work and 532 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.
cloudfront.net adds 134 ms
134 mscloudfront.net costs a phone 134 ms of main-thread work and 593 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.
Klaviyo adds 138 ms
138 msKlaviyo costs a phone 138 ms of main-thread work and 322 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
241 KiB8 images could be 241 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
150 ms · 11 KiB11 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 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.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 31.0 s
31.0 sThe page becomes fully interactive after 31.0 s. Good is under 3.8 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Curly hair model with 3 Elizabeth Arden products — Advanced…”.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 719 ms
719 msScripts block taps and scrolling for 719 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 182 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s 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.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 152 ms
152 msReal visitors wait 152 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 762 ms
762 msReal visitors wait 762 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 16.3 MB in 409 requests
16.3 MBYour homepage downloads 16.3 MB in 409 requests on a phone: media 10.5 MB (2), scripts 2.7 MB (157) and images 1.1 MB (42). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (244 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.6 g of CO₂ per visit
4.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.61 g of CO₂e: 552.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Headings skip levels
Headings skip levels (h2 → h5 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. (4 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (169 characters)
Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.elizabetharden.com/sitemap.xml, so Google discovers your pages only by following links.
270 internal links, 19 external
The homepage links to 270 pages on elizabetharden.com and 19 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Elizabeth Arden”.
Title: 53 characters
Your title is a healthy 53 characters: “Skincare, Fragrance, Makeup & Gifts | Elizabeth Arden”.
Canonical URL set
The canonical URL is https://www.elizabetharden.com/.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://www.elizabetharden.com/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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,104 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
1 broken image
1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/VBPU7X/images/27145439-7c82-43ec-882c-da13f2fb6a3a.png.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
32 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 542 words of copy
The homepage carries about 542 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BEST SELLERS” and “SHOP ALL SKINCARE”.
16 calls to action
The homepage has 16 calls to action, for example “SHOP CAPSULES”, “SHOP NEW ARRIVALS” and “Subscribe & Save”.
15 short forms
15 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 1 of them by other companies (measured from a US location before any click).
56 other companies contacted
Loading the homepage contacts 56 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 elizabetharden.com, 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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Klaviyo Email Marketing Sms · Llama Cart Upsells · Yotpo Product Reviews · Upsell Prod · Stape Remix · Social Widget · Narvar Extensions · Zipify Oneclickupsell · signifyd.com · gorgias.chat · global-e.com · amazonaws.com · 9gtb.com
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
Company
- Headquarters
- Miramar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on elizabetharden.com, including 17 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.