Website review, no card needed
ahlemeyewear.com website review
Visit site (opens in a new tab)Reviewed 18 October 202629 issues · 78 checks
This review found 29 issues worth fixing on ahlemeyewear.com, 11 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
79C- #56,203 of 126,178 reviewed websitesbeats 50%
- #36,667 of 70,384 online storesbeats 42%
- #35,107 of 63,910 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.1 s |
| May 2, 2026 | 1.1 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 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.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 79 ms |
| May 2, 2026 | 79 ms |
| May 9, 2026 | 77 ms |
| May 16, 2026 | 77 ms |
| May 23, 2026 | 77 ms |
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 73 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 72 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 73 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 71 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 69 ms |
| Aug 29, 2026 | 67 ms |
| Sep 5, 2026 | 69 ms |
| Sep 12, 2026 | 71 ms |
| Sep 19, 2026 | 74 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 77 ms |
| Oct 10, 2026 | 77 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
Reduce unused JavaScript
4.0 s · 682 KiBAbout 682 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
3.7 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.7 s.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Klaviyo and others), adding 1.2 MB and 777 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 81 KiB11 files are served with short cache lifetimes, so returning visitors download them again (81 KiB).
Legacy JavaScript
300 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 274 ms
274 msGoogle Tag Manager costs a phone 274 ms of main-thread work and 326 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.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 133 ms
133 msKlaviyo costs a phone 133 ms of main-thread work and 317 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Reduce unused CSS
130 ms · 35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Improve image delivery
30 KiB2 images could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 7.9 s
7.9 sThe first text or image appears after 7.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 16.8 s
16.8 sYour largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 452 ms
452 msScripts block taps and scrolling for 452 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 79 ms to 77 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-10, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 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.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: 86 ms
86 msReal visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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: 542 ms
542 msReal visitors wait 542 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: 3.1 MB in 226 requests
3.1 MBYour homepage downloads 3.1 MB in 226 requests on a phone: scripts 1.7 MB (70), other files 857 KiB (127) and fonts 289 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.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
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (219 characters)
Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.
30 internal links, 10 external
The homepage links to 30 pages on ahlemeyewear.com and 10 external pages.
6 checks passed
Title: 64 characters
Your title is a healthy 64 characters: “AHLEM - Sunglasses & Optical Handcrafted in France. Shop Online.”.
Canonical URL set
The canonical URL is https://www.ahlemeyewear.com/.
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://www.ahlemeyewear.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (346 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ahlemeyewear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.ahlemeyewear.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.ahlemeyewear.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.ahlemeyewear.com/customer_authentication/redirect and https://www.ahlemeyewear.com/apps/returns have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://www.ahlemeyewear.com/pages/ahlem-collectible, https://www.ahlemeyewear.com/pages/stores, https://www.ahlemeyewear.com/customer_authentication/redirect, https://www.ahlemeyewear.com/products/julien, https://www.ahlemeyewear.com/products/houdon and https://www.ahlemeyewear.com/pages/contact-us and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.ahlemeyewear.com/apps/returns 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 19 found) and read each the way a search engine does.
3 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.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
13 of 16 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 365 words of copy
The homepage carries about 365 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
25 other companies contacted
Loading the homepage contacts 25 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 ahlemeyewear.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on ahlemeyewear.com, including 14 speed issues, 2 SEO issues and 2 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.