Website review, no card needed

abc7chicago.com logo

abc7chicago.com website review

Visit site (opens in a new tab)Reviewed 11 October 202663 issues · 108 checks

This review found 63 issues worth fixing on abc7chicago.com, 31 of them high impact, across 108 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
2.0 s1.8 sApr 18Oct 32.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.8 s
Apr 25, 20261.8 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
233 ms199 msApr 18Oct 3213 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026229 ms
Apr 25, 2026216 ms
May 2, 2026208 ms
May 9, 2026204 ms
May 16, 2026203 ms
May 23, 2026205 ms
May 30, 2026204 ms
Jun 6, 2026205 ms
Jun 13, 2026209 ms
Jun 20, 2026209 ms
Jun 27, 2026216 ms
Jul 4, 2026220 ms
Jul 11, 2026217 ms
Jul 18, 2026212 ms
Jul 25, 2026210 ms
Aug 1, 2026211 ms
Aug 8, 2026211 ms
Aug 15, 2026213 ms
Aug 22, 2026212 ms
Aug 29, 2026209 ms
Sep 5, 2026207 ms
Sep 12, 2026205 ms
Sep 19, 2026207 ms
Sep 26, 2026211 ms
Oct 3, 2026213 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 abc7chicago.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix36
  • Use efficient cache lifetimes

    5.3 s · 20.5 MB

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

  • Improve image delivery

    1.6 s · 14.4 MB

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

  • Reduce unused JavaScript

    5.5 s · 2.2 MB

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

  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 8.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (abcotvs.net, Google/Doubleclick Ads and disney.com and others), adding 6.9 MB and 2.7 s of main-thread time.

  • Reduce unused CSS

    750 ms · 232 KiB

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

  • abcotvs.net adds 622 ms

    622 ms

    abcotvs.net costs a phone 622 ms of main-thread work and 1.8 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.

  • disney.com adds 501 ms

    501 ms

    disney.com costs a phone 501 ms of main-thread work and 1.9 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.

  • Google/Doubleclick Ads adds 591 ms

    591 ms

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

  • sigalert.com adds 345 ms

    345 ms

    sigalert.com costs a phone 345 ms of main-thread work and 761 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.

  • Google CDN adds 281 ms

    281 ms

    Google CDN costs a phone 281 ms of main-thread work and 738 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.

  • 2,405 HTML elements

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 31 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 73.3 s

    73.3 s

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

  • Speed Index: 49.9 s

    49.9 s

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

  • Time to Interactive: 109.8 s

    109.8 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Total Blocking Time: 832 ms

    832 ms

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

  • 33 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

    1.5 s

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

  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 509 ms

    509 ms

    Real visitors wait 509 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).

Images and page weight

5 to fix18
  • Page weight: 27.5 MB in 515 requests

    27.5 MB

    Your homepage downloads 27.5 MB in 515 requests on a phone: images 19.8 MB (94), scripts 5.9 MB (220) and other files 1.3 MB (179). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    3.0 MB

    4 images are downloaded at several times the size a phone draws them, for example 11484426_011822-wls-live-channel-thumb-v2-img.png at 1,920 px wide, shown at 390 px. Resized copies would save about 3.0 MB.

  • 34 images in older formats

    34 images (10.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.

  • 30 images below the first screen load straight away

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

  • About 7.8 g of CO₂ per visit

    7.80 g

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

Accessibility

21 to fixGoogle 6374
  • Certain ARIA roles must be contained by particular parents (18 elements)

    Certain ARIA roles must be contained by particular parents: 18 elements on the page fail this check, rated critical by axe-core.

  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails 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. (16 elements).

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 8584
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

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

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

  • 143 internal links, 16 external

    The homepage links to 143 pages on abc7chicago.com and 16 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Chicago&#39;s source for breaking news and live streaming video online. Covering News, Weather, Traffic and Sports for …”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “ABC7 WLS Chicago and Chicago News”.

  • Canonical URL set

    The canonical URL is https://abc7chicago.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://abc7chicago.com/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing name, 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.

  • No llms.txt

    There is no https://abc7chicago.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

4 to fix81
  • 2 pages share a title

    https://abc7chicago.com/watch/live and https://abc7chicago.com/live/23379 all use the title “ABC7 Chicago Live Stream: Newscasts, Breaking News from WLS-TV - ABC7…”. 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://abc7chicago.com/watch/live and https://abc7chicago.com/live/23379 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://abc7chicago.com/live/23379, whose canonical is https://abc7chicago.com/watch/23379. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://abc7chicago.com/chicago, https://abc7chicago.com/northern-suburbs, https://abc7chicago.com/western-suburbs, https://abc7chicago.com/southern-suburbs, https://abc7chicago.com/nw-indiana and https://abc7chicago.com/i-team and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://abc7chicago.com/pricetracker has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 75 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 a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 5483
  • 11 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Geolocation error: Geolocation has been disabled in this document by permissions policy.. (1)”.

  • 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

4 to fix50
  • 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.

  • 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 1,013 words of copy

    The homepage carries about 1,013 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop ABC7 Chicago”, “Sign up for ABC7 Chicago newsletters” and “Download ABC7 Chicago on the app store”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Comscore and Google Analytics (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.

  • 13 cookies set on arrival

    13

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

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 63 issues on abc7chicago.com, including 20 speed issues, 3 SEO issues and 4 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