Website review, no card needed
piercingxxl.fr website review
Visit site (opens in a new tab)Reviewed 7 November 202627 issues · 83 checks
This review found 27 issues worth fixing on piercingxxl.fr, 5 of them high impact, across 83 checks. The most urgent: 37 text elements with low contrast. 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
86B- #11,579 of 118,024 reviewed websitesbeats 86%
- #7,107 of 67,072 online storesbeats 85%
- #6,891 of 61,156 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 993 ms |
| Oct 17, 2026 | 980 ms |
| Oct 24, 2026 | 985 ms |
| Oct 31, 2026 | 976 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 134 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 131 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 132 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 119 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
Mobile performance score: 80
80/100Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused JavaScript
300 ms · 259 KiBAbout 259 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
200 ms · 255 KiB13 images could be 255 KiB 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.
Reduce unused CSS
300 ms · 108 KiBAbout 108 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.
2,701 HTML elements
The page has 2,701 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
267 KiB14 files are served with short cache lifetimes, so returning visitors download them again (267 KiB).
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 944 ms 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 (Key CDN, Usercentrics CMP and Trusted Shops and others), adding 698 KiB and 186 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 65 ms
65 msYour server sent the HTML in 65 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Barre Fleur Zircone”.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.103
0.103The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 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.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: 643 ms
643 msReal visitors wait 643 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 353 requests
3.4 MBYour homepage downloads 3.4 MB in 353 requests on a phone: other files 1.3 MB (236), images 1,015 KiB (46) and scripts 917 KiB (55). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → 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. (1 element).
2 checks passed
Every image has alt text
All 57 images in the HTML carry an alt attribute.
50 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: 50 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
415 internal links, 5 external
The homepage links to 415 pages on piercingxxl.fr and 5 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Boutique de piercing PiercingXXL”.
Title: 32 characters
Your title is a healthy 32 characters: “Boutique de Piercing PiercingXXL”.
Canonical URL set
The canonical URL is https://piercingxxl.fr/.
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://piercingxxl.fr/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,430 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://piercingxxl.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages slow to respond
https://piercingxxl.fr/collections/piercing-helix and https://piercingxxl.fr/collections/piercing-nez took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 126 found) and read each the way a search engine does.
7 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 an H1
Each page we checked has a main headline.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
45 of 56 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.
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: 13 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,427 words of copy
The homepage carries about 1,427 words of visible text.
1 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Analytics (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 piercingxxl.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Searchanise Search Filter · Stape Remix · cloudfront.net · trustedshops.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
- 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 piercingxxl.fr, including 12 speed issues, 2 SEO issues and 5 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.