Website review, no card needed

723vapor.com logo

723vapor.com website review

Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 86 checks

This review found 39 issues worth fixing on 723vapor.com, 10 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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.6 s1.1 sMay 9Oct 101.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
84 ms76 msMay 9Oct 1079 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202679 ms
May 16, 202678 ms
May 23, 202678 ms
May 30, 202680 ms
Jun 6, 202681 ms
Jun 13, 202680 ms
Jun 20, 202682 ms
Jun 27, 202680 ms
Jul 4, 202683 ms
Jul 11, 202680 ms
Sep 12, 202677 ms
Sep 19, 202678 ms
Sep 26, 202679 ms
Oct 3, 202678 ms
Oct 10, 202679 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 723vapor.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix64
  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    900 ms · 522 KiB

    14 images could be 522 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 198 KiB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Bigcommerce, Google Tag Manager and Google Analytics and others), adding 1.9 MB and 433 ms of main-thread time.

  • Duplicated JavaScript

    450 ms · 95 KiB

    95 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 450 ms faster on a phone.

  • Bigcommerce adds 213 ms

    213 ms

    Bigcommerce costs a phone 213 ms of main-thread work and 1.5 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.

  • Reduce unused CSS

    300 ms · 28 KiB

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

  • Google Tag Manager adds 192 ms

    192 ms

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

  • 1,501 HTML elements

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

  • Legacy JavaScript

    150 ms · 29 KiB

    Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 25 KiB

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 548 ms of it running JavaScript. That is comfortably low.

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 10.6 s

    10.6 s

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

  • Time to Interactive: 10.7 s

    10.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • 31 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 61 ms

    61 ms

    Scripts block the page for only 61 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix83
  • 12 images below the first screen load straight away

    12 images further down the page (609 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images far larger than shown

    142 KiB

    6 images are downloaded at several times the size a phone draws them, for example 1.png at 1,024 px wide, shown at 327 px. Resized copies would save about 142 KiB.

  • About 0.6 g of CO₂ per visit

    0.56 g

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

2 checks passed
  • Page weight: 2.0 MB in 63 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 63 requests on a phone: images 1.3 MB (39), scripts 537 KiB (12) and fonts 92 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8993
  • 7 text elements with low contrast

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

  • 3 tap targets too small

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

  • All page content should be contained by landmarks (28 elements)

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

  • 21 links without text

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

  • 4 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 8566
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (9 characters)

    Your title is only 9 characters: “723 Vapor”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://723vapor.com/sitemap.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 85 internal links, 1 external

    The homepage links to 85 pages on 723vapor.com and 1 external page.

2 checks passed
  • Canonical URL set

    The canonical URL is https://723vapor.com/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://723vapor.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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (681 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://723vapor.com/compare, https://723vapor.com/e-liquids, https://723vapor.com/e-liquids/bams-cannoli, https://723vapor.com/e-liquids/coastal-clouds, https://723vapor.com/e-liquids/coastal-clouds-salts and https://723vapor.com/e-liquids/ends-game-nixodine and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://723vapor.com/.

  • 3 small tap targets

    3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

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

  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • No analytics detected

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

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

    The homepage carries about 781 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Register”, “Learn More” and “SHOP ALL POD RIPPERS”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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

Upkeep, stack and company

Stack

E-commerce
BigCommerce
Hosting
Bigcommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on 723vapor.com, including 15 speed issues, 7 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