Programmable

Website review, no card needed

supervsn.com logo

supervsn.com website review

Visit site (opens in a new tab)Reviewed 11 November 202624 issues · 81 checks

This review found 24 issues worth fixing on supervsn.com, 0 of them high impact, across 81 checks. 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

Site score

91A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
928 ms720 msMay 23Nov 7769 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026904 ms
May 30, 2026826 ms
Jun 6, 2026781 ms
Jun 13, 2026775 ms
Jun 20, 2026769 ms
Jun 27, 2026825 ms
Jul 4, 2026830 ms
Jul 11, 2026837 ms
Jul 18, 2026845 ms
Jul 25, 2026850 ms
Aug 1, 2026799 ms
Aug 8, 2026788 ms
Aug 15, 2026804 ms
Aug 22, 2026744 ms
Aug 29, 2026788 ms
Sep 5, 2026789 ms
Sep 12, 2026781 ms
Sep 19, 2026788 ms
Sep 26, 2026775 ms
Oct 3, 2026786 ms
Oct 10, 2026787 ms
Oct 17, 2026795 ms
Oct 24, 2026799 ms
Oct 31, 2026794 ms
Nov 7, 2026769 ms
Real-visitor tap response (INP)75th percentile, phones
111 ms82 msMay 23Nov 7104 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202685 ms
May 30, 202686 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202689 ms
Jun 27, 202690 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202692 ms
Jul 25, 202695 ms
Aug 1, 202690 ms
Aug 8, 202691 ms
Aug 15, 202694 ms
Aug 22, 202688 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202689 ms
Sep 19, 202694 ms
Sep 26, 202699 ms
Oct 3, 2026104 ms
Oct 10, 2026108 ms
Oct 17, 2026108 ms
Oct 24, 2026108 ms
Oct 31, 2026105 ms
Nov 7, 2026104 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

supervsn.com (opens in a new tab)
Full-page screenshot of supervsn.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. supervsn.com at 0.7 s0.7 s
  2. supervsn.com at 1.5 s1.5 s
  3. supervsn.com at 2.2 s2.2 s
  4. supervsn.com at 3.0 s3.0 s
  5. supervsn.com at 3.7 s3.7 s
  6. supervsn.com at 4.5 s4.5 s
  7. supervsn.com at 5.2 s5.2 s
  8. supervsn.com at 5.9 s5.9 s

Speed

3 to fix98

  • Improve image delivery

    350 ms · 1.2 MB

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

  • Render-blocking requests

    450 ms

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

  • 1,796 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and Google CDN and others), adding 409 KiB and 156 ms of main-thread time.

  • Reduce unused JavaScript

    67 KiB

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

  • Reduce unused CSS

    40 KiB

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

  • Legacy JavaScript

    39 KiB

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

  • Use efficient cache lifetimes

    37 KiB

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

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

3 checks passed

  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.5 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

1 to fix100

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

    +22%

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

13 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: 0.9 s

    0.9 s

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

  • Real-user INP: 135 ms

    135 ms

    Real visitors wait 135 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 439 ms

    439 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Time to Interactive: 2.4 s

    2.4 s

    The page is fully interactive after 2.4 s.

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 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).

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix85

  • Page weight: 3.4 MB in 283 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 283 requests on a phone: images 1.7 MB (38), other files 1,014 KiB (162) and scripts 579 KiB (73). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9595

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

2 checks passed

  • Every image has alt text

    All 67 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10090

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “” and “Your cart”). One clear main headline is easier for people and search engines.

  • No favicon declared

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

  • 98 internal links, 12 external

    The homepage links to 98 pages on supervsn.com and 12 external pages.

6 checks passed

  • Meta description: 123 characters

    Your meta description is 123 characters: “*SUPERVSN is defined by the intersection between reality and creativity, when energy becomes ideas and ideas become thi…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Supervsn | The World Is Our Studio – Supervsn Studios”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://supervsn.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.

3 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 (1,063 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix88

  • 11 pages without a meta description

    https://supervsn.com/collections/new-arrival, https://supervsn.com/blogs/superverse, https://supervsn.com/blogs/projects, https://supervsn.com/pages/about-studio, https://supervsn.com/pages/about-flagship and https://supervsn.com/pages/about-supervsn and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://supervsn.com/pages/returns-and-exchanges and https://supervsn.com/pages/returns-exchanges use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://supervsn.com/collections/new-arrival, https://supervsn.com/pages/about-studio, https://supervsn.com/pages/about-flagship, https://supervsn.com/pages/about-supervsn, https://supervsn.com/pages/faq and https://supervsn.com/pages/returns-and-exchanges and 3 others 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 36 found) and read each the way a search engine does.

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

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

  • 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 ()”.

  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75

  • 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 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: 2 trust badges. 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 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 494 words of copy

    The homepage carries about 494 words of visible text.

4 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP”, “Contact” and “Subscribe”.

  • 6 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 supervsn.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Lucky Orange · mailmunch.co · chimpstatic.com · sesami.co · zonos.com · insprd.tech · shopthelook.app · giftcardpro.app · useamp.com

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
Hosting
Shopify

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on supervsn.com, including 4 speed issues, 3 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