Website review, no card needed

totalsportcards.com logo

totalsportcards.com website review

Visit site (opens in a new tab)Reviewed 12 November 202633 issues · 84 checks

This review found 33 issues worth fixing on totalsportcards.com, 10 of them high impact, across 84 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
978 ms847 msMay 23Nov 7961 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026963 ms
May 30, 2026960 ms
Jun 6, 2026955 ms
Jun 13, 2026935 ms
Jun 20, 2026925 ms
Jun 27, 2026943 ms
Jul 4, 2026953 ms
Jul 11, 2026948 ms
Jul 18, 2026959 ms
Jul 25, 2026937 ms
Aug 1, 2026923 ms
Aug 8, 2026931 ms
Aug 15, 2026909 ms
Aug 22, 2026917 ms
Aug 29, 2026910 ms
Sep 5, 2026912 ms
Sep 12, 2026918 ms
Sep 19, 2026888 ms
Sep 26, 2026878 ms
Oct 3, 2026862 ms
Oct 10, 2026865 ms
Oct 17, 2026879 ms
Oct 24, 2026921 ms
Oct 31, 2026945 ms
Nov 7, 2026961 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms64 msMay 23Nov 770 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202670 ms
May 30, 202670 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jun 27, 202671 ms
Jul 4, 202670 ms
Jul 11, 202670 ms
Jul 18, 202670 ms
Jul 25, 202666 ms
Aug 1, 202669 ms
Aug 8, 202669 ms
Aug 15, 202668 ms
Aug 22, 202670 ms
Aug 29, 202669 ms
Sep 5, 202669 ms
Sep 12, 202670 ms
Sep 19, 202665 ms
Sep 26, 202666 ms
Oct 3, 202665 ms
Oct 10, 202666 ms
Oct 17, 202670 ms
Oct 24, 202670 ms
Oct 31, 202671 ms
Nov 7, 202670 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 totalsportcards.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix66
  • Reduce unused JavaScript

    1.6 s · 334 KiB

    About 334 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

    1.0 s · 225 KiB

    3 images could be 225 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 66

    66/100

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

  • Render-blocking requests

    500 ms

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

  • Google Maps adds 220 ms

    220 ms

    Google Maps costs a phone 220 ms of main-thread work and 475 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Maps, Shopify and Google CDN and others), adding 701 KiB and 351 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 16 KiB

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

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    18 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

    A phone's processor spends 1.1 s on main-thread work while loading, 510 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

5 to fix100
  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Speed Index: 6.3 s

    6.3 s

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

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

  • 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

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

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

    1.0 s

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

  • Real-user INP: 70 ms

    70 ms

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

    0.7 s

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

  • Real-user TTFB: 254 ms

    254 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 9 ms

    9 ms

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

Images and page weight

1 to fix90
  • 2 images far larger than shown

    199 KiB

    2 images are downloaded at several times the size a phone draws them, for example ezgif.com-gif-maker_-_2022-09-02T171957.043.png at 2,343 px wide, shown at 86 px. Resized copies would save about 199 KiB.

  • 2 images below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.39 g

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

2 checks passed
  • Page weight: 1.4 MB in 80 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 80 requests on a phone: scripts 781 KiB (50), images 389 KiB (11) and fonts 122 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8292
  • Frames without titles

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

  • 6 images without alt text

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

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

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 52 links without text

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

  • 10 form fields without a label

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 7778
  • No meta description

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

  • Title is short (18 characters)

    Your title is only 18 characters: “Total Sports Cards”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 13 links crawlers can't follow

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

  • 91 internal links, 4 external

    The homepage links to 91 pages on totalsportcards.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Total Sports Cards”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://totalsportcards.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://totalsportcards.com/collections/frontpage/products/pokemon-30th-celebration-ditto-premium-collection and https://totalsportcards.com/products/pokemon-30th-celebration-ditto-premium-collection all use the title “Pokemon 30th Celebration Ditto Premium Collection– Total Sports Cards”. 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://totalsportcards.com/collections/sports-cards, https://totalsportcards.com/collections/sports-cards-hockey-cards-1, https://totalsportcards.com/collections/sports-cards-baseball-cards, https://totalsportcards.com/collections/sports-cards-basketball-cards, https://totalsportcards.com/collections/sports-cards-football-cards and https://totalsportcards.com/collections/soccer-other-sports-test and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://totalsportcards.com/collections/frontpage/products/pokemon-30th-celebration-ditto-premium-collection and https://totalsportcards.com/products/pokemon-30th-celebration-ditto-premium-collection use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://totalsportcards.com/collections/frontpage/products/pokemon-30th-celebration-ditto-premium-collection, whose canonical is https://totalsportcards.com/products/pokemon-30th-celebration-ditto-premium-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0259/8135/4043/files/file.png?v=1638521783.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    69 of 72 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No analytics detected

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

  • Only about 217 words

    The homepage has only about 217 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.

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

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Signup”, “Register Now” and “Subscribe”.

  • 5 short forms

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

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 totalsportcards.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

Ta Labels Badges · Beast Currency Converter · getmason.io · smile.io

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

  • The footer still says © 2021.

Stack

Framework
jQuery
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 33 issues on totalsportcards.com, including 10 speed issues, 4 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