Website review, no card needed

stlthvape.com logo

stlthvape.com website review

Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 77 checks

This review found 42 issues worth fixing on stlthvape.com, 11 of them high impact, across 77 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s1.3 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
270 ms61 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026244 ms
May 16, 2026246 ms
May 23, 2026245 ms
May 30, 2026211 ms
Jun 6, 2026163 ms
Jun 13, 2026112 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202685 ms
Aug 8, 202685 ms
Aug 15, 202686 ms
Aug 22, 202685 ms
Aug 29, 202686 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202686 ms
Oct 10, 202686 ms
Oct 17, 202686 ms
Oct 24, 202687 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

Full-page screenshot of stlthvape.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stlthvape.com at 0.4 s0.4 s
  2. stlthvape.com at 0.8 s0.8 s
  3. stlthvape.com at 1.1 s1.1 s
  4. stlthvape.com at 1.5 s1.5 s
  5. stlthvape.com at 1.9 s1.9 s
  6. stlthvape.com at 2.3 s2.3 s
  7. stlthvape.com at 2.6 s2.6 s
  8. stlthvape.com at 3.0 s3.0 s

Speed

10 to fix44
  • Avoid multiple page redirects

    18.0 s

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

  • Reduce unused JavaScript

    8.8 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.8 s faster on a phone.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    900 ms · 213 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Yotpo and others), adding 1.4 MB and 880 ms of main-thread time.

  • Minify JavaScript

    600 ms · 63 KiB

    63 KiB could be saved by minifying JavaScript.

  • Main-thread work: 3.6 s

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

  • Improve image delivery

    300 ms · 35 KiB

    1 image could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 304 ms

    304 ms

    Google Tag Manager costs a phone 304 ms of main-thread work and 304 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.

  • Shopify adds 206 ms

    206 ms

    Shopify costs a phone 206 ms of main-thread work and 385 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.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 27.5 s

    27.5 s

    Your largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 27.9 s

    27.9 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Total Blocking Time: 542 ms

    542 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.163

    0.163

    The layout shifts by 0.163 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 284 ms

    284 ms

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

  • Tap response (INP) got 65% faster for real visitors

    -65%

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

Images and page weight

1 to fix0
  • Page weight: 6.3 MB in 433 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 433 requests on a phone: scripts 3.0 MB (168), other files 1.3 MB (180) and images 1.3 MB (38). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.77 g

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

Accessibility

8 to fix66
  • Zoom is disabled

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 14 links without text

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

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

SEO

6 to fixGoogle 7771
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “STLTH Vape - Canada's Online Vape Shop - Disposables & Pods – STLTH VAPE”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (291 characters)

    Your meta description is 291 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

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

  • No X (Twitter) card tag

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

  • 131 internal links, 3 external

    The homepage links to 131 pages on stlthvape.com and 3 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://stlthvape.com/.

  • 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://stlthvape.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

    The site publishes https://stlthvape.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 8 pages share a meta description

    https://stlthvape.com/collections/stlth-x-geek-bar-disposable, https://stlthvape.com/collections/stlth-eco-xl, https://stlthvape.com/collections/eco-box-disposable, https://stlthvape.com/collections/stlth-eco-mini-disposable, https://stlthvape.com/collections/stlth-60k-disposable and https://stlthvape.com/pages/loop-2-system-25k use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://stlthvape.com/collections/loop-25k, https://stlthvape.com/pages/loop-2-system-25k and https://stlthvape.com/collections/loop-2-device 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 49 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

3 to fixGoogle 7384
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 console errors

    3 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_BLOCKED_BY_CLIENT”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

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

  • Thin social proof

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

  • No direct contact details

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

  • No opening hours

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

  • 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 441 words of copy

    The homepage carries about 441 words of visible text.

3 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact US”, “Learn more” and “Buy”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 stlthvape.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on stlthvape.com, including 17 speed issues, 6 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25