Website review, no card needed

Chicago Sun-Times logo

suntimes.com website review

Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 88 checks

This review found 43 issues worth fixing on suntimes.com, 23 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Chicago Sun-Times

  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.5 s2.3 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
177 ms143 msMay 30Nov 14165 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026153 ms
Jun 6, 2026155 ms
Jun 13, 2026155 ms
Jun 20, 2026154 ms
Jun 27, 2026152 ms
Jul 4, 2026152 ms
Jul 11, 2026150 ms
Jul 18, 2026149 ms
Jul 25, 2026148 ms
Aug 1, 2026147 ms
Aug 8, 2026154 ms
Aug 15, 2026160 ms
Aug 22, 2026163 ms
Aug 29, 2026164 ms
Sep 5, 2026163 ms
Sep 12, 2026164 ms
Sep 19, 2026164 ms
Sep 26, 2026166 ms
Oct 3, 2026167 ms
Oct 10, 2026169 ms
Oct 17, 2026171 ms
Oct 24, 2026173 ms
Oct 31, 2026172 ms
Nov 7, 2026166 ms
Nov 14, 2026165 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 suntimes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. suntimes.com at 1.7 s1.7 s
  2. suntimes.com at 3.4 s3.4 s
  3. suntimes.com at 5.1 s5.1 s
  4. suntimes.com at 6.8 s6.8 s
  5. suntimes.com at 8.5 s8.5 s
  6. suntimes.com at 10.2 s10.2 s
  7. suntimes.com at 11.9 s11.9 s
  8. suntimes.com at 13.6 s13.6 s

Speed

14 to fix22
  • Reduce unused JavaScript

    4.2 s · 1.4 MB

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

  • Use efficient cache lifetimes

    2.1 s · 1.1 MB

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

  • Improve image delivery

    1.7 s · 361 KiB

    2 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • Main-thread work: 18.2 s

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

  • script.ac adds 1.8 s

    1.8 s

    script.ac costs a phone 1.8 s of main-thread work and 85 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.

  • Render-blocking requests

    1.8 s

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

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

  • 4,730 HTML elements

    The page has 4,730 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 (script.ac, Google Tag Manager and piano and others), adding 2.9 MB and 5.0 s of main-thread time.

  • Google Tag Manager adds 716 ms

    716 ms

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

  • piano adds 566 ms

    566 ms

    piano costs a phone 566 ms of main-thread work and 325 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.

  • Osano CMP adds 501 ms

    501 ms

    Osano CMP costs a phone 501 ms of main-thread work and 95 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 495 ms. During a long task the page ignores taps.

  • Pubmatic adds 413 ms

    413 ms

    Pubmatic costs a phone 413 ms of main-thread work and 134 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

    47 KiB

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 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.

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 19.6 s

    19.6 s

    Your largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “O'Hare Airport's People Mover, as seen in 2021.”.

  • Time to Interactive: 52.5 s

    52.5 s

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

  • Speed Index: 13.8 s

    13.8 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.161

    0.161

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

  • 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

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 147 ms

    147 ms

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

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

    528 ms

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

Images and page weight

1 to fix70
  • Page weight: 7.6 MB in 1,223 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 1,223 requests on a phone: scripts 4.0 MB (149), other files 1.7 MB (505) and images 946 KiB (424). Under 2 MB keeps phones on slow connections fast.

  • About 2.1 g of CO₂ per visit

    2.14 g

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

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

5 to fixGoogle 8192
  • 3 buttons without a name

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • 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 (7 elements)

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

  • 5 links without text

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 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 7788
  • No H1 headline

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 553 internal links, 164 external

    The homepage links to 553 pages on suntimes.com and 164 external pages.

7 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “Chicago news, politics, sports, entertainment and more from America’s hardest-working paper.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Chicago Sun-Times: Chicago news, politics, sports and more”.

  • Canonical URL set

    The canonical URL is https://chicago.suntimes.com/.

  • Structured data in place

    Structured data found: WebPage.

  • 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://chicago.suntimes.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 Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://chicago.suntimes.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 (2,978 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://chicago.suntimes.com/become-a-member, https://chicago.suntimes.com/home-delivery-faq, https://chicago.suntimes.com/news, https://chicago.suntimes.com/architecture-design, https://chicago.suntimes.com/chicago and https://chicago.suntimes.com/crime and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://chicago.suntimes.com/become-a-member, https://chicago.suntimes.com/pages/activate, https://chicago.suntimes.com/home-delivery-faq and https://chicago.suntimes.com/la-voz have 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 194 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.

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

  • 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

5 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://ams-pageview-public.s3.amazonaws.com/1x1-pixel.png?id=feb6b46121fe.

  • 34 third-party cookies

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

  • 15 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token ')'”.

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

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

3 checks passed
  • 22 calls to action

    The homepage has 22 calls to action, for example “Subscribe to the E-Paper”, “Subscribe” and “Sun-Times Shop”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 5 of them by other companies (measured from a US location before any click).

  • 69 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 suntimes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Microsoft Clarity
Hosting
CloudFront

Hiring

Hiring
10 open roles
Teams
CONTENT - CHICAGO SUN-TIMES (3), Marketing - WBEZ (2), Broadcasting - WBEZ (1), Content Administration (1)
Job board
greenhouse

Company

Founded
1948
Headquarters
Chicago

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on suntimes.com, including 23 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