Website review, no card needed
all-eyezonme.com website review
Visit site (opens in a new tab)Reviewed 11 November 202636 issues · 79 checks
This review found 36 issues worth fixing on all-eyezonme.com, 8 of them high impact, across 79 checks. The most urgent: 2 linked pages are broken. 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
81B- #42,133 of 126,508 reviewed websitesbeats 61%
- #27,679 of 70,497 online storesbeats 54%
- #26,647 of 63,990 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 957 ms |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 946 ms |
| Jun 27, 2026 | 950 ms |
| Jul 4, 2026 | 980 ms |
| Jul 11, 2026 | 938 ms |
| Jul 18, 2026 | 908 ms |
| Jul 25, 2026 | 866 ms |
| Aug 1, 2026 | 908 ms |
| Aug 8, 2026 | 915 ms |
| Aug 15, 2026 | 894 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 113 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.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
400 ms · 493 KiB19 images could be 493 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Render-blocking requests
800 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
7 third-party services on the page
7 third-party services load with your homepage (Shopify, loox.io and Snapchat and others), adding 613 KiB and 520 ms of main-thread time.
Shopify adds 230 ms
230 msShopify costs a phone 230 ms of main-thread work and 418 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 892 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,411 HTML elements
The page has 2,411 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 232 ms. During a long task the page ignores taps.
Reduce unused JavaScript
159 KiBAbout 159 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
47 KiB8 files are served with short cache lifetimes, so returning visitors download them again (47 KiB).
Reduce unused CSS
27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
1 checks passed
Server response: 36 ms
36 msYour server sent the HTML in 36 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.9 s
9.9 sThe page becomes fully interactive after 9.9 s. Good is under 3.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
5 checks passed
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 102 ms
102 msScripts block the page for only 102 ms while loading. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 262 requests
3.5 MBYour homepage downloads 3.5 MB in 262 requests on a phone: images 1.8 MB (71), other files 859 KiB (125) and scripts 729 KiB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
15_5425b6aa-a144-4d2d-86be-b9e90cd1d544.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
60 links without text
60 visible links have no text or label, so screen readers cannot say where they go.
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 (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 94 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
116 internal links, 8 external
The homepage links to 116 pages on all-eyezonme.com and 8 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “All Eyez on Me - Lunettes de Soleil en édition limitée depuis 2017 ! Des Paires uniques inspirées du rap et de la stree…”.
Title: 37 characters
Your title is a healthy 37 characters: “Lunettes de Soleil en édition limitée”.
Canonical URL set
The canonical URL is https://all-eyezonme.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://all-eyezonme.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 (784 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://all-eyezonme.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://all-eyezonme.com/pages/contactez-nous and https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/week, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://all-eyezonme.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://all-eyezonme.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/ovni and https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/coachella all use the title “COACHELLA - Lunettes All Eyez on Me”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://all-eyezonme.com/customer_authentication/redirect, https://all-eyezonme.com/apps/help-center and https://all-eyezonme.com/pages/avis-clients have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/ovni and https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/coachella use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://all-eyezonme.com/collections/lunettes-all-eyezonme-collection-ss23/products/ovni, whose canonical is https://all-eyezonme.com/products/ovni. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://all-eyezonme.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://all-eyezonme.com/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
Best practices
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 “Refused to apply style from 'https://all-eyezonme.com/cdn/shop/t/39/assets/theme.scss.css?v=6579' because its MIME type…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
90 of 101 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 588 words of copy
The homepage carries about 588 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “CONTACT”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
22 other companies contacted
Loading the homepage contacts 22 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 all-eyezonme.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Countdown Timer · Slide Cart · loox.io · klaviyo.com · snapchat.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
- Framework
- jQuery
- 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 36 issues on all-eyezonme.com, including 10 speed issues, 2 SEO issues 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.