Skip to content
Audit Complete

Results for https://dailykos.com

Visit site
E-commerce · estimated Tracking: purchases
Spain Spain · Madrid Completed: Apr 22, 2026 00:52 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 16.4s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Cart Functionality · 356 peers
You 72
·
Avg 72
At average
0 50 100
Better than 35% of Cart Functionality sites See full Cart Functionality benchmark →
WordPress · 413 peers
You 72
·
Avg 74
At average
0 50 100
Better than 18% of WordPress sites See full WordPress benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

224 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdailykos.com)](https://beavercheck.com/results/d2f7fe97-f072-4bea-872e-0697323ec3df)
<a href="https://beavercheck.com/results/d2f7fe97-f072-4bea-872e-0697323ec3df"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdailykos.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdailykos.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 16.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 16.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 4 warning

7 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 16.4s to load

+12% bounce

Users abandon at ~3s — you're 13.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

399 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $0.84/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

$500

5h · 5 findings

Monthly returns

$0.84 /mo

~$10 / year

  • Bandwidth savings $0.84

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,510 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 2 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+8 more

Bandwidth Waste

$0.84 /mo

10485.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.0 MB per page load
    Saves $0.84/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

34
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.28 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

16.37 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.13 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.53 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

26.28 s

Detailed Report

Audit breakdown by category with detailed findings.

34

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:53.299 source:map[column:28926 line:1 type:source-location url:https://us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:89.269 source:map[type:text value:[unattributed]]] map[reflowTime:66.107 source:map[column:31494 line:0 type:source-location url:https://cdn.viafoura.net/entry/index.js urlProvider:network]] map[reflowTime:53.299 source:map[column:13242 line:0 type:source-location url:https://us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5 urlProvider:network]] map[reflowTime:31.333 source:map[column:107797 line:0 type:source-location url:https://beacon-v2.helpscout.net/static/js/full-beacon-init.2f5f9204.chunk.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Brawn on the lawn figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
www.dailykos.com/wp-content/uploads/sites/2/2026/04/brawn.webp?resize=252,30069.8 KiB62.8 KiB
Transportation chief wants AI to manage your air travel safety figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2025/11/AP25279796254436-1.jp...31.1 KiB24.6 KiB
Trump’s sagging polls and inflation lies foretell Democrat midterm wins figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/The-Recap-9.jpg?resiz...21.8 KiB17.3 KiB
Just look at my ear! figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/20260417edtcc-a.jpg?r...46.4 KiB13.4 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 873 ms
URLTime Spent
dailykos.com/873 ms
www.dailykos.com/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
www.dailykos.com/1.4 s

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
/f/AGSKWxXKT7FLTJZ_3cJeVLqEzkk2R_HHLdeQeuRqRN47XE2rUOdWhd...2.1 s1.6 s72 ms
www.dailykos.com/2.1 s68 ms6.6 ms
Unattributable1.1 s106 ms0.0 ms
us-assets.i.posthog.com/static/array.js862 ms841 ms13 ms
beacon-v2.helpscout.net/static/js/full-beacon-init.2f5f9204.chunk.js633 ms417 ms26 ms
cdn.viafoura.net/chunks/150.e8dd543747c61101ee67.js617 ms554 ms0.8 ms
cdn.viafoura.net/entry/index.js354 ms85 ms3.2 ms
fundingchoicesmessages.google.com/i/154013155?ers=3349 ms319 ms24 ms
cdn.intergient.com/pageos/V.20260416.1/main.121b53b8564b55f13382.js298 ms238 ms38 ms
cdn.viafoura.net/vf-v2.js288 ms211 ms67 ms
www.googletagmanager.com/gtag/js?id=G-9ZM1F50YPZ&cx=c&gtm=4e64h1h1278 ms233 ms43 ms
btloader.com/tag?o=5150306120761344&upapi=true275 ms254 ms12 ms
cdn.viafoura.net/chunks/entry-topic-follow.efe879650eb278c66ff3.js252 ms249 ms0.3 ms
cdn.viafoura.net/chunks/142.604b6661d6c6835e3317.js247 ms231 ms1.9 ms
cdn.intergient.com/prebid/prebid.05eaa3284c60ad6e334d.js222 ms151 ms69 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js192 ms142 ms41 ms
www.googletagmanager.com/gtm.js?id=GTM-5Z2LL8GF181 ms147 ms30 ms
us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5134 ms109 ms14 ms
introjava.com/build/o66m2dvjaj6n-prod.js100 ms90 ms7.8 ms
cdn.parsely.com/keys/dailykos.com/p.js?ver=3.23.192 ms83 ms4.4 ms
securepubads.g.doubleclick.net/tag/js/gpt.js?network-code=15401315587 ms72 ms14 ms
cdn.viafoura.net/chunks/da.b2d74e500032ae57e5e8.js82 ms69 ms9.3 ms
/_static/??-eJyt08FOBCEMANAfkmU9uBMPxm8p0GE6A5SFsrp/7zgaE...73 ms40 ms3.4 ms
cdn.viafoura.net/chunks/entry-tray.bd2ccb5e65815d83c262.js65 ms57 ms0.6 ms
www.paypalobjects.com/donate/sdk/donate-sdk.js65 ms44 ms20 ms
cdn.viafoura.net/chunks/180.d5867a49a2e94e0094b5.js62 ms61 ms0.2 ms
secure.actblue.com/cf/assets/actblue.js60 ms57 ms2.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation6.9 s
Style & Layout2.0 s
Other1.4 s
Script Parsing & Compilation571 ms
Rendering440 ms
Parse HTML & CSS336 ms
Garbage Collection243 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.8 KiB
URLTransfer SizeEst Savings
prod.uidapi.com/static/js/uid2-sdk-2.0.0.js14.8 KiB5.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Donate with PayPal button div.donation-ask__paypal > div.paypal-donate-button-container > div#donation-ask-paypal-0 > img#donate-button
/wp-content/themes/daily-kos-theme/assets/images/paypal-b...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 6 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 310 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
DAILY KOS div.wp-block-group > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dk-header-group > div.wp-block-group > div.wp-block-site-logo > a.custom-logo-link div.dk-header-group > div.wp-block-group > div.wp-block-site-logo > a.custom-logo-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
News div.wp-block-group > div.taxonomy-category > div.inner > a
Cartoon div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Video div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Video div.wp-block-group > div.taxonomy-category > div.inner > a
Courts div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Cartoon div.wp-block-group > div.taxonomy-category > div.inner > a
Just look at my ear! div.card > div.wp-block-group > h3.wp-block-post-title > a
Announcements div.wp-block-group > div.taxonomy-category > div.inner > a
Daily Kos div.wp-block-group > div.taxonomy-category > div.inner > a
DK6 Day 7: The Running List div.card > div.wp-block-group > h3.wp-block-post-title > a
National div.wp-block-group > div.taxonomy-category > div.inner > a
Video div.wp-block-group > div.taxonomy-category > div.inner > a
Congress div.wp-block-group > div.taxonomy-category > div.inner > a
Courts div.wp-block-group > div.taxonomy-category > div.inner > a
National div.wp-block-group > div.taxonomy-category > div.inner > a
Cartoon div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
White House div.wp-block-group > div.taxonomy-category > div.inner > a
Announcements div.wp-block-group > div.taxonomy-category > div.inner > a
Daily Kos div.wp-block-group > div.taxonomy-category > div.inner > a
DK6 Day 4: Some Behind The Scenes Info div.card > div.wp-block-group > h3.wp-block-post-title > a
Announcements div.wp-block-group > div.taxonomy-category > div.inner > a
Daily Kos div.wp-block-group > div.taxonomy-category > div.inner > a
Welcome to your new Daily Kos div.card > div.wp-block-group > h3.wp-block-post-title > a
White House div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Elections div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Announcements div.wp-block-group > div.taxonomy-category > div.inner > a
Daily Kos div.wp-block-group > div.taxonomy-category > div.inner > a
Elections div.wp-block-group > div.taxonomy-category > div.inner > a
Elections div.wp-block-group > div.taxonomy-category > div.inner > a
About Daily Kos nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Subscribe nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Newsletter nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Code of Ethics nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Rules of the Road (Community Guidelines) nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Masthead nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Terms of Service nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Privacy Policy nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Do Not Sell or Share My Personal Information nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
DMCA Copyright Notice nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Accessibility nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Advertising nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Jobs nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Merchandise nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Contact Us nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
RSS nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
AbortError: Transition was skipped
AbortError: Transition was skipped
AbortError: Transition was skipped
AbortError: Transition was skipped
AbortError: Transition was skipped
AbortError: Transition was skipped
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

80
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

946 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.38 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

206 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.024

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.41 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.35 s

Detailed Report

Audit breakdown by category with detailed findings.

80

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:49.022 source:map[column:28926 line:1 type:source-location url:https://us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:117.633 source:map[type:text value:[unattributed]]] map[reflowTime:52.886 source:map[column:31494 line:0 type:source-location url:https://cdn.viafoura.net/entry/index.js urlProvider:network]] map[reflowTime:1.056 source:map[column:15229 line:0 type:source-location url:https://us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5 urlProvider:network]] map[reflowTime:0.727 source:map[column:497297 line:1 type:source-location url:https://cdn.intergient.com/pageos/V.20260416.1/main.121b53b8564b55f13382.js urlProvider:network]] map[reflowTime:0.779 source:map[column:315621 line:1 type:source-location url:https://cdn.intergient.com/pageos/V.20260416.1/main.121b53b8564b55f13382.js urlProvider:network]] map[reflowTime:1.916 source:map[column:673393 line:2 type:source-location url:https://cdn.viafoura.net/vf-v2.js urlProvider:network]] map[reflowTime:49.022 source:map[column:13242 line:0 type:source-location url:https://us-assets.i.posthog.com/static/posthog-recorder.js?v=1.369.5 urlProvider:network]] map[reflowTime:11.47 source:map[column:449 line:19 type:source-location url:/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads-contributor.ContributorServingResponseClientJs.en_US.DsKGN-qqfrQ.es5.O/d=1/exm=kernel_loader,loader_js_executable/ed=1/rs=AJlcJMz2YRLcgcQw7bN4By8dD3CBlNJULw/m=web_iab_tcf_v2_wall_executable urlProvider:network]] map[reflowTime:32.078 source:map[column:15892 line:5 type:source-location url:https://beacon-v2.helpscout.net/static/js/main.c8916e6f.js urlProvider:network]] map[reflowTime:30.29 source:map[column:107797 line:0 type:source-location url:https://beacon-v2.helpscout.net/static/js/full-beacon-init.2f5f9204.chunk.js urlProvider:network]] map[reflowTime:3.99 source:map[column:90987 line:0 type:source-location url:https://beacon-v2.helpscout.net/static/js/full-beacon-init.2f5f9204.chunk.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Community Story div.card > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail
/wp-content/themes/daily-kos-theme/assets/images/Communit...75.2 KiB73.6 KiB
Brawn on the lawn figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
www.dailykos.com/wp-content/uploads/sites/2/2026/04/brawn.webp?resize=252,30069.8 KiB68.4 KiB
Trump’s sagging polls and inflation lies foretell Democrat midterm wins figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/The-Recap-9.jpg?resiz...32.1 KiB31.3 KiB
Transportation chief wants AI to manage your air travel safety figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2025/11/AP25279796254436-1.jp...31.1 KiB29.3 KiB
Trump’s media hitman to rub elbows with his victims figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/images/1460641/original/AP191...40.3 KiB28.2 KiB
Idiots, warmongers, and Catholics figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/20260416edohc-a.jpg?r...22.0 KiB20.4 KiB
What’s REALLY wrong with RFК the lesser? figure.wp-block-post-featured-image > a > figure.wp-block-image > img.attachment-post-thumbnail
www.dailykos.com/wp-content/uploads/sites/2/2026/04/rfkjr.jpg26.9 KiB15.0 KiB
Gardening and Hope for Spring figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/IMG_20260421_2045342-...16.3 KiB11.7 KiB
Contemporary Fiction Views: Discoveries div.card > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/Book-corner.jpg?resiz...13.2 KiB7.4 KiB
Stomp My Flag and I’ll Stomp Your Face: Musings of a Phony Patriot figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/Stomp-My-Flag-I-Will-...10.8 KiB7.1 KiB
Virginia Redistricting Referendum Narrowly Passes figure.wp-block-post-featured-image > a > figure.wp-post-image-figure > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/AP26090566244184.jpg?...15.1 KiB5.4 KiB
Evening Shade—Resistance Rising—Tuesday, April 21, 2026 div.card > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail
/wp-content/uploads/sites/2/2026/04/shawshank.jpeg?resize...9.7 KiB5.1 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 317 ms
URLTime Spent
dailykos.com/317 ms
www.dailykos.com/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
www.dailykos.com/1.4 s

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.7 s
Style & Layout497 ms
Other404 ms
Script Parsing & Compilation141 ms
Rendering139 ms
Garbage Collection71 ms
Parse HTML & CSS66 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with WebSocket cannot enter back/forward cache.Pending browser support

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.8 KiB
URLTransfer SizeEst Savings
prod.uidapi.com/static/js/uid2-sdk-2.0.0.js14.8 KiB5.8 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Donate with PayPal button div.donation-ask__paypal > div.paypal-donate-button-container > div#donation-ask-paypal-0 > img#donate-button
/wp-content/themes/daily-kos-theme/assets/images/paypal-b...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 10 long tasks found
Network Requests
Network Round Trip Times 120 ms
Server Backend Latencies 120 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SIGN UP div.wp-block-group > div.dk-header-user-actions > span.dk-header-user-actions__auth-links > a.dk-header-user-actions__auth-link
LOGIN div.wp-block-group > div.dk-header-user-actions > span.dk-header-user-actions__auth-links > a.dk-header-user-actions__auth-link
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
Group div.entry-content > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading
DAILY KOS div.wp-block-group > div.wp-block-columns > div.wp-block-column > h6.wp-block-heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dk-header-group > div.wp-block-group > div.wp-block-site-logo > a.custom-logo-link div.dk-header-group > div.wp-block-group > div.wp-block-site-logo > a.custom-logo-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
News div.wp-block-group > div.taxonomy-category > div.inner > a
Cartoon div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Video div.wp-block-group > div.taxonomy-category > div.inner > a
National div.wp-block-group > div.taxonomy-category > div.inner > a
Cartoon div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
White House div.wp-block-group > div.taxonomy-category > div.inner > a
News div.wp-block-group > div.taxonomy-category > div.inner > a
Announcements div.wp-block-group > div.taxonomy-category > div.inner > a
Daily Kos div.wp-block-group > div.taxonomy-category > div.inner > a
Elections div.wp-block-group > div.taxonomy-category > div.inner > a
Elections div.wp-block-group > div.taxonomy-category > div.inner > a
Subscribe nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content
Newsletter nav.has-x-small-font-size > ul.wp-block-navigation__container > li.has-x-small-font-size > a.wp-block-navigation-item__content

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback