Website review, no card needed

usabaseballshop.us logo

usabaseballshop.us website review

Visit site (opens in a new tab)Reviewed 8 November 202619 issues · 74 checks

This review found 19 issues worth fixing on usabaseballshop.us, 2 of them high impact, across 74 checks. The most urgent: 121 tap targets too small. 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 usabaseballshop.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix92
  • Render-blocking requests

    450 ms

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

  • 2 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (usabaseballshop.com, Shopify and 51.la and others), adding 416 KiB and 393 ms of main-thread time.

  • Reduce unused JavaScript

    80 KiB

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

  • Improve image delivery

    70 KiB

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

  • Use efficient cache lifetimes

    16 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 92

    92/100

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

  • Main-thread work: 1.4 s

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

  • Server response: 60 ms

    60 ms

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

Core Web Vitals

2 to fix92
  • Time to Interactive: 4.9 s

    4.9 s

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

  • Total Blocking Time: 279 ms

    279 ms

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

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

4 checks passed
  • Speed Index: 3.0 s

    3.0 s

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

  • Cumulative Layout Shift: 0.075

    0.075

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

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The Official Shop of USA Baseball”.

Images and page weight

100
  • 2 images below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.45 g

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

3 checks passed
  • Page weight: 1.6 MB in 100 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 100 requests on a phone: scripts 758 KiB (59), images 698 KiB (13) and HTML 94 KiB (3). That is a lean page.

  • 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

5 to fixGoogle 9393
  • 121 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (24 elements)

    All page content should be contained by landmarks: 24 elements on the page fail 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.

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

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 71 images in the HTML carry an alt attribute.

  • 46 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: 46 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

2 to fixGoogle 7794
  • Structured data has 2 problems

    Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://usabaseballshop.com)”.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 194 internal links, 4 external

    The homepage links to 194 pages on usabaseballshop.us and 4 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Since 1978 USA Baseball has been the national governing body for amateur baseball. It represents the sport in the Unite…”.

  • One H1 headline

    Your main headline reads: “The Official Shop of USA Baseball”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “USA Baseball Official Online Shop”.

  • Canonical URL set

    The canonical URL is https://www.usabaseballshop.us/.

  • 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://www.usabaseballshop.us/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing 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,012 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 2 pages share a title

    https://www.usabaseballshop.us/collections/baseballism and https://www.usabaseballshop.us/collections/baseballism/headwear all use the title “USA Baseball x Baseballism”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://www.usabaseballshop.us/collections/new-arrivals, https://www.usabaseballshop.us/collections/best-sellers, https://www.usabaseballshop.us/collections/backpacks-bags, https://www.usabaseballshop.us/collections/usa-baseball-x-fear-of-god-essentials, https://www.usabaseballshop.us/collections/baseballism and https://www.usabaseballshop.us/collections/baseballism/headwear and 4 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 69 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.

  • 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

4 to fixGoogle 8577
  • 33 small tap targets

    33 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 739 words of copy

    The homepage carries about 739 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: “The Official Shop of USA Baseball”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop by Brand”, “Shop by Style” and “USA Baseball Shop”.

  • 8 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 10 cookies set on arrival

    10

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on usabaseballshop.us, including 4 speed issues, 2 SEO issues and 1 conversion gap. 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