Website review, no card needed

gpsportcards.com logo

gpsportcards.com website review

Visit site (opens in a new tab)Reviewed 16 November 202623 issues · 72 checks

This review found 23 issues worth fixing on gpsportcards.com, 7 of them high impact, across 72 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
804 ms646 msMay 30Nov 14694 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026786 ms
Jun 6, 2026735 ms
Jun 13, 2026728 ms
Jun 20, 2026744 ms
Jun 27, 2026705 ms
Jul 4, 2026714 ms
Jul 11, 2026727 ms
Jul 18, 2026726 ms
Jul 25, 2026694 ms
Aug 1, 2026687 ms
Aug 8, 2026664 ms
Aug 15, 2026670 ms
Aug 22, 2026692 ms
Aug 29, 2026690 ms
Sep 5, 2026694 ms
Sep 12, 2026678 ms
Sep 19, 2026680 ms
Sep 26, 2026680 ms
Oct 3, 2026690 ms
Oct 10, 2026694 ms
Oct 17, 2026704 ms
Oct 24, 2026716 ms
Oct 31, 2026693 ms
Nov 7, 2026686 ms
Nov 14, 2026694 ms
Real-visitor tap response (INP)75th percentile, phones
60 ms53 msMay 30Nov 1454 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202659 ms
Jun 6, 202659 ms
Jun 13, 202655 ms
Jun 20, 202655 ms
Jun 27, 202654 ms
Jul 4, 202654 ms
Jul 11, 202654 ms
Jul 18, 202654 ms
Jul 25, 202654 ms
Aug 1, 202654 ms
Aug 8, 202654 ms
Aug 15, 202654 ms
Aug 22, 202654 ms
Aug 29, 202654 ms
Sep 5, 202654 ms
Sep 12, 202654 ms
Sep 19, 202658 ms
Sep 26, 202658 ms
Oct 3, 202657 ms
Oct 10, 202654 ms
Oct 17, 202654 ms
Oct 24, 202656 ms
Oct 31, 202655 ms
Nov 7, 202654 ms
Nov 14, 202654 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 gpsportcards.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gpsportcards.com at 0.4 s0.4 s
  2. gpsportcards.com at 0.8 s0.8 s
  3. gpsportcards.com at 1.2 s1.2 s
  4. gpsportcards.com at 1.7 s1.7 s
  5. gpsportcards.com at 2.1 s2.1 s
  6. gpsportcards.com at 2.5 s2.5 s
  7. gpsportcards.com at 2.9 s2.9 s
  8. gpsportcards.com at 3.3 s3.3 s

Speed

7 to fix74
  • Reduce unused JavaScript

    1.1 s · 184 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    300 ms · 77 KiB

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

  • Reduce unused CSS

    300 ms · 18 KiB

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

  • Use efficient cache lifetimes

    300 ms · 17 KiB

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

  • Shopify adds 197 ms

    197 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, merchantyard.com and Privy and others), adding 504 KiB and 206 ms of main-thread time.

  • 1 long task on the main thread

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

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

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 7.2 s

    7.2 s

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

  • Time to Interactive: 7.5 s

    7.5 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 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: 0.7 s

    0.7 s

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

  • Real-user INP: 51 ms

    51 ms

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

    0.6 s

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

  • Speed Index: 3.3 s

    3.3 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.49 g

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

4 checks passed
  • Page weight: 1.7 MB in 175 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 175 requests on a phone: other files 820 KiB (113), scripts 626 KiB (44) and images 199 KiB (9). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9597
  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9283
  • No meta description

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

  • Title is short (15 characters)

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

  • 33 internal links, 5 external

    The homepage links to 33 pages on gpsportcards.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “<img src="//gpsportcards.com/cdn/shop/files/GP_Sports_Cards3445_1_135x.png?v=1636480098" srcset="//gpsportcards.com/cdn…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,006 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://gpsportcards.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://gpsportcards.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://gpsportcards.com/collections/breaks, https://gpsportcards.com/pages/contact and https://gpsportcards.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://gpsportcards.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 9693
  • 10 small tap targets

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

2 checks passed
  • No console errors

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

  • 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 297 words of copy

    The homepage carries about 297 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Quote (0)”.

  • 5 calls to action

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

  • 3 short forms

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

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

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

Apps your storefront loads

Ta Labels Badges · Sa Request A Quote · Ecomsend · merchantyard.com · privy.com

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

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 23 issues on gpsportcards.com, including 11 speed issues, 2 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