lashbase.co.uk website review

About 845 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

25 files are served with short cache lifetimes, so returning visitors download them again (498 KiB).

A phone's processor spends 4.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (FontAwesome CDN, Bold Commerce and Google Tag Manager and others), adding 2.3 MB and 1.6 s of main-thread time.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

FontAwesome CDN costs a phone 568 ms of main-thread work and 179 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.

Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

10 long tasks block the main thread while loading, the longest for 293 ms. During a long task the page ignores taps.

Bold Commerce costs a phone 225 ms of main-thread work and 485 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.

Google Tag Manager costs a phone 182 ms of main-thread work and 327 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 costs a phone 168 ms of main-thread work and 453 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 costs a phone 162 ms of main-thread work and 393 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.

The page has 1,540 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 178 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

2 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

11 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 23.3 s. Good is under 3.8 s.

Visually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 459 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 362 requests on a phone: scripts 2.7 MB (137), images 2.1 MB (29) and other files 1.1 MB (164). Under 2 MB keeps phones on slow connections fast.

4150b4ac-712b-4f9a-91f7-c45e5ceab1ea.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 4150b4ac-712b-4f9a-91f7-c45e5ceab1ea.png at 886 px wide, shown at 250 px. Resized copies would save about 525 KiB.

1 image (1.8 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 tap targets are too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

9 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3 and h2 → h6), which makes the page harder to scan with a screen reader.

Your meta description is 250 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 220 pages on lashbase.co.uk and 17 external pages.

There is no https://lashbase.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://lashbase.co.uk/collections/korean-lash-lift, https://lashbase.co.uk/collections/new-arrivals, https://lashbase.co.uk/collections/most-popular-products, https://lashbase.co.uk/collections/classic and https://lashbase.co.uk/collections/pre-pro-made-fans-trays have no <h1> headline, so visitors and search engines get no clear main topic.

https://lashbase.co.uk/collections/classic 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.

We fetched 15 pages linked from your homepage (of 98 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355008786&Ver=2&mid=80490327-7184-4cce-963f-d2b424db9829&bo=1&sid=dddeb2d0dd9411f1b62dfdd9d47819d8&vid=dddedf80dd9411f189ca79c881eedad6&vids=1&msclkid=N&pi=918639831&l.

8 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

1 image is served at too low a resolution for sharp phone screens.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 260 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.

Opening the homepage sets 23 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.