Website review, no card needed
evolutionvaping.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202644 issues · 94 checks
This review found 44 issues worth fixing on evolutionvaping.co.uk, 20 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
66D- #107,004 of 116,964 reviewed websitesbeats 7%
- #63,945 of 66,854 online storesbeats 4%
- #58,778 of 60,980 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 105 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 106 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
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Reduce unused JavaScript
4.2 s · 657 KiBAbout 657 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.
Use efficient cache lifetimes
2.2 s · 482 KiB16 files are served with short cache lifetimes, so returning visitors download them again (482 KiB).
Render-blocking requests
1.9 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,000 HTML elements
The page has 5,000 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, PayPal and fastbundle.co and others), adding 1.3 MB and 567 ms of main-thread time.
Reduce unused CSS
450 ms · 141 KiBAbout 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Shopify adds 209 ms
209 msShopify costs a phone 209 ms of main-thread work and 519 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.
Improve image delivery
150 ms · 88 KiB8 images could be 88 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.
Duplicated JavaScript
50 ms · 8 KiB8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 77 ms
77 msYour server sent the HTML in 77 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.
Real-user CLS: 0.83
0.83For real visitors the layout shifts by 0.83 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 23.7 s
23.7 sYour largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.752
0.752The layout shifts by 0.752 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 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.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 278 ms
278 msReal visitors wait 278 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.6 MB in 462 requests
5.6 MBYour homepage downloads 5.6 MB in 462 requests on a phone: images 2.2 MB (191), scripts 1.6 MB (88) and other files 1.1 MB (144). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (396 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (190 KiB) 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.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 190.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
87 elements hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (53 elements)
All page content should be contained by landmarks: 53 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
61 links without text
61 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 12 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
136 links crawlers can't follow
136 links have no real href, so search engines can't follow them.
Title is short (16 characters)
Your title is only 16 characters: “Evolution Vaping”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 H1 headlines
There are 3 <h1> headlines (“Evolution Vaping”, “Sign Up Today” and “Sign Up Today”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, CollectionPage, ImageObject and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
642 internal links, 60 external
The homepage links to 642 pages on evolutionvaping.co.uk and 60 external pages.
5 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Evolution Vaping offers 150+ e-liquid brands & the UK’s largest vape hardware range. Shop Vaporesso, OXVA, GeekVape, El…”.
Canonical URL set
The canonical URL is https://www.evolutionvaping.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://www.evolutionvaping.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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 (5,828 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.evolutionvaping.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://www.evolutionvaping.co.uk/collections/new-products, https://www.evolutionvaping.co.uk/collections/all-eliquid, https://www.evolutionvaping.co.uk/pages/eliquid-brands, https://www.evolutionvaping.co.uk/collections/bar-juice-5000, https://www.evolutionvaping.co.uk/collections/bar-series-eliquid and https://www.evolutionvaping.co.uk/collections/elfliq-eliquid and 9 others have 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 190 found) and read each the way a search engine does.
6 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 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.evolutionvaping.co.uk/.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'value')”.
2 checks passed
Tap targets are thumb-sized
457 of 463 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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 4,414 words of copy
The homepage carries about 4,414 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “SHOP BY BRAND”.
82 calls to action
The homepage has 82 calls to action, for example “Shop”, “SHOP BY BRAND” and “Pablo's Cake Shop”.
4 short forms
4 short forms (4 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 2 trust badges.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
28 other companies contacted
Loading the homepage contacts 28 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 evolutionvaping.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Lipscore Reviews · Klaviyo Email Marketing Sms · Gsc Countdown Timer · Fbp Fast Bundle · Hulk Form Builder · Yoast Seo · Crisp Live Chat Chatbot · Vex Auto Add To Cart · Pushowl · Crisp Chatbox · Ecomsend · trustpilot.com · onrender.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
- The footer still says © 2025.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on evolutionvaping.co.uk, including 18 speed issues, 5 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.