ejuicestore.com website review

18 images could be 13.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

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

About 135 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.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 225 KiB and 134 ms of main-thread time.

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

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

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

21 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fifty Bar 20K”.

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

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

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

14 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 79 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 15.9 MB in 92 requests on a phone: images 14.6 MB (21), fonts 630 KiB (5) and scripts 405 KiB (31). Under 2 MB keeps phones on slow connections fast.

7 images weigh 12.3 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example ejuicestore_Banner-scaled.png at 2,560 px wide, shown at 370 px. Resized copies would save about 10.9 MB.

20 images (13.9 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.

SB-10-600x196.png 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).

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

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

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 on the page fails this check, rated moderate by axe-core.

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

12 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 66 characters, so Google will cut it off around 60: “Vape Juice | Disposable Vape & Premium E-liquid | Online Vape Shop”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 1,502 pages on ejuicestore.com and 0 external pages.

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ejuicestore.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ejuicestore.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 1,479 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be ejuicestore.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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