Website review, no card needed

thestringdusters-store.com logo

thestringdusters-store.com website review

Visit site (opens in a new tab)Reviewed 9 November 202628 issues · 75 checks

This review found 28 issues worth fixing on thestringdusters-store.com, 8 of them high impact, across 75 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

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

How it loaded on a phone

  1. thestringdusters-store.com at 1.3 s1.3 s
  2. thestringdusters-store.com at 2.6 s2.6 s
  3. thestringdusters-store.com at 3.9 s3.9 s
  4. thestringdusters-store.com at 5.2 s5.2 s
  5. thestringdusters-store.com at 6.6 s6.6 s
  6. thestringdusters-store.com at 7.9 s7.9 s
  7. thestringdusters-store.com at 9.2 s9.2 s
  8. thestringdusters-store.com at 10.5 s10.5 s

Speed

2 to fix85
  • Render-blocking requests

    15.9 s

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

  • Mobile performance score: 85

    85/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Shopify and minmaxify.com and others), adding 382 KiB and 297 ms of main-thread time.

  • Improve image delivery

    216 KiB

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

  • Reduce unused JavaScript

    214 KiB

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

  • Use efficient cache lifetimes

    111 KiB

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

  • 1 long task on the main thread

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

  • Reduce unused CSS

    53 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    12 KiB

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

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

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix97
  • Speed Index: 13.8 s

    13.8 s

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

  • Time to Interactive: 6.7 s

    6.7 s

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

  • 41 images without width and height

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 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 Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “THE INFAMOUS STRINGDUSTERS DUST THE HALLS VOL.2 CD *PREORDE…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 19 ms

    19 ms

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

Images and page weight

2 to fix83
  • Page weight: 2.1 MB in 158 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 158 requests on a phone: other files 747 KiB (89), images 684 KiB (15) and scripts 612 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    header-1_3797e1e7-706e-4877-af96-0010dc11fffb.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).

  • 2 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7988
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 7 images without alt text

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

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

  • 2 links without text

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

  • 1 form field without a label

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 44 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: 44 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9283
  • Title is short (26 characters)

    Your title is only 26 characters: “The Infamous Stringdusters”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (32 characters)

    Your meta description is only 32 characters: “The Infamous Stringdusters Store”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“The Infamous Stringdusters” and “The Infamous Stringdusters Undercover Vol. 3 / Du…”). One clear main headline is easier for people and search engines.

  • 98 internal links, 15 external

    The homepage links to 98 pages on thestringdusters-store.com and 15 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://thestringdusters-store.com/.

  • Structured data in place

    Structured data found: Product.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without a meta description

    https://thestringdusters-store.com/collections/new-products, https://thestringdusters-store.com/collections/t-shirts, https://thestringdusters-store.com/collections/sweatshirts-jackets, https://thestringdusters-store.com/collections/accessories, https://thestringdusters-store.com/collections/holidays-2023 and https://thestringdusters-store.com/pages/dusters-skis-snowboard and 8 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 64 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 7776
  • 5 broken images

    5 images failed to load on a phone, for example https://thestringdusters-store.com/.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

2 checks passed
  • Tap targets are thumb-sized

    22 of 24 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 544 words of copy

    The homepage carries about 544 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

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

  • 5 calls to action

    The homepage has 5 calls to action, for example “SHOP NOW”, “BUY NOW” and “Contact Us”.

  • 3 short forms

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 10 cookies set on arrival

    10

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 thestringdusters-store.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Minmaxify Order Limits · Sc Product Options · Selleasy · Promotion Popup Allnew

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 28 issues on thestringdusters-store.com, including 6 speed issues, 3 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