Website review, no card needed

suorinusa.com logo

suorinusa.com website review

Visit site (opens in a new tab)Reviewed 9 November 202621 issues · 67 checks

This review found 21 issues worth fixing on suorinusa.com, 7 of them high impact, across 67 checks. The most urgent: improve image delivery. 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

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

How it loaded on a phone

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

Speed

5 to fix75
  • Improve image delivery

    24.3 s · 12.1 MB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (digitaloceanspaces.com), adding 23.4 MB and 0 ms of main-thread time.

  • digitaloceanspaces.com adds 0 ms

    0 ms

    digitaloceanspaces.com costs a phone 0 ms of main-thread work and 23.4 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.

  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    700 ms

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

  • Legacy JavaScript

    150 ms · 14 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    29 KiB

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

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 31.7 s

    31.7 s

    Your largest element takes 31.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mynto Ice WaterBerry by DripFire”.

  • Time to Interactive: 32.2 s

    32.2 s

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

8 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 INP: 125 ms

    125 ms

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

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (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.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

5 to fix14
  • Page weight: 23.6 MB in 56 requests

    23.6 MB

    Your homepage downloads 23.6 MB in 56 requests on a phone: images 23.4 MB (31), scripts 168 KiB (10) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 15.5 MB together. On a phone connection a single image that size takes seconds.

  • 13 images far larger than shown

    8.4 MB

    13 images are downloaded at several times the size a phone draws them, for example Staghound_DripFire_VCT_Banner.png at 1,536 px wide, shown at 390 px. Resized copies would save about 8.4 MB.

  • 15 images in older formats

    15 images (16.5 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.

  • An image on the first screen is lazy-loaded

    SUSA_Halloween_Vape_Banner_2026_v2.jpg 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).

  • About 6.7 g of CO₂ per visit

    6.70 g

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

Accessibility

1 to fixGoogle 10099
  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 123 internal links, 2 external

    The homepage links to 123 pages on suorinusa.com and 2 external pages.

6 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Suorin USA — official Suorin vape devices, pods, cartridges, coils, accessories and DripFire e-liquids.”.

  • One H1 headline

    Your main headline reads: “Be bold.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “The Leader In Open Pod Systems | Suorin USA”.

  • Canonical URL set

    The canonical URL is https://suorinusa.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://suorinusa.com/sitemap.xml.

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://suorinusa.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 (705 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 76 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

2 to fixGoogle 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • 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 analytics detected

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

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

    The homepage carries about 514 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop Now”, “Shop now” and “Sign Up”.

  • 3 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 suorinusa.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
Next.js
E-commerce
Shopify;Shopify Plus
Hosting
DigitalOcean

Company

Headquarters
Brea

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on suorinusa.com, including 7 speed issues, 2 SEO issues and 3 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