Website review, no card needed

shopseether.com logo

shopseether.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 75 checks

This review found 26 issues worth fixing on shopseether.com, 12 of them high impact, across 75 checks. The most urgent: page weight: 26.8 MB in 175 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.1 s581 msMay 23Nov 7809 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026909 ms
May 30, 2026825 ms
Jun 6, 2026844 ms
Jun 13, 2026804 ms
Jun 20, 2026889 ms
Jun 27, 2026910 ms
Jul 4, 2026983 ms
Jul 11, 20261.0 s
Jul 18, 2026966 ms
Jul 25, 2026966 ms
Aug 1, 2026761 ms
Aug 8, 2026668 ms
Aug 15, 2026640 ms
Aug 22, 2026650 ms
Aug 29, 2026672 ms
Sep 5, 2026715 ms
Sep 12, 2026802 ms
Sep 19, 2026782 ms
Sep 26, 2026799 ms
Oct 3, 2026759 ms
Oct 10, 2026728 ms
Oct 17, 2026743 ms
Oct 24, 2026703 ms
Oct 31, 2026775 ms
Nov 7, 2026809 ms
Real-visitor tap response (INP)75th percentile, phones
91 ms58 msMay 23Nov 763 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202676 ms
May 30, 202671 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jul 4, 202682 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202684 ms
Aug 1, 202677 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202664 ms
Sep 26, 202664 ms
Oct 3, 202663 ms
Oct 10, 202662 ms
Oct 17, 202662 ms
Oct 24, 202662 ms
Oct 31, 202662 ms
Nov 7, 202663 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 shopseether.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix70
  • Use efficient cache lifetimes

    1.9 s · 388 KiB

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

  • Reduce unused JavaScript

    1.2 s · 319 KiB

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

  • 3,085 HTML elements

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

  • Mobile performance score: 70

    70/100

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

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    357 KiB

    15 images could be 357 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • bandsintown.com adds 140 ms

    140 ms

    bandsintown.com costs a phone 140 ms of main-thread work and 448 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (bandsintown.com, Google Tag Manager and Shopify and others), adding 882 KiB and 333 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 6 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    19 KiB

    About 19 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: 1.5 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LOGO WHITE.png__PID:34bb204a-27e0-424d-82d6-5307aafaffc3”.

  • Time to Interactive: 9.5 s

    9.5 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

10 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: 62 ms

    62 ms

    Real visitors wait 62 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.9 s

    0.9 s

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

  • Real-user TTFB: 431 ms

    431 ms

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

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

    -15%

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

  • Total Blocking Time: 141 ms

    141 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

1 to fix70
  • Page weight: 26.8 MB in 175 requests

    26.8 MB

    Your homepage downloads 26.8 MB in 175 requests on a phone: media 24.3 MB (3), scripts 963 KiB (48) and other files 761 KiB (92). Under 2 MB keeps phones on slow connections fast.

  • About 7.6 g of CO₂ per visit

    7.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.61 g of CO₂e: 912.9 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

4 to fixGoogle 8893
  • 58 tap targets too small

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

  • 56 text elements with low contrast

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

  • Links must have discernible text (29 elements)

    Links must have discernible text: 29 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8583
  • No meta description

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

  • Title is short (28 characters)

    Your title is only 28 characters: “SEETHER OFFICIAL MERCH STORE”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Open Graph partly set

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

  • 59 internal links, 7 external

    The homepage links to 59 pages on shopseether.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Seether-store”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

3 to fix83
  • 2 pages share a title

    https://shopseether.com/collections/tour and https://shopseether.com/pages/tour all use the title “TOUR”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://shopseether.com/collections/all-products, https://shopseether.com/collections/tees, https://shopseether.com/collections/hoodies, https://shopseether.com/collections/outerwear, https://shopseether.com/collections/headwear and https://shopseether.com/collections/tour and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://shopseether.com/pages/tour has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://shopseether.com/collections/tees and https://shopseether.com/collections/hoodies took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

    33 of 38 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 social proof

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

  • No analytics detected

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP” and “SHOP NEW COLLECTION”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SHOP BY TYPE”, “SIGN UP” and “SHOP NEW COLLECTION”.

  • 9 short forms

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 16 other companies contacted

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

Apps your storefront loads

Gorgias Live Chat Helpdesk · Pagefly Ai Page Builder · Fontify

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on shopseether.com, including 10 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