Website review, no card needed

scoresports.com logo

scoresports.com website review

Visit site (opens in a new tab)Reviewed 22 October 202647 issues · 91 checks

This review found 47 issues worth fixing on scoresports.com, 20 of them high impact, across 91 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.6 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
124 ms83 msMay 2Oct 17112 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202695 ms
May 9, 202690 ms
May 16, 202688 ms
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202693 ms
Jun 13, 202695 ms
Jun 20, 202694 ms
Jun 27, 202693 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 2026104 ms
Aug 15, 2026111 ms
Aug 22, 2026112 ms
Aug 29, 2026119 ms
Sep 5, 2026112 ms
Sep 12, 2026111 ms
Sep 19, 2026112 ms
Sep 26, 2026110 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026112 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 scoresports.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. scoresports.com at 0.7 s0.7 s
  2. scoresports.com at 1.3 s1.3 s
  3. scoresports.com at 2.0 s2.0 s
  4. scoresports.com at 2.6 s2.6 s
  5. scoresports.com at 3.3 s3.3 s
  6. scoresports.com at 4.0 s4.0 s
  7. scoresports.com at 4.6 s4.6 s
  8. scoresports.com at 5.3 s5.3 s

Speed

12 to fix44
  • Improve image delivery

    8.8 s · 5.2 MB

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

  • Render-blocking requests

    4.3 s

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

  • Reduce unused JavaScript

    2.5 s · 712 KiB

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

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44 (desktop: 10). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Klaviyo and others), adding 2.1 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    890 ms · 130 KiB

    About 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 890 ms faster on a phone.

  • Use efficient cache lifetimes

    650 ms · 362 KiB

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

  • Google Tag Manager adds 676 ms

    676 ms

    Google Tag Manager costs a phone 676 ms of main-thread work and 959 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.

  • Facebook adds 283 ms

    283 ms

    Facebook costs a phone 283 ms of main-thread work and 254 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.

  • Klaviyo adds 112 ms

    112 ms

    Klaviyo costs a phone 112 ms of main-thread work and 335 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.

  • Cloudflare CDN adds 40 ms

    40 ms

    Cloudflare CDN costs a phone 40 ms of main-thread work and 420 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.

  • Legacy JavaScript

    150 ms · 41 KiB

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • 17 long tasks on the main thread

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

  • Minify JavaScript

    140 ms · 2 KiB

    2 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.42

    0.42

    For real visitors the layout shifts by 0.42 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 55.6 s

    55.6 s

    Your largest element takes 55.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NRPA SCORE SPORTS”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 60.2 s

    60.2 s

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

  • First Contentful Paint: 5.8 s

    5.8 s

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

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

    +21%

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

  • Total Blocking Time: 476 ms

    476 ms

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

  • 8 images without width and height

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 120 ms

    120 ms

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

  • 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: 298 ms

    298 ms

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

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

    -12%

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

4 to fix35
  • Page weight: 15.0 MB in 371 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 371 requests on a phone: images 12.0 MB (25), scripts 2.3 MB (282) and fonts 509 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 10.0 MB together. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.7 MB) is 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.

  • 3 images far larger than shown

    88 KiB

    3 images are downloaded at several times the size a phone draws them, for example NRPA_SCORE_SPORTS_2026-07-MOBILE-OK.png at 1,280 px wide, shown at 420 px. Resized copies would save about 88 KiB.

  • About 4.3 g of CO₂ per visit

    4.27 g

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

1 checks passed
  • Images load when needed

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

Accessibility

7 to fixGoogle 7289
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 19 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

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

5 to fixGoogle 7779
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (195 characters)

    Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 103 internal links, 9 external

    The homepage links to 103 pages on scoresports.com and 9 external pages.

5 checks passed
  • Title: 45 characters

    Your title is a healthy 45 characters: “Scoresports.com - Sports Uniforms & Equipment”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://scoresports.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://scoresports.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 (489 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 64 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 8883
  • Scrolls sideways on phones

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'set')”.

  • 2 distorted images

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix61
  • 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.

  • No social proof

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

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

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • Only about 238 words

    The homepage has only about 238 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

4 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “LEARN MORE”, “SHOP NOW” and “START DESIGNING”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 24 cookies set on arrival

    24

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 scoresports.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
Bootstrap
E-commerce
Magento
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on scoresports.com, including 21 speed issues, 5 SEO issues and 5 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