Website review, no card needed
vapeverse.co.uk website review
Visit site (opens in a new tab)Reviewed 6 November 202627 issues · 87 checks
This review found 27 issues worth fixing on vapeverse.co.uk, 4 of them high impact, across 87 checks. The most urgent: 23 text elements with low contrast. 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
89B- #3,636 of 116,487 reviewed websitesbeats 95%
- #1,903 of 66,776 online storesbeats 95%
- #1,847 of 60,929 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 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.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 359 ms |
| May 23, 2026 | 369 ms |
| May 30, 2026 | 373 ms |
| Jun 6, 2026 | 377 ms |
| Jun 13, 2026 | 375 ms |
| Jun 20, 2026 | 383 ms |
| Jun 27, 2026 | 398 ms |
| Jul 4, 2026 | 412 ms |
| Jul 11, 2026 | 450 ms |
| Jul 18, 2026 | 435 ms |
| Jul 25, 2026 | 430 ms |
| Aug 1, 2026 | 434 ms |
| Aug 8, 2026 | 421 ms |
| Aug 15, 2026 | 407 ms |
| Aug 22, 2026 | 381 ms |
| Aug 29, 2026 | 378 ms |
| Sep 5, 2026 | 367 ms |
| Sep 12, 2026 | 338 ms |
| Sep 19, 2026 | 308 ms |
| Sep 26, 2026 | 263 ms |
| Oct 3, 2026 | 223 ms |
| Oct 10, 2026 | 221 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 190 ms |
| Oct 31, 2026 | 176 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.7 s
3.3 s
4.0 s
4.7 s
5.3 s
Speed
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 149 KiBAbout 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused JavaScript
150 ms · 358 KiBAbout 358 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and omnisnippet1.com and others), adding 1.2 MB and 313 ms of main-thread time.
Improve image delivery
300 ms · 43 KiB2 images could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,233 HTML elements
The page has 2,233 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 93 ms
93 msShopify costs a phone 93 ms of main-thread work and 821 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
172 KiB16 files are served with short cache lifetimes, so returning visitors download them again (172 KiB).
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.
Minify CSS
14 KiB14 KiB could be saved by minifying CSS.
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: 80 ms
80 msYour server sent the HTML in 80 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 12.3 s
12.3 sThe page becomes fully interactive after 12.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CP Pro CP10K prefilled pod kit – 1000mAh rechargeable batte…”.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 587 ms
587 msReal visitors wait 587 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 50% faster for real visitors
-50%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 359 ms to 176 ms 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.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Total Blocking Time: 10 ms
10 msScripts block the page for only 10 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 326 requests
3.5 MBYour homepage downloads 3.5 MB in 326 requests on a phone: other files 1.2 MB (191), scripts 1,021 KiB (87) and images 849 KiB (27). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
UK_s_First_70k_Vape_mobile_1_d1fa7210-ed6a-401c-a3c5-e2908aa 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).
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.1 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
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 68 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Vapeverse Online Store in UK - Get Premium Vape Kits, Pods, & More.”.
2 H1 headlines
There are 2 <h1> headlines (“Vapeverse Online Store in UK - Get Premium Vape K…” and “Vapeverse: Premium Online Vape Shop UK”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, CollectionPage, FAQPage and ImageObject) but with 1 problem, for example “OnlineStore: potentialAction.target is not an absolute URL ("tel:+447961780970")”.
14 links crawlers can't follow
14 links have no real href, so search engines can't follow them.
247 internal links, 7 external
The homepage links to 247 pages on vapeverse.co.uk and 7 external pages.
5 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Discover our collection of vapes in UK. Buy from the Vapeverse online for the best deals on E-liquid, Vape kits, Mods, …”.
Canonical URL set
The canonical URL is https://vapeverse.co.uk/.
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://vapeverse.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 (2,635 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vapeverse.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 112 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 6 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <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 “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
81 of 88 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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,275 words of copy
The homepage carries about 2,275 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “TRACK ORDER”.
12 calls to action
The homepage has 12 calls to action, for example “Track Order”, “Shop Top Sellers →” and “Shop Vape Kits”.
9 short forms
9 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and Yandex Metrica (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
29 other companies contacted
Loading the homepage contacts 29 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 vapeverse.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Bm Country Blocker Ip Blocker · Yoast Seo · Boostymark Regionblock · Omnisend · Avada Faqs · Pushowl · Essential Loyalty Rewards · Unlimited Bundles · trustpilot.com · revy.io
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 27 issues on vapeverse.co.uk, including 11 speed issues, 4 SEO issues and 2 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.