Website review, no card needed

pulsarvaporizers.com logo

pulsarvaporizers.com website review

Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 79 checks

This review found 33 issues worth fixing on pulsarvaporizers.com, 9 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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.3 s1.1 sMay 30Nov 141.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Nov 14, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
169 ms106 msMay 30Nov 14149 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026113 ms
Jun 6, 2026120 ms
Jun 13, 2026125 ms
Jun 20, 2026128 ms
Jun 27, 2026130 ms
Jul 4, 2026136 ms
Jul 11, 2026137 ms
Jul 18, 2026138 ms
Jul 25, 2026138 ms
Aug 1, 2026142 ms
Aug 8, 2026147 ms
Aug 15, 2026154 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026162 ms
Sep 12, 2026161 ms
Sep 19, 2026156 ms
Sep 26, 2026155 ms
Oct 3, 2026154 ms
Oct 10, 2026154 ms
Oct 17, 2026157 ms
Oct 24, 2026158 ms
Oct 31, 2026158 ms
Nov 7, 2026154 ms
Nov 14, 2026149 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 pulsarvaporizers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix63
  • Reduce unused JavaScript

    2.4 s · 389 KiB

    About 389 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    150 ms · 4.3 MB

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

  • Use efficient cache lifetimes

    150 ms · 1.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Bigcommerce, Klaviyo and Google Tag Manager and others), adding 6.8 MB and 678 ms of main-thread time.

  • Mobile performance score: 63

    63/100

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

  • Bigcommerce adds 358 ms

    358 ms

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

  • Reduce unused CSS

    750 ms · 123 KiB

    About 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Minify JavaScript

    300 ms · 52 KiB

    52 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.5 s

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

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

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • 7 long tasks on the main thread

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

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

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

6 to fix100
  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pulsar 510 Relay cartridge vaporizer and power bank”.

  • Time to Interactive: 24.9 s

    24.9 s

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

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

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

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

  • Total Blocking Time: 246 ms

    246 ms

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

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 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.3 s

    1.3 s

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

  • Real-user INP: 196 ms

    196 ms

    Real visitors wait 196 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.1 s

    1.1 s

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

  • Real-user TTFB: 502 ms

    502 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix18
  • Page weight: 6.8 MB in 118 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 118 requests on a phone: images 5.6 MB (26), scripts 960 KiB (57) and stylesheets 176 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.2 MB

    4 images are downloaded at several times the size a phone draws them, for example ax1gejxu.jpeg at 3,458 px wide, shown at 350 px. Resized copies would save about 2.2 MB.

  • 5 images in older formats

    5 images (2.8 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.

  • 5 images below the first screen load straight away

    5 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.94 g

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

Accessibility

2 to fixGoogle 10098
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 17 links without text

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 9274
  • No meta description

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

  • Title is short (11 characters)

    Your title is only 11 characters: “Pulsar Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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://www.pulsarshop.com/sitemap.xml, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 119 internal links, 32 external

    The homepage links to 119 pages on pulsarvaporizers.com and 32 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Pulsar Shop”.

  • Canonical URL set

    The canonical URL is https://www.pulsarshop.com/.

  • Structured data in place

    Structured data found: SocialMediaPosting.

  • 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://www.pulsarshop.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 (511 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

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

2 checks passed
  • Tap targets are thumb-sized

    26 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • Only about 176 words

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

  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pulsar Shop” and “Shop Now”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop by Collection”, “Shop by Category” and “Pulsar Shop”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 of them by other companies (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.

  • 18 other companies contacted

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

Apps on your store

Your storefront loads 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Agechecker Net Age Verifier · Terms Checkbox · Microsoft Clarity · Klaviyo Email Marketing Sms · Instafeed · Judge Me Reviews · Crazy Egg · Rebuy Personalization Engine · Route Protection Tracking · Region Restrictions · Terms And Conditions In Cart · Watchlist · powr.io · recovermycart.com · rebuyengine.com · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on pulsarvaporizers.com, including 16 speed issues, 5 SEO issues and 2 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