Website review, no card needed
lepro.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 92 checks
This review found 42 issues worth fixing on lepro.co.uk, 16 of them high impact, across 92 checks. The most urgent: main-thread work: 14.4 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
75C- #79,785 of 121,612 reviewed websitesbeats 30%
- #50,867 of 68,795 online storesbeats 22%
- #48,056 of 62,685 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 93 ms |
| May 23, 2026 | 93 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 101 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 130 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 133 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
3.8 s
7.6 s
11.4 s
15.2 s
19.0 s
22.8 s
26.6 s
30.4 s
Speed
Main-thread work: 14.4 s
A phone's processor spends 14.4 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,145 HTML elements
The page has 3,145 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 (hcaptcha.com, Clarity and PayPal and others), adding 2.8 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
510 ms · 625 KiBAbout 625 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 510 ms faster on a phone.
hcaptcha.com adds 940 ms
940 mshcaptcha.com costs a phone 940 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.
Use efficient cache lifetimes
400 ms · 341 KiB14 files are served with short cache lifetimes, so returning visitors download them again (341 KiB).
Improve image delivery
350 ms · 320 KiB15 images could be 320 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Clarity adds 517 ms
517 msClarity costs a phone 517 ms of main-thread work and 30 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 281 ms
281 msShopify costs a phone 281 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.
PayPal adds 286 ms
286 msPayPal costs a phone 286 ms of main-thread work and 229 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
50 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
Duplicated JavaScript
15 KiB15 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “lepro black friday sale”.
Time to Interactive: 30.3 s
30.3 sThe page becomes fully interactive after 30.3 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.437
0.437The layout shifts by 0.437 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 677 ms
677 msScripts block taps and scrolling for 677 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 45% slower for real visitors
+45%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 93 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 209 ms
209 msReal visitors wait 209 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.9 MB in 669 requests
6.9 MBYour homepage downloads 6.9 MB in 669 requests on a phone: scripts 2.4 MB (218), images 2.1 MB (84) and other files 1.6 MB (326). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
710 KiB4 images are downloaded at several times the size a phone draws them, for example 50ft.png at 1,500 px wide, shown at 90 px. Resized copies would save about 710 KiB.
An image on the first screen is lazy-loaded
en-TB1-MO.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 2.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 235.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
20 tap targets too small
20 tap targets are too small or too close together to hit reliably with a finger.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 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 (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 138 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (183 characters)
Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.
198 internal links, 10 external
The homepage links to 198 pages on lepro.co.uk and 10 external pages.
6 checks passed
Title: 51 characters
Your title is a healthy 51 characters: “Lepro UK | Smart Lighting | Indoor & Outdoor Lights”.
Canonical URL set
The canonical URL is https://www.lepro.co.uk/.
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.lepro.co.uk/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 (3,356 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.lepro.co.uk/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.lepro.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.lepro.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://www.lepro.co.uk/collections/all, https://www.lepro.co.uk/customer_authentication/redirect, https://www.lepro.co.uk/pages/black-friday-sale, https://www.lepro.co.uk/collections/emergency-outage-lighting, https://www.lepro.co.uk/collections/permanent-outdoor-lights and https://www.lepro.co.uk/collections/led-strip-lights and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.lepro.co.uk/products/lepro-ee1-ai-permanent-outdoor-lights and https://www.lepro.co.uk/products/lepro-tb1-ai-table-lamp-smart-led-lamp-with-music-sync use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://www.lepro.co.uk/collections/all, https://www.lepro.co.uk/customer_authentication/redirect, https://www.lepro.co.uk/pages/black-friday-sale, https://www.lepro.co.uk/collections/desk-lamps, https://www.lepro.co.uk/collections/led-strip-lights and https://www.lepro.co.uk/collections/led-lighting-bulbs and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.lepro.co.uk/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 76 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
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.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Identifier 'LeLazyTool' has already been declared”.
2 checks passed
Tap targets are thumb-sized
134 of 150 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.
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.
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 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.
About 2,684 words of copy
The homepage carries about 2,684 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
25 calls to action
The homepage has 25 calls to action, for example “Start Shopping >”, “Shop Now” and “Shop All”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 79 testimonial or review blocks, 6 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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, 1 of them by other companies (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.
32 other companies contacted
Loading the homepage contacts 32 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 lepro.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geoly Ai Traffic Booster · Judge Me Reviews · Powerful Form Builder · Microsoft Clarity · Impact Com · Pagefly Ai Page Builder · Forms
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
- Analytics
- 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 42 issues on lepro.co.uk, including 19 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.