Website review, no card needed
collectorscage.fr website review
Visit site (opens in a new tab)Reviewed 12 November 202640 issues · 86 checks
This review found 40 issues worth fixing on collectorscage.fr, 12 of them high impact, across 86 checks. The most urgent: page weight: 14.7 MB in 535 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
69D- #108,295 of 126,458 reviewed websitesbeats 12%
- #64,611 of 70,479 online storesbeats 7%
- #59,489 of 63,977 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 3.1 s |
| Nov 7, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 19, 2026 | 242 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 213 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 200 ms |
| Oct 24, 2026 | 200 ms |
| Oct 31, 2026 | 218 ms |
| Nov 7, 2026 | 223 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.2 s
3.2 s
4.3 s
5.4 s
6.5 s
7.5 s
8.6 s
Speed
Main-thread work: 12.5 s
A phone's processor spends 12.5 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 684 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
6,468 HTML elements
The page has 6,468 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 (Google Tag Manager, Klaviyo and Facebook and others), adding 2.8 MB and 2.2 s of main-thread time.
Improve image delivery
100 ms · 908 KiB16 images could be 908 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
600 KiBAbout 600 KiB of JavaScript is downloaded but never used on this page.
Klaviyo adds 305 ms
305 msKlaviyo costs a phone 305 ms of main-thread work and 515 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.
Use efficient cache lifetimes
322 KiB15 files are served with short cache lifetimes, so returning visitors download them again (322 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 295 ms. During a long task the page ignores taps.
Shopify adds 34 ms
34 msShopify costs a phone 34 ms of main-thread work and 1.2 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.
Reduce unused CSS
150 ms · 46 KiBAbout 46 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.
Legacy JavaScript
76 KiBPolyfills for old browsers add 76 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
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: 16 ms
16 msYour server sent the HTML in 16 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.
Time to Interactive: 27.3 s
27.3 sThe page becomes fully interactive after 27.3 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 972 ms
972 msScripts block taps and scrolling for 972 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Charger la vidéo :”.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 240 ms
240 msReal visitors wait 240 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 59% slower for real visitors
+59%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 242 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 544 ms
544 msReal visitors wait 544 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: 14.7 MB in 535 requests
14.7 MBYour homepage downloads 14.7 MB in 535 requests on a phone: media 8.0 MB (1), images 3.7 MB (302) and scripts 2.0 MB (109). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
12 KiB3 images are downloaded at several times the size a phone draws them, for example 480920984_665526589159110_5315042201050759399_n_1.jpg at 450 px wide, shown at 145 px. Resized copies would save about 12 KiB.
2 images in older formats
2 images (189 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 4.2 g of CO₂ per visit
4.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.16 g of CO₂e: 498.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
32 tap targets too small
32 tap targets are too small or too close together to hit reliably with a finger.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
33 links without text
33 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 (20 elements)
Alternative text of images should not be repeated as text: 20 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail 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. (1 element).
1 checks passed
53 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: 53 passed and 7 failed. 6 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 (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
424 internal links, 60 external
The homepage links to 424 pages on collectorscage.fr and 60 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Sacs de Créateur Vintage · 100% Authentiques”.
Title: 63 characters
Your title is a healthy 63 characters: “Sacs de Créateur Vintage · 100% Authentiques – Collector's Cage”.
Canonical URL set
The canonical URL is https://collectorscage.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://collectorscage.fr/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (4,821 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://collectorscage.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
https://collectorscage.fr/pages/about-us-new, https://collectorscage.fr/pages/sustainability-new, https://collectorscage.fr/pages/blog-new, https://collectorscage.fr/pages/jobs-new, https://collectorscage.fr/pages/our-stores-new and https://collectorscage.fr/pages/private-events-new and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://collectorscage.fr/pages/blog-new, whose canonical is https://collectorscage.fr/blogs/guides. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://collectorscage.fr/pages/about-us-new, https://collectorscage.fr/pages/sustainability-new, https://collectorscage.fr/pages/jobs-new, https://collectorscage.fr/pages/our-stores-new, https://collectorscage.fr/pages/private-events-new and https://collectorscage.fr/pages/faq-new and 2 others have 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 149 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
96 small tap targets
96 of 167 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 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,029 words of copy
The homepage carries about 1,029 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop Best Seller”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 530 testimonial or review blocks, 40 customer or partner logos, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
32 cookies set on arrival
32Opening the homepage sets 32 cookies (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.
39 other companies contacted
Loading the homepage contacts 39 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 collectorscage.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Klaviyo Email Marketing Sms · Microsoft Clarity · snapchat.com · gorgias.chat · nfcube.com · loox.io
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on collectorscage.fr, including 22 speed issues, 1 SEO issue 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.