vaping101.co.uk website review

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

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

8 third-party services load with your homepage (omnisnippet1.com, Shopify and bonloyalty.com and others), adding 780 KiB and 1.0 s of main-thread time.

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

About 180 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 680 ms faster on a phone.

omnisnippet1.com costs a phone 833 ms of main-thread work and 129 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.

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

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

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

Shopify costs a phone 120 ms of main-thread work and 320 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.

13 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 9.4 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 9.5 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 2.8 MB in 310 requests on a phone: other files 974 KiB (161), images 906 KiB (27) and scripts 730 KiB (101). Under 2 MB keeps phones on slow connections fast.

12 images (1.5 MB) are 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.

elux-banner-mob.webp 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).

6 images further down the page (694 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example ukvia-logo.webp at 2,059 px wide, shown at 100 px. Resized copies would save about 242 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

9 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 on the page fail this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 467 pages on vaping101.co.uk and 21 external pages.

https://vaping101.co.uk/pages/loyalty-program has no meta description, so Google writes the search snippet from whatever text it finds.

https://vaping101.co.uk/pages/loyalty-program and https://vaping101.co.uk/collections/vape-juice-just-in have no <h1> headline, so visitors and search engines get no clear main topic.

https://vaping101.co.uk/collections/best-selling-prefilled-kit took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.lipscore.com/assets/lipscore-v1-2e2951a46c8bf29aa4ba34b7e15ecba509a9e089b6c…”.

Requests the notification permission on page load.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 2,213 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 8 cookies, 1 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.