shopsmokeless.com website review

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

6 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

5 third-party services load with your homepage (Klaviyo, Google Tag Manager and Adobe TypeKit and others), adding 2.5 MB and 234 ms of main-thread time.

About 178 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

r2.dev costs a phone 0 ms of main-thread work and 2.0 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.

Klaviyo costs a phone 132 ms of main-thread work and 338 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 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

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.

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vapes, THC gummies, THC beverages, CBD and e-liquid from Sm…”.

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

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

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

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

3 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' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 100 requests on a phone: images 2.3 MB (18), scripts 701 KiB (46) and fonts 87 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example c082d00a-1b7b-4a88-9469-4ebb2814b453.png at 1,080 px wide, shown at 342 px. Resized copies would save about 14 KiB.

1 image (146 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.90 g of CO₂e: 107.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 24 characters: “Smokeless - Vape THC CBD”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 53 characters: “Smokeless — vape, THC & CBD. Must be 21+ to purchase.”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 118 pages on shopsmokeless.com and 5 external pages.

Your Organization JSON-LD is missing logo, 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.

There is no https://shopsmokeless.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://shopsmokeless.com/collections/devices, https://shopsmokeless.com/collections/replacement-pods, https://shopsmokeless.com/collections/replacement-coils, https://shopsmokeless.com/collections/edibles-all, https://shopsmokeless.com/collections/glass and https://shopsmokeless.com/collections/d8-concentrates and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'length')”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 1,140 words of visible text.

Before 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.

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