ecigoz.com website review

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

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

personalizer.io costs a phone 77 ms of main-thread work and 297 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 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

2 third-party services load with your homepage (personalizer.io and Shopify), adding 412 KiB and 77 ms of main-thread time.

1 long task block the main thread while loading, the longest for 110 ms. During a long task the page ignores taps.

12 images could be 93 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 41 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vape Vend is a vape shop in NZ for customers aged 18 and ov…”.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image (37 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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 42.3 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.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (20 elements).

Structured data found (BreadcrumbList, ImageObject, LocalBusiness and OnlineStore) but with 3 problems, for example “WebSite: missing name”.

The homepage links to 658 pages on ecigoz.com and 6 external pages.

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

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://edge.personalizer.io/storefront/css/recommendation.087715de3fb1f5110a14.css' from …”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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 2,129 words of visible text.

Opening the homepage sets 7 cookies (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.