Website review, no card needed

kingsteamstore.com logo

kingsteamstore.com website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 78 checks

This review found 39 issues worth fixing on kingsteamstore.com, 11 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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.4 s2.0 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
209 ms170 msMay 30Nov 14183 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026175 ms
Jun 6, 2026184 ms
Jun 13, 2026192 ms
Jun 20, 2026199 ms
Jun 27, 2026180 ms
Jul 4, 2026174 ms
Jul 11, 2026175 ms
Jul 18, 2026174 ms
Jul 25, 2026178 ms
Aug 1, 2026184 ms
Aug 8, 2026185 ms
Aug 15, 2026179 ms
Aug 22, 2026182 ms
Aug 29, 2026195 ms
Sep 5, 2026201 ms
Sep 12, 2026204 ms
Sep 19, 2026200 ms
Sep 26, 2026192 ms
Oct 3, 2026183 ms
Oct 10, 2026181 ms
Oct 17, 2026195 ms
Oct 24, 2026192 ms
Oct 31, 2026196 ms
Nov 7, 2026188 ms
Nov 14, 2026183 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 kingsteamstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix61
  • Reduce unused JavaScript

    1.6 s · 591 KiB

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

  • Improve image delivery

    800 ms · 918 KiB

    17 images could be 918 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 8 third-party services on the page

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

  • Mobile performance score: 61

    61/100

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

  • Use efficient cache lifetimes

    150 ms · 311 KiB

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

  • Google Tag Manager adds 373 ms

    373 ms

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

  • Render-blocking requests

    350 ms

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

  • Main-thread work: 3.3 s

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

  • 2,176 HTML elements

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

  • Shopify adds 79 ms

    79 ms

    Shopify costs a phone 79 ms of main-thread work and 379 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.

  • azurefd.net adds 71 ms

    71 ms

    azurefd.net costs a phone 71 ms of main-thread work and 332 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.

  • Reduce unused CSS

    290 ms · 42 KiB

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

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    40 KiB

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”.

  • Time to Interactive: 18.3 s

    18.3 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 294 ms

    294 ms

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

  • Cumulative Layout Shift: 0.111

    0.111

    The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

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

    1.7 s

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

  • Real-user INP: 131 ms

    131 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 417 ms

    417 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

1 to fix33
  • Page weight: 4.8 MB in 314 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 314 requests on a phone: images 1.7 MB (30), scripts 1.6 MB (105) and other files 1.2 MB (167). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

Accessibility

6 to fixGoogle 8283
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 11 images without alt text

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

  • 5 buttons without a name

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (8 elements).

1 checks passed
  • 20 automated accessibility rules passed

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

SEO

5 to fixGoogle 8566
  • No meta description

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

  • No H1 headline

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

  • Title is short (27 characters)

    Your title is only 27 characters: “Sacramento Kings Team Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 230 internal links, 5 external

    The homepage links to 230 pages on kingsteamstore.com and 5 external pages.

3 checks passed
  • Canonical URL set

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

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

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

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

Other pages

5 to fix65
  • 1 page points its canonical at the homepage

    https://kingsteamstore.com/products/westbrook-authentic-jersey declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://kingsteamstore.com/collections/new-arrivals and https://kingsteamstore.com/collections/monk are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://kingsteamstore.com/products/westbrook-authentic-jersey all use the title “Sacramento Kings Team Store”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://kingsteamstore.com/collections/all, https://kingsteamstore.com/pages/featured, https://kingsteamstore.com/collections/new-arrivals, https://kingsteamstore.com/collections/adult-featured, https://kingsteamstore.com/collections/youth-featured and https://kingsteamstore.com/collections/headwear-featured and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://kingsteamstore.com/collections/all and https://kingsteamstore.com/products/westbrook-authentic-jersey have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://kingsteamstore.com/collections/all, https://kingsteamstore.com/collections/new-arrivals, https://kingsteamstore.com/collections/adult-featured and https://kingsteamstore.com/collections/youth-featured took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

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

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 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 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 10 words

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

  • 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
  • 35 calls to action

    The homepage has 35 calls to action, for example “Shop All”, “Shop by Player” and “Shop All Collaborations”.

  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

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

  • 1 other company contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on kingsteamstore.com, including 17 speed issues, 5 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