denverpost.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.3 s

  3.3 s

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

• Real-user FCP: 2.1 s

  2.1 s

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

• Largest content (LCP) held steady for real visitors

  +5%

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

• Page weight: 21.2 MB

  21.2 MB

  Your homepage downloads 21.2 MB on a phone, 17.6 MB of it images (83%). Under 2 MB keeps phones on slow connections fast.

• 1 image below the first screen load straight away

  1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 6.0 g of CO₂ per visit

  6.02 g

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

• Frames without titles

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

  Elements (1)

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

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 1 form field without a label

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

  View source

• Title is long (83 characters)

  Your title is 83 characters, so Google will cut it off around 60: “The Denver Post – Colorado breaking news, sports, business, weather, entertainment.”.

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“The Denver Post” and “”). One clear main headline is easier for people and search engines.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 302 internal links, 45 external

  The homepage links to 302 pages on denverpost.com and 45 external pages.

• robots.txt blocks 6 AI answer engine crawlers

  6 of 6

  Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-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.

• No llms.txt

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

• 2 pages without a meta description

  https://www.denverpost.com/news/education and https://www.denverpost.com/tag/photos-and-videos have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 15 internal pages checked

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

• 4 broken images

  4 images failed to load on a phone, for example https://s.w.org/images/core/emoji/17.0.2/svg/1f1fa-1f1f8.svg.

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Sailthru is not defined”.

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• Thin social proof

  Social proof on the homepage: 6 testimonial or review blocks. 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 map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

• 9 trackers load before any consent

  9

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

• 36 cookies set on arrival

  36

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

• 105 other companies contacted

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