Website review, no card needed
armorlux.com website review
Visit site (opens in a new tab)Reviewed 26 October 202627 issues · 84 checks
This review found 27 issues worth fixing on armorlux.com, 9 of them high impact, across 84 checks. The most urgent: page weight: 5.6 MB in 317 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
89B- #3,646 of 116,857 reviewed websitesbeats 95%
- #1,903 of 66,840 online storesbeats 95%
- #1,847 of 60,969 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 86 ms |
| May 16, 2026 | 84 ms |
| May 23, 2026 | 84 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 91 ms |
| Jul 18, 2026 | 92 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 90 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 84 ms |
| Sep 5, 2026 | 84 ms |
| Sep 12, 2026 | 83 ms |
| Sep 19, 2026 | 83 ms |
| Sep 26, 2026 | 83 ms |
| Oct 3, 2026 | 83 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 84 ms |
| Oct 24, 2026 | 84 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
4,190 HTML elements
The page has 4,190 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 72
72/100Your mobile performance score is 72 (desktop: 88). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
784 KiBAbout 784 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Didomi and wonderpush.com and others), adding 1.4 MB and 486 ms of main-thread time.
Improve image delivery
511 KiB7 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
307 KiB14 files are served with short cache lifetimes, so returning visitors download them again (307 KiB).
Shopify adds 182 ms
182 msShopify costs a phone 182 ms of main-thread work and 696 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
19 KiB19 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
17 KiB17 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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 277 ms
277 msScripts block taps and scrolling for 277 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 86 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 563 ms
563 msReal visitors wait 563 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: 5.6 MB in 317 requests
5.6 MBYour homepage downloads 5.6 MB in 317 requests on a phone: images 2.6 MB (33), scripts 1.7 MB (78) and other files 1.1 MB (193). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (85 KiB) are 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.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 191.7 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
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.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
26 links without text
26 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → 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. (3 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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
644 internal links, 10 external
The homepage links to 644 pages on armorlux.com and 10 external pages.
8 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Armor-Lux, site Officiel | vêtement marin, prêt-à-porter et sous-vêtements - Armor-lux la qualité et l'authenticité dep…”.
One H1 headline
Your main headline reads: “Nos collections de vêtements marins”.
Title: 59 characters
Your title is a healthy 59 characters: “Vêtement marin, prêt-à-porter et sous-vêtements – Armor-lux”.
Canonical URL set
The canonical URL is https://www.armorlux.com/.
Structured data in place
Structured data found: Organization and SiteNavigationElement.
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.armorlux.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 (2,748 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.armorlux.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.armorlux.com/collections/tricot-mariniere-au-metre has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.armorlux.com/collections/pret-a-porter-homme-10004, https://www.armorlux.com/collections/mariniere-homme-10022, https://www.armorlux.com/collections/pull-marin-pull-homme-10020, https://www.armorlux.com/collections/manteau-veste-homme-43360, https://www.armorlux.com/collections/sous-vetements-nuit-homme-43364 and https://www.armorlux.com/collections/accessoires-homme-10008 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.armorlux.com/collections/fr-mariniere-manches-courtes-homme-10082 has 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 159 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.
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
2 broken images
2 images failed to load on a phone, for example https://www.armorlux.com/#.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Didomi - Cannot subscribe to unknown event type "ready"”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
26 of 31 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 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 797 words of copy
The homepage carries about 797 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More →” and “SHOP NOW”.
1 call to action
The homepage has 1 call to action, for example “Contact”.
6 short forms
6 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) 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 armorlux.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on armorlux.com, including 14 speed issues and 1 conversion gap. 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.