Website review, no card needed

laytonsportscards.com logo

laytonsportscards.com website review

Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 76 checks

This review found 28 issues worth fixing on laytonsportscards.com, 8 of them high impact, across 76 checks. The most urgent: page weight: 6.4 MB in 200 requests. 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
864 ms793 msMay 16Oct 31810 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026837 ms
May 23, 2026848 ms
May 30, 2026851 ms
Jun 6, 2026847 ms
Jun 13, 2026842 ms
Jun 20, 2026837 ms
Jun 27, 2026832 ms
Jul 4, 2026824 ms
Jul 11, 2026824 ms
Jul 18, 2026811 ms
Jul 25, 2026807 ms
Aug 1, 2026801 ms
Aug 8, 2026813 ms
Aug 15, 2026825 ms
Aug 22, 2026840 ms
Aug 29, 2026856 ms
Sep 5, 2026847 ms
Sep 12, 2026845 ms
Sep 19, 2026839 ms
Sep 26, 2026836 ms
Oct 3, 2026825 ms
Oct 10, 2026820 ms
Oct 17, 2026814 ms
Oct 24, 2026807 ms
Oct 31, 2026810 ms
Real-visitor tap response (INP)75th percentile, phones
87 ms77 msMay 16Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202678 ms
May 23, 202679 ms
May 30, 202680 ms
Jun 6, 202683 ms
Jun 13, 202685 ms
Jun 20, 202686 ms
Jun 27, 202686 ms
Jul 4, 202685 ms
Jul 11, 202686 ms
Jul 18, 202684 ms
Jul 25, 202683 ms
Aug 1, 202681 ms
Aug 8, 202680 ms
Aug 15, 202680 ms
Aug 22, 202682 ms
Aug 29, 202684 ms
Sep 5, 202685 ms
Sep 12, 202685 ms
Sep 19, 202685 ms
Sep 26, 202686 ms
Oct 3, 202685 ms
Oct 10, 202684 ms
Oct 17, 202681 ms
Oct 24, 202680 ms
Oct 31, 202680 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 laytonsportscards.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. laytonsportscards.com at 0.8 s0.8 s
  2. laytonsportscards.com at 1.6 s1.6 s
  3. laytonsportscards.com at 2.3 s2.3 s
  4. laytonsportscards.com at 3.1 s3.1 s
  5. laytonsportscards.com at 3.9 s3.9 s
  6. laytonsportscards.com at 4.7 s4.7 s
  7. laytonsportscards.com at 5.5 s5.5 s
  8. laytonsportscards.com at 6.2 s6.2 s

Speed

11 to fix56
  • 8 third-party services on the page

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

  • Improve image delivery

    550 ms · 926 KiB

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

  • Reduce unused JavaScript

    750 ms · 291 KiB

    About 291 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Signyfyd adds 796 ms

    796 ms

    Signyfyd costs a phone 796 ms of main-thread work and 280 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.

  • Shopify adds 27 ms

    27 ms

    Shopify costs a phone 27 ms of main-thread work and 3.0 MB 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.

  • Main-thread work: 3.4 s

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

  • Reduce unused CSS

    300 ms · 17 KiB

    About 17 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.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    285 KiB

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

  • 1,652 HTML elements

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

  • Font display

    50 ms

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

  • Minify JavaScript

    9 KiB

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

  • Legacy JavaScript

    4 KiB

    Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2026 inception football banner”.

  • Time to Interactive: 14.7 s

    14.7 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Total Blocking Time: 468 ms

    468 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 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

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 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.1 s

    1.1 s

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

  • Real-user INP: 78 ms

    78 ms

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

    0.8 s

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

  • Real-user TTFB: 396 ms

    396 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 6.4 MB in 200 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 200 requests on a phone: images 4.4 MB (37), scripts 995 KiB (64) and other files 769 KiB (89). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (196 KiB) 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.

  • About 1.8 g of CO₂ per visit

    1.81 g

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

2 checks passed
  • 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

3 to fixGoogle 8994
  • <dt> and <dd> elements must be contained by a <dl> (22 elements)

    <dt> and <dd> elements must be contained by a <dl>: 22 elements on the page fail this check, rated serious by axe-core.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (11 elements)

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

  • 4 images without alt text

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

1 checks passed
  • 48 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: 48 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Layton Sports Cards - Specializing in Sports Cards & Live Case Breaks”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“<img src="//laytonsportscards.com/cdn/shop/files/…” and “Sign Up to Receive our Exclusive Newsletter, Upda…”). One clear main headline is easier for people and search engines.

  • Meta description is long (273 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 100 internal links, 26 external

    The homepage links to 100 pages on laytonsportscards.com and 26 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://laytonsportscards.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,305 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 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 a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'api_endpoint')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

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

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

    The homepage carries about 816 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: “CLICK HERE TO JOIN”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Break Schedule”, “Our Main Channel Schedule” and “Our Channel 2 Schedule”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

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, Meta Pixel and TikTok 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.

  • 16 cookies set on arrival

    16

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

  • 29 other companies contacted

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

Apps your storefront loads

Blockify Fraud Filter · Postscript Sms Marketing · Region Restrictions · Test Sms · sharethis.com · signifyd.com · nfcube.com · elfsight.com · avada.io · yotpo.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

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Apopka

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on laytonsportscards.com, including 17 speed issues, 4 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