Website review, no card needed

chicagobears.com logo

chicagobears.com website review

Visit site (opens in a new tab)Reviewed 29 October 202647 issues · 91 checks

This review found 47 issues worth fixing on chicagobears.com, 19 of them high impact, across 91 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.0 s2.1 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
120 ms101 msMay 9Oct 24105 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026106 ms
May 16, 2026105 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026106 ms
Jun 13, 2026114 ms
Jun 20, 2026116 ms
Jun 27, 2026114 ms
Jul 4, 2026118 ms
Jul 11, 2026111 ms
Jul 18, 2026105 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026107 ms
Aug 22, 2026108 ms
Aug 29, 2026109 ms
Sep 5, 2026109 ms
Sep 12, 2026107 ms
Sep 19, 2026108 ms
Sep 26, 2026106 ms
Oct 3, 2026107 ms
Oct 10, 2026107 ms
Oct 17, 2026104 ms
Oct 24, 2026105 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 chicagobears.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chicagobears.com at 0.4 s0.4 s
  2. chicagobears.com at 0.8 s0.8 s
  3. chicagobears.com at 1.3 s1.3 s
  4. chicagobears.com at 1.7 s1.7 s
  5. chicagobears.com at 2.1 s2.1 s
  6. chicagobears.com at 2.6 s2.6 s
  7. chicagobears.com at 3.0 s3.0 s
  8. chicagobears.com at 3.4 s3.4 s

Speed

16 to fix22
  • Use efficient cache lifetimes

    6.8 s · 1.7 MB

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

  • Reduce unused JavaScript

    2.1 s · 1,011 KiB

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

  • Improve image delivery

    1.2 s · 1.5 MB

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

  • Render-blocking requests

    1.3 s

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

  • Reduce unused CSS

    1.1 s · 142 KiB

    About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 22

    22/100

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

  • Main-thread work: 6.0 s

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

  • 3,234 HTML elements

    The page has 3,234 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 (Google/Doubleclick Ads, Integral Ad Science and Adobe Tag Manager and others), adding 4.4 MB and 2.2 s of main-thread time.

  • Google/Doubleclick Ads adds 622 ms

    622 ms

    Google/Doubleclick Ads costs a phone 622 ms of main-thread work and 2.6 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.

  • Integral Ad Science adds 595 ms

    595 ms

    Integral Ad Science costs a phone 595 ms of main-thread work and 424 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.

  • 20 long tasks on the main thread

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

  • Adobe Tag Manager adds 333 ms

    333 ms

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

    300 ms · 33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 174 ms

    174 ms

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

  • Optanon adds 155 ms

    155 ms

    Optanon costs a phone 155 ms of main-thread work and 351 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.

  • Duplicated JavaScript

    150 ms · 42 KiB

    42 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    7 KiB

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

  • 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: 21 ms

    21 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 18.3 s

    18.3 s

    Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking any of the buttons in this banner, or by clicki…”.

  • Time to Interactive: 31.6 s

    31.6 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Cumulative Layout Shift: 0.222

    0.222

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

  • 23 images without width and height

    23 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-10-24, real Chrome visitors' tap response (inp) went from 106 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user INP: 118 ms

    118 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 405 ms

    405 ms

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

Images and page weight

3 to fix45
  • 1 image over 500 KB

    2026_Matchup_Graphics_-_Week_8_Seattle_-_Mobile_Header.gif weighs 27.8 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 6.3 MB in 270 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 270 requests on a phone: scripts 2.5 MB (92), images 2.4 MB (71) and fonts 733 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (27.8 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.

  • About 1.8 g of CO₂ per visit

    1.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 213.0 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

7 to fixGoogle 8491
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 2 links without text

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 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.

  • 106 internal links, 72 external

    The homepage links to 106 pages on chicagobears.com and 72 external pages.

6 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Chicago Bears Official Website | Official Bears news, videos, photos, tickets, rosters, stats, schedule, and gameday in…”.

  • One H1 headline

    Your main headline reads: “Chicago Bears Official Website | ChicagoBears.com 🐻⬇️”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Chicago Bears Official Website | ChicagoBears.com 🐻⬇️”.

  • Canonical URL set

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

Other pages

3 to fix86
  • 2 pages share a title

    https://www.chicagobears.com/tickets and https://www.chicagobears.com/tickets/index all use the title “Tickets | Chicago Bears Official Website”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.chicagobears.com/tickets and https://www.chicagobears.com/tickets/index use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.chicagobears.com/tickets/index, whose canonical is https://www.chicagobears.com/tickets. 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 78 found) and read each the way a search engine does.

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

  • 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 7385
  • 14 small tap targets

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

  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “🚀 Failed to execute data element module core/src/lib/dataElements/customCode.js for data element identityProvider (Loc…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix70
  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 2,919 words of copy

    The homepage carries about 2,919 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “PRO SHOP” and “Buy Tickets”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SCHEDULE”, “PRO SHOP” and “Buy Tickets”.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and The Trade Desk (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies (measured from a US location before any click).

  • 50 other companies contacted

    Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

Hosting
Fastly

Company

Founded
1919

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on chicagobears.com, including 25 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