Website review, no card needed
louisxviwatches.com website review
Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 86 checks
This review found 26 issues worth fixing on louisxviwatches.com, 10 of them high impact, across 86 checks. The most urgent: render-blocking 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
87B- #8,755 of 126,652 reviewed websitesbeats 90%
- #4,919 of 70,540 online storesbeats 90%
- #4,763 of 64,024 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 157 ms |
| Oct 31, 2026 | 154 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.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.1 s
Speed
Render-blocking requests
4.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,494 HTML elements
The page has 6,494 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, cdn-cookieyes.com and LoyaltyLion and others), adding 1.2 MB and 489 ms of main-thread time.
Improve image delivery
516 KiB14 images could be 516 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 242 ms
242 msShopify costs a phone 242 ms of main-thread work and 755 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.
LoyaltyLion adds 62 ms
62 msLoyaltyLion costs a phone 62 ms of main-thread work and 350 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 JavaScript
150 ms · 176 KiBAbout 176 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 70 KiBAbout 70 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.
Minify JavaScript
150 ms · 3 KiB3 KiB could be saved by minifying JavaScript.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 140 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
16 KiB10 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
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
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 75 ms
75 msYour server sent the HTML in 75 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.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: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 404 ms
404 msScripts block taps and scrolling for 404 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 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: 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 INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 660 ms
660 msReal visitors wait 660 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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 328 requests
5.4 MBYour homepage downloads 5.4 MB in 328 requests on a phone: images 2.0 MB (57), other files 1.6 MB (143) and scripts 960 KiB (108). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (165 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.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
241 internal links, 13 external
The homepage links to 241 pages on louisxviwatches.com and 13 external pages.
8 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “LOUIS XVI watches are Swiss Made. They are equipped with sapphire crystal glass and come with a 5 year international wa…”.
One H1 headline
Your main headline reads: “LOUIS XVI”.
Title: 36 characters
Your title is a healthy 36 characters: “LOUIS XVI Watches | Official Webshop”.
Canonical URL set
The canonical URL is https://www.louisxviwatches.com/en-us.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, ItemList, 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.louisxviwatches.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: 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 (2,714 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.louisxviwatches.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.louisxviwatches.com/collections, whose canonical is https://www.louisxviwatches.com/en-us/collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.louisxviwatches.com/collections, https://www.louisxviwatches.com/en-us/collections/alle-herrenuhren, https://www.louisxviwatches.com/en-us/collections/bestseller, https://www.louisxviwatches.com/en-us/collections/neuheiten, https://www.louisxviwatches.com/en-us/collections/palais-royale-2-0 and https://www.louisxviwatches.com/en-us/collections/palais-royale-automatique and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.louisxviwatches.com/collections and https://www.louisxviwatches.com/en-us/collections/artagnan 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
42 of 49 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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.
About 1,283 words of copy
The homepage carries about 1,283 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Buy now” and “Contact us”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 126 testimonial or review blocks, a star rating and “Over 100,000 satisfied customers”.
Analytics in place
Analytics detected: Hotjar.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager, Klaviyo and TikTok Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 louisxviwatches.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Moose Whatsapp · T Lab Ai Translate · Klaviyo Email Marketing Sms · Judge Me Reviews · Uppromote Affiliate · Loyalty Rewards And Referrals · Smart Seo · Moosedesk Whatsapp · Content Translation · Affliate By Secomapp · Frontend · Boo Eu Withdrawal Button · covet.pics · addons.business · shareasale.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
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Zürich
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on louisxviwatches.com, including 13 speed issues, 1 SEO issue 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.