Website review, no card needed
danielwellington.com website review
Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 86 checks
This review found 35 issues worth fixing on danielwellington.com, 13 of them high impact, across 86 checks. The most urgent: page weight: 21.0 MB in 325 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
77C- #66,230 of 118,374 reviewed websitesbeats 39%
- #43,143 of 67,243 online storesbeats 31%
- #41,083 of 61,313 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 149 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 150 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 184 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 220 ms |
| Oct 3, 2026 | 217 ms |
| Oct 10, 2026 | 217 ms |
| Oct 17, 2026 | 219 ms |
| Oct 24, 2026 | 218 ms |
| Oct 31, 2026 | 220 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
1.1 s
2.3 s
3.4 s
4.5 s
5.6 s
6.8 s
7.9 s
9.0 s
Speed
Render-blocking requests
1.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,170 HTML elements
The page has 3,170 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 (cloudfront.net, Klaviyo and Cookiebot and others), adding 18.2 MB and 1.6 s of main-thread time.
Shopify adds 23 ms
23 msShopify costs a phone 23 ms of main-thread work and 17.0 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.
Improve image delivery
200 ms · 1.1 MB10 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
500 ms · 168 KiB24 files are served with short cache lifetimes, so returning visitors download them again (168 KiB).
cloudfront.net adds 635 ms
635 mscloudfront.net costs a phone 635 ms of main-thread work and 33 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 385 ms
385 msKlaviyo costs a phone 385 ms of main-thread work and 670 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.
Cookiebot adds 369 ms
369 msCookiebot costs a phone 369 ms of main-thread work and 164 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 375 ms. During a long task the page ignores taps.
Reduce unused JavaScript
308 KiBAbout 308 KiB of JavaScript is downloaded but never used on this page.
Duplicated JavaScript
200 ms · 27 KiB27 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
50 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
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
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.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user INP: 234 ms
234 msReal visitors wait 234 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 47% slower for real visitors
+47%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 220 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 623 ms
623 msReal visitors wait 623 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.0 MB in 325 requests
21.0 MBYour homepage downloads 21.0 MB in 325 requests on a phone: media 16.9 MB (3), images 1.4 MB (15) and scripts 1.3 MB (129). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
DW_FW26_ERA_Master_DW00100882_024_DW00100882_DW004019431000x 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).
About 6.0 g of CO₂ per visit
5.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.96 g of CO₂e: 715.8 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
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
139 internal links, 5 external
The homepage links to 139 pages on danielwellington.com and 5 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Daniel Wellington - official online store. Buy silver & gold watches for men and women, jewelry and accessories with an…”.
Title: 55 characters
Your title is a healthy 55 characters: “Daniel Wellington - Watches & Jewelry Online Store | DW”.
Canonical URL set
The canonical URL is https://www.danielwellington.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.danielwellington.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (587 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.danielwellington.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.danielwellington.com/collections/bestsellers/type-watch is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.danielwellington.com/collections/bestsellers and https://www.danielwellington.com/collections/bestsellers/type-watch all use the title “Bestsellers - Watches, Jewellery & Icons | DW”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.danielwellington.com/collections/bestsellers and https://www.danielwellington.com/collections/bestsellers/type-watch use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 106 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
33 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
About 316 words of copy
The homepage carries about 316 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY 2 OR MORE, SAVE 15%” and “SHOP NOW”.
4 calls to action
The homepage has 4 calls to action, for example “BUY 2 OR MORE, SAVE 15%”, “Shop now” and “Shop the new collection”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 danielwellington.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Founded
- 2011
- Headquarters
- Uppsala
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on danielwellington.com, including 21 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.