Website review, no card needed
jimmyfairly.co.uk website review
Visit site (opens in a new tab)Reviewed 16 November 202637 issues · 84 checks
This review found 37 issues worth fixing on jimmyfairly.co.uk, 11 of them high impact, across 84 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
80B- #48,322 of 124,051 reviewed websitesbeats 55%
- #31,935 of 69,761 online storesbeats 48%
- #30,684 of 63,450 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 271 ms |
| Jun 6, 2026 | 268 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 270 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 258 ms |
| Jul 11, 2026 | 253 ms |
| Jul 18, 2026 | 248 ms |
| Jul 25, 2026 | 247 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 238 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 236 ms |
| Sep 5, 2026 | 238 ms |
| Sep 12, 2026 | 234 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 223 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 209 ms |
| Oct 24, 2026 | 209 ms |
| Oct 31, 2026 | 211 ms |
| Nov 7, 2026 | 214 ms |
| Nov 14, 2026 | 216 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.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Reduce unused JavaScript
1.5 s · 716 KiBAbout 716 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
4,495 HTML elements
The page has 4,495 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, cookiefirst.com and Accessibe Accessibility Overlay and others), adding 1.2 MB and 1.1 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 519 ms
519 msGoogle Tag Manager costs a phone 519 ms of main-thread work and 697 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
450 ms · 89 KiB12 files are served with short cache lifetimes, so returning visitors download them again (89 KiB).
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 28 KiBAbout 28 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.
Improve image delivery
105 KiB1 image could be 105 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 635 ms
635 msScripts block taps and scrolling for 635 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 776 ms
776 msReal visitors wait 776 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 271 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 274 requests
4.7 MBYour homepage downloads 4.7 MB in 274 requests on a phone: scripts 2.0 MB (97), images 1.5 MB (55) and other files 993 KiB (103). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.8 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
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.
1 tap target too small
1 tap target is 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Jimmy Fairly”, “Jimmy Fairly” and “Founded in 2010, Jimmy Fairly was built on a visi…”). One clear main headline is easier for people and search engines.
Structured data has 3 problems
Structured data found (BrandRating, OnlineStore, Organization and WebPage) but with 3 problems, for example “OnlineStore: logo is not an absolute URL ("//www.jimmyfairly.com/cdn/shop/files/favicon_jimmy_fairl…”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
130 internal links, 8 external
The homepage links to 130 pages on jimmyfairly.co.uk and 8 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Shop high-quality glasses and sunglasses, designed in France. Jimmy Fairly frames start at $148, prescription lenses in…”.
Title: 60 characters
Your title is a healthy 60 characters: “Jimmy Fairly Paris ©: Eyewear Online and In Store in the USA”.
Canonical URL set
The canonical URL is https://www.jimmyfairly.com/en-us.
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.jimmyfairly.com/sitemap.xml.
AI search readiness
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
llms.txt published
The site publishes https://www.jimmyfairly.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.jimmyfairly.com/en-us/collections/womens-eyeglasses-us and https://www.jimmyfairly.com/en-us/collections/women-eyeglasses all use the title “Women's Eyeglasses | Jimmy Fairly EN”. 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://www.jimmyfairly.com/en-us/pages/nyc, https://www.jimmyfairly.com/en-us/pages/faq-2026 and https://www.jimmyfairly.com/en-us/pages/collection-lab have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.jimmyfairly.com/en-us/collections/womens-eyeglasses-us and https://www.jimmyfairly.com/en-us/collections/women-eyeglasses use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.jimmyfairly.com/en-us/collections/womens-eyeglasses-us, whose canonical is https://www.jimmyfairly.com/en-us/collections/women-eyeglasses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://www.jimmyfairly.com/en-us/pages/nyc, https://www.jimmyfairly.com/en-us/pages/faq-2026, https://www.jimmyfairly.com/en-us/collections/women-giftguide, https://www.jimmyfairly.com/en-us/pages/collection-lab, https://www.jimmyfairly.com/en-us/collections/men-giftguide and https://www.jimmyfairly.com/en-us/products/mens-colored-lenses-us and 1 other 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 32 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.
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
2 broken images
2 images failed to load on a phone, for example https://www.jimmyfairly.com/en-us.
5 small tap targets
5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'defaultView')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 95 words
The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
19 calls to action
The homepage has 19 calls to action, for example “Book an eye test”, “Shop now” and “Women's Sunglasses Shop now”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 6 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
26 other companies contacted
Loading the homepage contacts 26 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 jimmyfairly.co.uk, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · cloudfront.net · noibu.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
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Hiring
- Hiring
- 13 open roles
- Job board
- jazzhr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on jimmyfairly.co.uk, including 13 speed issues, 3 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.