Website review, no card needed
mylee.co.uk website review
Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 75 checks
This review found 33 issues worth fixing on mylee.co.uk, 9 of them high impact, across 75 checks. The most urgent: main-thread work: 10.2 s. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 217 ms |
| May 23, 2026 | 220 ms |
| May 30, 2026 | 219 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 243 ms |
| Jul 4, 2026 | 259 ms |
| Jul 11, 2026 | 264 ms |
| Jul 18, 2026 | 265 ms |
| Jul 25, 2026 | 261 ms |
| Aug 1, 2026 | 253 ms |
| Aug 8, 2026 | 255 ms |
| Aug 15, 2026 | 261 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 270 ms |
| Sep 5, 2026 | 271 ms |
| Sep 12, 2026 | 271 ms |
| Sep 19, 2026 | 268 ms |
| Sep 26, 2026 | 273 ms |
| Oct 3, 2026 | 276 ms |
| Oct 10, 2026 | 283 ms |
| Oct 17, 2026 | 295 ms |
| Oct 24, 2026 | 302 ms |
| Oct 31, 2026 | 312 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
Main-thread work: 10.2 s
A phone's processor spends 10.2 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,735 HTML elements
The page has 4,735 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 (Other Google APIs/SDKs, Klaviyo and Yotpo and others), adding 2.3 MB and 1.4 s of main-thread time.
Other Google APIs/SDKs adds 325 ms
325 msOther Google APIs/SDKs costs a phone 325 ms of main-thread work and 743 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.
Klaviyo adds 224 ms
224 msKlaviyo costs a phone 224 ms of main-thread work and 402 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.
Shopify adds 122 ms
122 msShopify costs a phone 122 ms of main-thread work and 427 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 80 ms
80 msYour server sent the HTML in 80 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.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 281 ms
281 msReal visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 217 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user TTFB: 473 ms
473 msReal visitors wait 473 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 539 requests
5.3 MBYour homepage downloads 5.3 MB in 539 requests on a phone: scripts 2.3 MB (173), images 1.2 MB (65) and other files 1.1 MB (239). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Festive_Launch_banner_mobile_1_1.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.5 g of CO₂ per visit
1.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 179.9 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
58 tap targets too small
58 tap targets are too small or too close together to hit reliably with a finger.
46 text elements with low contrast
46 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (9 elements)
Scrollable region must have keyboard access: 9 elements on the page fail this check, rated serious by axe-core.
autocomplete attribute must be used correctly (2 elements)
autocomplete attribute must be used correctly: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
34 links without text
34 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 (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 8 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
281 internal links, 7 external
The homepage links to 281 pages on mylee.co.uk and 7 external pages.
6 checks passed
Meta description: 91 characters
Your meta description is 91 characters: “Shop gel nail polish, kits and accessories at Mylee. Over 250 colours. Exclusive discounts.”.
Title: 37 characters
Your title is a healthy 37 characters: “Mylee: Gel Nail Polish & Kits – Mylee”.
Canonical URL set
The canonical URL is https://mylee.co.uk/.
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://mylee.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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 (1,604 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mylee.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://mylee.co.uk/collections/all, https://mylee.co.uk/policies/shipping-policy and https://mylee.co.uk/pages/kits-comparison have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://mylee.co.uk/pages/kits-comparison has 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 105 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
110 small tap targets
110 of 144 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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 (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 790 words of copy
The homepage carries about 790 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NEW SEASON” and “SHOP APRÈS ALL DAY”.
20 calls to action
The homepage has 20 calls to action, for example “SHOP NEW SEASON”, “SHOP APRÈS ALL DAY” and “SHOP NOW”.
11 short forms
11 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 46 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and TikTok Pixel.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
68 other companies contacted
Loading the homepage contacts 68 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 mylee.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Mw Bundle Builder · Yotpo Loyalty Rewards · Videowise Connect · Klaviyo Email Marketing Sms · Cozy Country Redirect · Attentive · Yotpo Product Reviews · Microsoft Clarity · Tms Prod V 3c482b6 · Hitsy Progress Bar · Mravinsky Data Expert · snapchat.com · cloudfront.net · webmarked.net · sharethis.com · socialsnowball.io · octaneai.com · attn.tv · trustpilot.com · amazonaws.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 | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on mylee.co.uk, including 12 speed issues, 3 SEO issues 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.