Skip to content
Audit Complete

Results for https://christianitytoday.com

Visit site
Singapore Singapore · Singapore Completed: Apr 22, 2026 21:09 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)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Room to improve — your 29.2s 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

WordPress · 625 peers
You 74
·
Avg 74
At average
0 50 100
Better than 42% of WordPress sites See full WordPress benchmark →
Adobe Fonts · 206 peers
You 74
·
Avg 73
At average
0 50 100
Better than 54% of Adobe Fonts sites See full Adobe Fonts 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

Page weighs 11.8 MB (4.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 control(s) without accessible label

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

Accessibility › Form Accessibility
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%2Fchristianitytoday.com)](https://beavercheck.com/results/0432a209-7ad5-475d-8502-2639b3d15b56)
<a href="https://beavercheck.com/results/0432a209-7ad5-475d-8502-2639b3d15b56"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fchristianitytoday.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fchristianitytoday.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 29.2s 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.
Your LCP is 29.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 4 warning

6 barrier(s) likely increasing bounce by ~27%.

Speed (2)

Page takes 29.2s to load

+12% bounce

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

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

Page feels frozen for 1.6s

+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

Usability (1)

1 form field(s) without a label

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

Navigation (1)

1 broken link(s) on the page

+2% 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 → $1.19/month returns + USD 157,500 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$1.19 /mo

~$14 / year

  • Bandwidth savings $1.19

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,514 / 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
  • 1 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

+3 more

Bandwidth Waste

$1.19 /mo

14853.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.5 MB per page load
    Saves $1.19/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.

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

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

18.86 s

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

29.16 s

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

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

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

29.43 s

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

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.

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:46.145 source:map[column:3117 line:1 type:source-location url:https://www.npttech.com/advertising.js 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:95.899 source:map[column:132404 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:0.405 source:map[column:132636 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:1.361 source:map[column:3330 line:0 type:source-location url:https://www.npttech.com/advertising.js urlProvider:network]] map[reflowTime:44.784 source:map[column:3408 line:0 type:source-location url:https://www.npttech.com/advertising.js urlProvider:network]] map[reflowTime:2.615 source:map[type:text value:[unattributed]]] map[reflowTime:0.182 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.728 source:map[column:327363 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.101 source:map[column:45016 line:5 type:source-location url:https://cdn.cxense.com/cx.js urlProvider:network]] map[reflowTime:1.615 source:map[column:33383 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.28 source:map[column:33416 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.559 source:map[column:297534 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.351 source:map[column:55 line:919 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-2P7KM6QEMN&cx=c&gtm=4e64k0 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
karen-swallow-prior-birds-bees-babies div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/Sam-Cedar-KSP-Thumbnail-2.jpg...32.5 KiB24.9 KiB
Churchgoers attend a worship service created entirely by ChatGPT in Bavaria. div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/ai-pastors-lifeway-research.j...32.1 KiB19.8 KiB
Smoke billows from a fire next to Azadi Tower following strikes near Mehrabad I… div.main-article > div.featured-image > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/just-war-ends-means.jpg?resiz...25.4 KiB19.5 KiB
A CT magazine cover and an film still from Blade Runner. div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/attempts-cultural-crossover.j...22.6 KiB17.3 KiB
Gen Z women are becoming less religious. div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/gen-z-women-religion-study.jp...18.8 KiB14.4 KiB
cover of the books To Live Well, by Alan Noble, Spellbound by Molly Worthen, an… div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/03/Michael-Books-2.jpg?resize=76...17.2 KiB13.2 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
value: no origins were preconnected
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

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: 985 ms

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.

Estimated savings: 760 ms 69.0 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

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 Evaluation4.6 s
Other1.2 s
Script Parsing & Compilation830 ms
Style & Layout789 ms
Parse HTML & CSS214 ms
Garbage Collection161 ms
Rendering111 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 a sub frame.Actionable

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
Icon for Twitter ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_x_grayscale.svg
Icon for Twitter ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_x_grayscale.svg
Icon for WhatsApp ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2024/10/icon_whatsapp.svg
Icon for WhatsApp ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2024/10/icon_whatsapp.svg
Christianity Today Logo div#stpeter > footer.site-footer > div.footer-logo > img.custom-footer-logo
www.christianitytoday.com/wp-content/uploads/2024/07/logo_ct_white_b9154b.svg
Icon for YouTube ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_youtube_grayscale.svg
Icon for YouTube ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_youtube_grayscale.svg
Christianity Today Logo div.site-header-content > div.site-branding > a.custom-logo-link > img.custom-logo
/wp-content/uploads/2024/07/logo_christianitytoday_black_...
Icon for Facebook ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_facebook_grayscale.svg
Icon for Instagram ul > li > a > img
/wp-content/uploads/2023/10/icon_instagram_grayscale.svg
Icon for RSS ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_rss_grayscale.svg
Icon for Telegram ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_telegram_grayscale.svg
Icon for Facebook ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_facebook_grayscale.svg
Icon for Instagram ul > li > a > img
/wp-content/uploads/2023/10/icon_instagram_grayscale.svg
Icon for RSS ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_rss_grayscale.svg
Icon for Telegram ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_telegram_grayscale.svg

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
Minify JavaScript
User Timing marks and measures 23 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 250 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 0 ms
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
Atta Kenare / Contributor / Getty section.wp-block-ct > div.main-article > div.featured-image > p.image-caption
GUEST COLUMNIST div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
PAID CONTENT div#dynamic-post-river > div.ct-article-card > div.thumbnail > span.ct-article-sponsor
PAID CONTENT FOR COMPASSION INTERNATIONAL div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-kicker
CT STAFF; CONTRIBUTOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
Sign up now. div.newsletter-signup > div.content > p > button.signup
COLUMNIST div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
CONTRIBUTOR; CONTRIBUTOR; CONTRIBUTOR, QUALMS & PROVERBS div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF EDITOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF EDITOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF WRITER div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
Subscribe for as low as $6/mo div.newsletter-signup > div.content > p > a
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
STAFF WRITER ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CORRESPONDENT ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST; CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR; CONTRIBUTOR; CONTRIBUTOR, QUALMS & PROVERBS ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CT STAFF ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
STAFF WRITER ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
CONTRIBUTOR ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF WRITER ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
COLUMNIST ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CT STAFF div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
SUBSCRIBE div.wp-block-group > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
BACK TO TOP div#stpeter > footer.site-footer > div.back-to-top > a
GIVE div.wp-block-group > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#stpeter > div#piano-inline > div.tp-container-inner > iframe#offer_dfa70c471ab776f3cf60-0 div#stpeter > div#piano-inline > div.tp-container-inner > iframe#offer_dfa70c471ab776f3cf60-0

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.wp-block-ct-magazine-content > div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a
ul.article-list > li > div.thumbnail > a ul.article-list > li > div.thumbnail > 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.

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
`[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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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 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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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
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
AttributionReporting
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

81
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
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.

1.38 s

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

1.54 s

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

200 ms

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

0.005

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

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

4.47 s

Detailed Report

Audit breakdown by category with detailed findings.

81

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.

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:20.41 source:map[column:129422 line:1 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g 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:158.615 source:map[type:text value:[unattributed]]] map[reflowTime:15.703 source:map[column:44658 line:10 type:source-location url:https://securepubads.g.doubleclick.net/tag/js/gpt.js?ver=1.0 urlProvider:network]] map[reflowTime:9.377 source:map[column:34216 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:14.029 source:map[column:49577 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:11.453 source:map[column:45540 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:4.684 source:map[column:237248 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.24 source:map[column:48581 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:1.167 source:map[column:83422 line:0 type:source-location url:https://www.christianitytoday.com/wp-content/themes/christianitytoday/build/index.js?m=1776411179g urlProvider:network]] map[reflowTime:0.243 source:map[column:400730 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:2.146 source:map[column:327363 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:6.125 source:map[column:21381 line:0 type:source-location url:https://www.christianitytoday.com/_static/??/wp-content/themes/christianitytoday/build/piano.js,/wp-includes/js/dist/dom-ready.min.js,/wp-includes/js/dist/hooks.min.js?m=1776411179j urlProvider:network]] map[reflowTime:1.035 source:map[column:6492 line:0 type:source-location url:https://www.christianitytoday.com/_static/??/wp-content/themes/christianitytoday/build/piano.js,/wp-includes/js/dist/dom-ready.min.js,/wp-includes/js/dist/hooks.min.js?m=1776411179j urlProvider:network]] map[reflowTime:1.081 source:map[column:33383 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.291 source:map[column:33416 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.473 source:map[column:297534 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.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
Smoke billows from a fire next to Azadi Tower following strikes near Mehrabad I… div.main-article > div.featured-image > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/just-war-ends-means.jpg?resiz...83.8 KiB56.6 KiB
Arial view of the Strait of Hormuz with a "closed" sign on it. div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/Episode-272.png?resize=301,16948.9 KiB40.7 KiB
Malcolm Guite sitting by a tree. div.ct-article-card > div.thumbnail > a.ct-article-card-link > img.ct-article-card-image
/wp-content/uploads/2026/04/galahad-grail-guite-profile.j...21.2 KiB12.9 KiB
This Great and Complicated Place div.ct-podcast-river-posts > a.ct-podcast-river-post > div.ct-podcast-river-image > img.attachment-medium
www.christianitytoday.com/wp-content/uploads/2024/12/TGCP_art.png?resize=82,829.0 KiB7.9 KiB
div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a > img div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a > img
www.christianitytoday.com/wp-content/uploads/2026/03/MA26_Front_Cover.jpg?w=32428.5 KiB6.3 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
value: no origins were preconnected
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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

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: 460 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

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.

Estimated savings: 40 ms 66.7 KiB

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.2 s
Other371 ms
Style & Layout297 ms
Script Parsing & Compilation209 ms
Parse HTML & CSS55 ms
Rendering53 ms
Garbage Collection47 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 a sub frame.Actionable

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
Icon for Twitter ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_x_grayscale.svg
Icon for Twitter ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_x_grayscale.svg
Icon for WhatsApp ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2024/10/icon_whatsapp.svg
Icon for WhatsApp ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2024/10/icon_whatsapp.svg
Christianity Today Logo div#stpeter > footer.site-footer > div.footer-logo > img.custom-footer-logo
www.christianitytoday.com/wp-content/uploads/2024/07/logo_ct_white_b9154b.svg
Icon for YouTube ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_youtube_grayscale.svg
Icon for YouTube ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_youtube_grayscale.svg
Christianity Today Logo div.site-header-content > div.site-branding > a.custom-logo-link > img.custom-logo
/wp-content/uploads/2024/07/logo_christianitytoday_black_...
Icon for Facebook ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_facebook_grayscale.svg
Icon for Instagram ul > li > a > img
/wp-content/uploads/2023/10/icon_instagram_grayscale.svg
Icon for RSS ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_rss_grayscale.svg
Icon for Telegram ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_telegram_grayscale.svg
Icon for Facebook ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_facebook_grayscale.svg
Icon for Instagram ul > li > a > img
/wp-content/uploads/2023/10/icon_instagram_grayscale.svg
Icon for RSS ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_rss_grayscale.svg
Icon for Telegram ul > li > a > img
www.christianitytoday.com/wp-content/uploads/2023/10/icon_telegram_grayscale.svg

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

Max Potential First Input Delay 130 ms
Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 23 user timings
JavaScript execution time 1.2 s
Avoid long main-thread tasks 8 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 280 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 2 layout shifts found
INP breakdown
Avoid non-composited animations
87

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
Atta Kenare / Contributor / Getty section.wp-block-ct > div.main-article > div.featured-image > p.image-caption
GUEST COLUMNIST div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
PAID CONTENT div#dynamic-post-river > div.ct-article-card > div.thumbnail > span.ct-article-sponsor
PAID CONTENT FOR COMPASSION INTERNATIONAL div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-kicker
CT STAFF; CONTRIBUTOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div#dynamic-post-river > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
Sign up now. div.newsletter-signup > div.content > p > button.signup
COLUMNIST div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
CONTRIBUTOR; CONTRIBUTOR; CONTRIBUTOR, QUALMS & PROVERBS div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF EDITOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF EDITOR div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
STAFF WRITER div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-articles > div.ct-article-card > p.ct-article-card-byline-descriptor
Subscribe for as low as $6/mo div.newsletter-signup > div.content > p > a
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
STAFF WRITER ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CORRESPONDENT ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
STAFF EDITOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
COLUMNIST; CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
PRESIDENT & CEO ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
CT STAFF ul.article-list > li > div.post-content > p.ct-article-card-byline-descriptor
STAFF WRITER ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
CONTRIBUTOR ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF WRITER ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
STAFF EDITOR ul > li > div.writer-content > p.byline-descriptor
COLUMNIST ul > li > div.writer-content > p.byline-descriptor
CT STAFF ul > li > div.writer-content > p.byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CT STAFF div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
CONTRIBUTOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
STAFF EDITOR div.swiper-wrapper > div.ct-article-card > div.card-content > p.ct-article-card-byline-descriptor
SUBSCRIBE div.wp-block-group > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
BACK TO TOP div#stpeter > footer.site-footer > div.back-to-top > a
GIVE div.wp-block-group > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#stpeter > div#piano-inline > div.tp-container-inner > iframe#offer_dfa70c471ab776f3cf60-0 div#stpeter > div#piano-inline > div.tp-container-inner > iframe#offer_dfa70c471ab776f3cf60-0

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.wp-block-ct-magazine-content > div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a div.wp-block-ct-magazine-content > div.wp-block-ct-magazine-cover-wrap > figure.wp-block-ct-magazine-cover-image > a
ul.article-list > li > div.thumbnail > a ul.article-list > li > div.thumbnail > 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.

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
div#header-search-container > form.search-form > label > input#search-field-2720302464 div#header-search-container > form.search-form > label > input#search-field-2720302464

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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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
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
AttributionReporting
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