Website review, no card needed
arthur.fr website review
Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 87 checks
This review found 36 issues worth fixing on arthur.fr, 17 of them high impact, across 87 checks. The most urgent: avoid multiple page redirects. 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
76C- #71,954 of 117,726 reviewed websitesbeats 34%
- #46,468 of 66,937 online storesbeats 26%
- #44,085 of 61,033 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 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 | 151 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 185 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 182 ms |
| Aug 1, 2026 | 181 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 210 ms |
| Oct 3, 2026 | 207 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 184 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
Speed
Avoid multiple page redirects
25.1 sThe page goes through 1 redirect before it starts loading, costing about 25.1 s. Link and advertise the final URL directly.
Reduce unused JavaScript
6.9 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.
Render-blocking requests
1.3 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 5.2 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 (Google Tag Manager, cloudfront.net and Shopify and others), adding 2.1 MB and 1.4 s of main-thread time.
Use efficient cache lifetimes
200 ms · 755 KiB21 files are served with short cache lifetimes, so returning visitors download them again (755 KiB).
Google Tag Manager adds 503 ms
503 msGoogle Tag Manager costs a phone 503 ms of main-thread work and 323 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 296 ms. During a long task the page ignores taps.
cloudfront.net adds 245 ms
245 mscloudfront.net costs a phone 245 ms of main-thread work and 318 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.
2,750 HTML elements
The page has 2,750 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 150 ms
150 msShopify costs a phone 150 ms of main-thread work and 1.1 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.
Legacy JavaScript
150 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
140 ms · 19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Improve image delivery
75 KiB2 images could be 75 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
6 KiB6 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: 129 ms
129 msYour server sent the HTML in 129 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 11.0 s
11.0 sThe first text or image appears after 11.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 34.1 s
34.1 sYour largest element takes 34.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 43.8 s
43.8 sThe page becomes fully interactive after 43.8 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 151 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 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 your site (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: 182 ms
182 msReal visitors wait 182 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 318 ms
318 msReal visitors wait 318 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 8.0 MB in 488 requests
8.0 MBYour homepage downloads 8.0 MB in 488 requests on a phone: scripts 4.0 MB (234), images 2.7 MB (37) and other files 782 KiB (125). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
426 KiB3 images are downloaded at several times the size a phone draws them, for example img-8a4d21cc-77b0-4d75-b0f3-1a9a648f0539.jpg at 1,500 px wide, shown at 88 px. Resized copies would save about 426 KiB.
1 image in older formats
1 image (158 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 2.3 g of CO₂ per visit
2.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.27 g of CO₂e: 271.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
48 tap targets too small
48 tap targets are too small or too close together to hit reliably with a finger.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 2 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 (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
171 internal links, 1 external
The homepage links to 171 pages on arthur.fr and 1 external page.
7 checks passed
One H1 headline
Your main headline reads: “ARTHUR | Pyjamas et sous-vêtements”.
Title: 43 characters
Your title is a healthy 43 characters: “ARTHUR | Pyjamas et sous-vêtements – Arthur”.
Canonical URL set
The canonical URL is https://arthur.fr/.
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://arthur.fr/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (774 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://arthur.fr/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://arthur.fr/products/carte-cadeau-arthur is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://arthur.fr/pages/le-guide-de-noel has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=22023829&tm=gtm002&Ver=2&mid=989299e8-e05a-46ad-a8ec-54f55e9d656a&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=ARTHUR%20%7C%20Pyjamas%20et%20sous-v%C3%AAtem.
5 small tap targets
5 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
Missing source maps
Large scripts ship without source maps.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. 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 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 384 words of copy
The homepage carries about 384 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Microsoft Ads, Microsoft Clarity and Pinterest Tag and 1 more (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.
34 cookies set on arrival
34Opening the homepage sets 34 cookies, 1 of them by other companies (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.
48 other companies contacted
Loading the homepage contacts 48 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 arthur.fr, 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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Doofinder Search Discovery · Join Stories · Eg Auto Add To Cart · Sc Easy Redirects · Microsoft Clarity · Iadvize Ai Shopping Assistant · Se Wishlist Engine · Addingwell · Klaviyo Email Marketing Sms · Forms · Syde Sales Genius · cloudfront.net · gorgias.chat · glopal.com · 9gtb.com · baback.co
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
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Founded
- 1983
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on arthur.fr, including 17 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.