vaperanger.com website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.

The page goes through 1 redirect before it starts loading, costing about 1.1 s. Link and advertise the final URL directly.

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

8 third-party services load with your homepage (mybigcommerce.com, Google Tag Manager and Bigcommerce and others), adding 4.1 MB and 1.6 s of main-thread time.

57 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

mybigcommerce.com costs a phone 449 ms of main-thread work and 488 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.

Bigcommerce costs a phone 261 ms of main-thread work and 2.1 MB 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 131 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.

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

Google Tag Manager costs a phone 302 ms of main-thread work and 499 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 201 ms of main-thread work and 496 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,615 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 97 ms of main-thread work and 382 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 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

10 KiB could be saved by minifying JavaScript.

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

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 visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.35 (75th percentile). Good is under 0.1.

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

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

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “* indicates field is required. ; Email Address * Password *…”. Most of its time is element render delay (3.8 s).

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

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

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

12 images 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 127 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 381 requests on a phone: scripts 3.9 MB (281), images 1.4 MB (26) and other files 204 KiB (45). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 frame has no title, so screen-reader users cannot tell what it contains.

Google's crawler is blocked from indexing this page.

6 links have no real href, so search engines can't follow them.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 245 pages on vaperanger.com and 26 external pages.

https://vaperanger.com/brands/sticky-green is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://vaperanger.com/sales-and-top-links/state-compliant-products, https://vaperanger.com/sales/vapes-for-5-and-below, https://vaperanger.com/sales-and-top-links/arkansas-vape-registry, https://vaperanger.com/sales-and-top-links/mississippi-vape-registry, https://vaperanger.com/sales-and-top-links/nebraska-vape-registry and https://vaperanger.com/sales-and-top-links/wisconsin-vape-registry have no meta description, so Google writes the search snippet from whatever text it finds.

https://vaperanger.com/black-friday-2026, https://vaperanger.com/help-center, https://vaperanger.com/deals, https://vaperanger.com/sales/vapes-for-5-and-below, https://vaperanger.com/collections/new-arrivals and https://vaperanger.com/sales-and-top-links/arkansas-vape-registry and 2 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://vaperanger.com/favicon.ico.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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.

The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads 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.

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