Website review, no card needed

eastbay.com logo

eastbay.com website review

Visit site (opens in a new tab)Reviewed 29 October 202642 issues · 86 checks

This review found 42 issues worth fixing on eastbay.com, 19 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
3.8 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.3 s
May 23, 20263.0 s
May 30, 20262.8 s
Jun 6, 20263.3 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.4 s
Jul 4, 20262.7 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
572 ms409 msMay 9Oct 24494 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026431 ms
May 16, 2026428 ms
May 23, 2026430 ms
May 30, 2026438 ms
Jun 6, 2026446 ms
Jun 13, 2026454 ms
Jun 20, 2026453 ms
Jun 27, 2026465 ms
Jul 4, 2026476 ms
Jul 11, 2026487 ms
Jul 18, 2026512 ms
Jul 25, 2026523 ms
Aug 1, 2026544 ms
Aug 8, 2026553 ms
Aug 15, 2026547 ms
Aug 22, 2026538 ms
Aug 29, 2026523 ms
Sep 5, 2026522 ms
Sep 12, 2026523 ms
Sep 19, 2026525 ms
Sep 26, 2026522 ms
Oct 3, 2026507 ms
Oct 10, 2026503 ms
Oct 17, 2026495 ms
Oct 24, 2026494 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 eastbay.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eastbay.com at 1.7 s1.7 s
  2. eastbay.com at 3.4 s3.4 s
  3. eastbay.com at 5.0 s5.0 s
  4. eastbay.com at 6.7 s6.7 s
  5. eastbay.com at 8.4 s8.4 s
  6. eastbay.com at 10.1 s10.1 s
  7. eastbay.com at 11.8 s11.8 s
  8. eastbay.com at 13.4 s13.4 s

Speed

13 to fix27
  • Use efficient cache lifetimes

    11.2 s · 2.2 MB

    76 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Improve image delivery

    2.8 s · 5.5 MB

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

  • Reduce unused JavaScript

    4.2 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Render-blocking requests

    3.7 s

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

  • Main-thread work: 13.5 s

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

  • ContentSquare adds 1.2 s

    1.2 s

    ContentSquare costs a phone 1.2 s of main-thread work and 195 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 27

    27/100

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

  • 3,204 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (ContentSquare, Adobe Tag Manager and Bazaarvoice and others), adding 1.4 MB and 1.9 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    600 ms · 145 KiB

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

  • Adobe Tag Manager adds 250 ms

    250 ms

    Adobe Tag Manager costs a phone 250 ms of main-thread work and 402 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.

  • Bazaarvoice adds 164 ms

    164 ms

    Bazaarvoice costs a phone 164 ms of main-thread work and 371 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

    26 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

9 to fix33
  • 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 INP: 849 ms

    849 ms

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

  • Real-user CLS: 0.86

    0.86

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

  • First Contentful Paint: 10.1 s

    10.1 s

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

  • Largest Contentful Paint: 23.9 s

    23.9 s

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

  • Speed Index: 26.3 s

    26.3 s

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

  • Time to Interactive: 44.6 s

    44.6 s

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

  • Total Blocking Time: 2.3 s

    2.3 s

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

  • 6 images without width and height

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

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

    +15%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 586 ms

    586 ms

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

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

    -34%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix28
  • Page weight: 11.0 MB in 272 requests

    11.0 MB

    Your homepage downloads 11.0 MB in 272 requests on a phone: images 6.5 MB (71), scripts 3.5 MB (86) and fonts 561 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (3.5 MB) are 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.

  • 8 images below the first screen load straight away

    8 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    169 KiB

    4 images are downloaded at several times the size a phone draws them, for example OctWk4-OctoberA-Frames-2up.gif at 1,200 px wide, shown at 390 px. Resized copies would save about 169 KiB.

  • About 3.1 g of CO₂ per visit

    3.13 g

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

Accessibility

3 to fixGoogle 10097
  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

    3 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 (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 111 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 2 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 9284
  • Title is short (29 characters)

    Your title is only 29 characters: “Champs Sports | Champs Sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

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

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 375 internal links, 26 external

    The homepage links to 375 pages on eastbay.com and 26 external pages.

5 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Get your head-to-toe hook up on the latest shoes and clothing from Jordan, Nike, adidas, and more. Free shipping for FL…”.

  • One H1 headline

    Your main headline reads: “Champs Sports”.

  • Canonical URL set

    The canonical URL is https://www.champssports.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://www.champssports.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://www.champssports.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 (922 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.champssports.com/product/champs-sports-e-mail-gift-card/ECARD20.html, whose canonical is https://www.champssports.com/product/model/digital-gift-card/65301.html. 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 193 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 7788
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 33 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 356 words of copy

    The homepage carries about 356 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Licensed Gear” and “Shop On”.

  • 48 calls to action

    The homepage has 48 calls to action, for example “Sign In | Join FLX”, “🎁 Holiday Shop” and “Shop All Gifts”.

  • 3 short forms

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 12 cookies set on arrival

    12

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

  • 21 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
Hosting
Fastly

Company

Founded
1980
Headquarters
Wausau

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on eastbay.com, including 22 speed issues, 4 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