Skip to content
Audit Complete

Results for https://schneier.com

Visit site
E-commerce · estimated Tracking: purchases
Spain Spain · Madrid Completed: Apr 22, 2026 20:00 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)
C77

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

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.

Lean and efficient — low environmental impact per visit.

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

WooCommerce · 66 peers
You 77
·
Avg 75
At average
0 50 100
Better than 65% of WooCommerce sites See full WooCommerce benchmark →
WordPress · 546 peers
You 77
·
Avg 74
At average
0 50 100
Better than 75% 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

No Content-Security-Policy header found

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

Security › Content Security Policy
3

1 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
4

2 control(s) without accessible label

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

Accessibility › Form Accessibility
5

No <main> landmark found

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

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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%2Fschneier.com)](https://beavercheck.com/results/34787017-79e5-47c5-9314-5e9c1ccc8bbb)
<a href="https://beavercheck.com/results/34787017-79e5-47c5-9314-5e9c1ccc8bbb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fschneier.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fschneier.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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

7 warning

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

Speed (1)

Page loads in 3.2s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 657ms over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

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

Usability (2)

2 form field(s) without a label

+4% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% 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

$550 investment → $1,237/month returns + USD 150,000 risk avoided

Payback period: < 1 month First-year ROI: +2599%

Investment

$550

6h · 5 findings

Monthly returns

$1,237 /mo

~$14,843 / year

  • Conversions recovered $1,237
  • Bandwidth savings $0.07

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

Payback period

0 12mo 24mo

$100 — 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

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 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

$12,500 / month at risk

~$150,001 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • 2 of 2 <nav> elements are unlabeled
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

+4 more

Bandwidth Waste

$0.07 /mo

856.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~86 KB per page load
    Saves $0.07/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 5 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.

89
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
55
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
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.71 s

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

3.16 s

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

42 ms

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

0.004

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

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

3.92 s

Detailed Report

Audit breakdown by category with detailed findings.

89

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.

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: 777 ms
URLTime Spent
schneier.com/777 ms
www.schneier.com/0.0 ms

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

Diagnostics

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 2.2 KiB
URLTransfer SizeEst Savings
/wp-content/themes/schneier/assets/vendor/socialsharepriv...7.2 KiB2.2 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
Support Bloggers' Rights! section > div#schneier_promotion-2 > a > img#effbutton
www.schneier.com/wp-content/themes/schneier/assets/images/join-eff@2x.png
Rewiring Democracy section > div#schneier_latest_book-3 > a > img.sidepic
www.schneier.com/wp-content/uploads/2025/05/book-rewiring-200w.jpg
Defend Privacy--Support Epic section > div#schneier_promotion-2 > a > img
www.schneier.com/wp-content/themes/schneier/assets/images/support-epic@2x.png
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img
www.schneier.com/wp-content/uploads/2019/10/Bruce-Schneier.jpg
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Atom div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/rss-32px.png
Facebook div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/facebook-32px.png
Twitter div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/twitter-32px.png
Email div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/email-32px.png

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

Max Potential First Input Delay 100 ms
Use efficient cache lifetimes
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 279 KiB
JavaScript execution time 0.2 s
Minimizes main-thread work 0.8 s
Avoid long main-thread tasks 6 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 30 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 0 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
55

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.

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
Search div#sidebar-one > section > div#schneier_search-3 > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section > div#schneier_search-3 > form > input#search section > div#schneier_search-3 > form > input#search

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
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
public-interest technologist section > div#schneier_about-2 > p.small > a
blog section > div#schneier_about-2 > p.small > a
newsletter section > div#schneier_about-2 > p.small > a
Kennedy School section > div#schneier_about-2 > p.small > a
EFF section > div#schneier_about-2 > p.small > a
Inrupt, Inc. section > div#schneier_about-2 > p.small > a

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

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
3d printers div#schneier_archives-2 > ul.top-tags > li > a
9/11 div#schneier_archives-2 > ul.top-tags > li > a
A Hacker's Mind div#schneier_archives-2 > ul.top-tags > li > a
Aaron Swartz div#schneier_archives-2 > ul.top-tags > li > a
academic div#schneier_archives-2 > ul.top-tags > li > a
academic papers div#schneier_archives-2 > ul.top-tags > li > a
accountability div#schneier_archives-2 > ul.top-tags > li > a
ACLU div#schneier_archives-2 > ul.top-tags > li > a
activism div#schneier_archives-2 > ul.top-tags > li > a
Adobe div#schneier_archives-2 > ul.top-tags > li > a
advanced persistent threats div#schneier_archives-2 > ul.top-tags > li > a
adware div#schneier_archives-2 > ul.top-tags > li > a
AES div#schneier_archives-2 > ul.top-tags > li > a
Afghanistan div#schneier_archives-2 > ul.top-tags > li > a
AI div#schneier_archives-2 > ul.top-tags > li > a
air marshals div#schneier_archives-2 > ul.top-tags > li > a
air travel div#schneier_archives-2 > ul.top-tags > li > a
airgaps div#schneier_archives-2 > ul.top-tags > li > a
al Qaeda div#schneier_archives-2 > ul.top-tags > li > a
alarms div#schneier_archives-2 > ul.top-tags > li > a
algorithms div#schneier_archives-2 > ul.top-tags > li > a
alibis div#schneier_archives-2 > ul.top-tags > li > a
Amazon div#schneier_archives-2 > ul.top-tags > li > a
Android div#schneier_archives-2 > ul.top-tags > li > a
anonymity div#schneier_archives-2 > ul.top-tags > li > a
Anonymous div#schneier_archives-2 > ul.top-tags > li > a
Apache div#schneier_archives-2 > ul.top-tags > li > a
Apple div#schneier_archives-2 > ul.top-tags > li > a
Applied Cryptography div#schneier_archives-2 > ul.top-tags > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
Input buttons have discernible text.
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<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
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
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.
96

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Email div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/email-32px.png32 x 3232 x 3248 x 48
Facebook div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/facebook-32px.png32 x 3232 x 3248 x 48
Atom div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/rss-32px.png32 x 3232 x 3248 x 48
Twitter div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/twitter-32px.png32 x 3232 x 3248 x 48
Uses HTTPS
Avoids deprecated APIs
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
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
85

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
66
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
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.

814 ms

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

952 ms

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

0 ms

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

0.003

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

814 ms

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

961 ms

Detailed Report

Audit breakdown by category with detailed findings.

98

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.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: Schneier on Security
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,HEADER,0,DIV
selector: div#wrapper > div#main > header > div#header
snippet: <div id="header">

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.

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
Defend Privacy--Support Epic section > div#schneier_promotion-2 > a > img
www.schneier.com/wp-content/themes/schneier/assets/images/support-epic@2x.png30.3 KiB28.0 KiB
Schneier on Security div#wrapper > div#main > header > div#header
www.schneier.com/wp-content/themes/schneier/assets/images/header-lock.jpg24.8 KiB13.3 KiB
Rewiring Democracy section > div#schneier_latest_book-3 > a > img.sidepic
www.schneier.com/wp-content/uploads/2025/05/book-rewiring-200w.jpg23.1 KiB13.2 KiB
Support Bloggers' Rights! section > div#schneier_promotion-2 > a > img#effbutton
www.schneier.com/wp-content/themes/schneier/assets/images/join-eff@2x.png13.2 KiB9.9 KiB
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img
www.schneier.com/wp-content/uploads/2019/10/Bruce-Schneier.jpg10.4 KiB4.3 KiB

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

Diagnostics

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 2.2 KiB
URLTransfer SizeEst Savings
/wp-content/themes/schneier/assets/vendor/socialsharepriv...7.2 KiB2.2 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
Support Bloggers' Rights! section > div#schneier_promotion-2 > a > img#effbutton
www.schneier.com/wp-content/themes/schneier/assets/images/join-eff@2x.png
Rewiring Democracy section > div#schneier_latest_book-3 > a > img.sidepic
www.schneier.com/wp-content/uploads/2025/05/book-rewiring-200w.jpg
Defend Privacy--Support Epic section > div#schneier_promotion-2 > a > img
www.schneier.com/wp-content/themes/schneier/assets/images/support-epic@2x.png
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img
www.schneier.com/wp-content/uploads/2019/10/Bruce-Schneier.jpg
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
"Tweet this"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.tweet_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Facebook "Like"-Dummy ul.social_share_privacy_area > li.help_info > div.dummy_btn > img.fb_like_privacy_dummy
/wp-content/themes/schneier/assets/vendor/socialsharepriv...
Atom div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/rss-32px.png
Facebook div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/facebook-32px.png
Twitter div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/twitter-32px.png
Email div#schneier_social-4 > div#subscription-buttons > a > img
www.schneier.com/wp-content/uploads/2019/10/email-32px.png

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

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: 234 ms
URLTime Spent
schneier.com/234 ms
www.schneier.com/0.0 ms
Use efficient cache lifetimes
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 1.0 s
Max Potential First Input Delay 30 ms
Minify CSS
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 298 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.2 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 20 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 0 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
66

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.

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
Search div#sidebar-one > section > div#schneier_search-3 > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section > div#schneier_search-3 > form > input#search section > div#schneier_search-3 > form > input#search

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
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a
ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a ul.social_share_privacy_area > li.settings_info > div.settings_info_menu > a

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
public-interest technologist section > div#schneier_about-2 > p.small > a
blog section > div#schneier_about-2 > p.small > a
newsletter section > div#schneier_about-2 > p.small > a
Kennedy School section > div#schneier_about-2 > p.small > a
EFF section > div#schneier_about-2 > p.small > a
Inrupt, Inc. section > div#schneier_about-2 > p.small > a

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

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
3d printers div#schneier_archives-2 > ul.top-tags > li > a
A Hacker's Mind div#schneier_archives-2 > ul.top-tags > li > a
accountability div#schneier_archives-2 > ul.top-tags > li > a
ACLU div#schneier_archives-2 > ul.top-tags > li > a
adware div#schneier_archives-2 > ul.top-tags > li > a
AES div#schneier_archives-2 > ul.top-tags > li > a
Afghanistan div#schneier_archives-2 > ul.top-tags > li > a
AI div#schneier_archives-2 > ul.top-tags > li > a
air marshals div#schneier_archives-2 > ul.top-tags > li > a
air travel div#schneier_archives-2 > ul.top-tags > li > a
airgaps div#schneier_archives-2 > ul.top-tags > li > a
al Qaeda div#schneier_archives-2 > ul.top-tags > li > a
alarms div#schneier_archives-2 > ul.top-tags > li > a
algorithms div#schneier_archives-2 > ul.top-tags > li > a
alibis div#schneier_archives-2 > ul.top-tags > li > a
Amazon div#schneier_archives-2 > ul.top-tags > li > a
Android div#schneier_archives-2 > ul.top-tags > li > a
anonymity div#schneier_archives-2 > ul.top-tags > li > a
Anonymous div#schneier_archives-2 > ul.top-tags > li > a
antivirus div#schneier_archives-2 > ul.top-tags > li > a
Apache div#schneier_archives-2 > ul.top-tags > li > a
Apple div#schneier_archives-2 > ul.top-tags > li > a
Applied Cryptography div#schneier_archives-2 > ul.top-tags > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Input buttons have discernible text.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<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
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
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
Buttons have an accessible name
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
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.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
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
85

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#sidebar-two > section > div#schneier_about-2 > img div#sidebar-two > section > div#schneier_about-2 > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Send Feedback