Skip to content
Audit Complete

Results for https://newadvent.org

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 22:08 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

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

Google Search Console · 3514 peers
You 72
·
Avg 73
At average
0 50 100
Better than 33% of Google Search Console sites See full Google Search Console benchmark →
Google Workspace · 1643 peers
You 72
·
Avg 73
At average
0 50 100
Better than 25% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

1 control(s) without accessible label

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

Accessibility › Form Accessibility
5

16 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
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%2Fnewadvent.org)](https://beavercheck.com/results/8cf8dca0-e1e2-4056-9ae2-8f010bcf5ddf)
<a href="https://beavercheck.com/results/8cf8dca0-e1e2-4056-9ae2-8f010bcf5ddf"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnewadvent.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnewadvent.org

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.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 8 warning

10 barrier(s) likely increasing bounce by ~36%.

Speed (2)

Page loads in 2.8s

+5% bounce

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

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

Page feels frozen for 685ms

+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 (2)

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

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

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

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

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

Investment

$450

4h · 5 findings

Monthly returns

$567 /mo

~$6,809 / year

  • Conversions recovered $567
  • Bandwidth savings $0.16

Regulatory risk avoided

USD 157,500

if kept compliant

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

Payback period

0 12mo 24mo

$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

$450

4.5 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,125 / month at risk

~$157,502 / 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
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+8 more

Bandwidth Waste

$0.16 /mo

2061.9 MB/mo × 0.080 USD/GB

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

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

1.75 s

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

2.80 s

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

685 ms

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.

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

6.52 s

Detailed Report

Audit breakdown by category with detailed findings.

78

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.

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
div > div > a > img div > div > a > img
/ads/1904-5692-6703-7f6aa45e-93ec-4b44-b671-5d67698ac5d2.gif124.3 KiB59.7 KiB
div#grumi-container > div#mgcontainer-dc01b72bd7dc3f033fd99651b2af5d01 > a.mediago-placement-track_8a11b3 > img#mediago-img div#grumi-container > div#mgcontainer-dc01b72bd7dc3f033fd99651b2af5d01 > a.mediago-placement-track_8a11b3 > img#mediago-img
images.mediago.io/ML/12e6fbe87c33360908a53f0ce12f7d09__scv1__622x368.webp53.1 KiB45.6 KiB
div.homecenter > p > a > img div.homecenter > p > a > img
www.newadvent.org/images/cdimage3.jpg19.7 KiB18.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/8888-phil.jpg10.6 KiB9.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-scal.jpg10.6 KiB9.3 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/8888-mcdo.jpg9.2 KiB7.9 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-towe.jpg7.7 KiB6.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-dugi.jpg6.1 KiB4.8 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-harr.jpg5.7 KiB4.4 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9191-cudd.jpg5.6 KiB4.2 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-cald.jpg5.5 KiB4.1 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-rocc.jpg5.4 KiB4.1 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-brun.jpg5.4 KiB4.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
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
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.

URLTransfer SizeDuration
www.newadvent.org/utility/screen8.css3.5 KiB150 ms

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

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: 802 ms
URLTime Spent
newadvent.org/802 ms
www.newadvent.org/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

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

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 Evaluation2.3 s
Other749 ms
Script Parsing & Compilation331 ms
Rendering238 ms
Style & Layout196 ms
Garbage Collection76 ms
Parse HTML & CSS70 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
An iframe on the page started a navigation that did not complete.Not 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
div.homecenter > p > a > img div.homecenter > p > a > img
www.newadvent.org/images/cdimage3.jpg

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 671 KiB
Avoid long main-thread tasks 17 long tasks found
Network Requests
Network Round Trip Times 140 ms
Server Backend Latencies 200 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 70 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
68

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
The Complete List of Popes div#article > div.homeright > div > p
Click here to see the list of 133 cardinal electors (“WHO WILL BE THE NEXT POPE… div.homeright > div > p > a
St. Peter div > ol > li > a
St. Linus div > ol > li > a
St. Anacletus (Cletus) div > ol > li > a
St. Clement I div > ol > li > a
St. Evaristus div > ol > li > a
St. Alexander I div > ol > li > a
St. Sixtus I div > ol > li > a
St. Telesphorus div > ol > li > a
St. Hyginus div > ol > li > a
St. Pius I div > ol > li > a
St. Anicetus div > ol > li > a
St. Soter div > ol > li > a
St. Eleutherius div > ol > li > a
St. Victor I div > ol > li > a
St. Zephyrinus div > ol > li > a
St. Callistus I div > ol > li > a
St. Urban I div > ol > li > a
St. Pontian div > ol > li > a
St. Anterus div > ol > li > a
St. Fabian div > ol > li > a
St. Cornelius div > ol > li > a
St. Lucius I div > ol > li > a
St. Stephen I div > ol > li > a
St. Sixtus II div > ol > li > a
St. Dionysius div > ol > li > a
St. Felix I div > ol > li > a
St. Eutychian div > ol > li > a
St. Caius div > ol > li > a
St. Marcellinus div > ol > li > a
St. Marcellus I div > ol > li > a
St. Eusebius div > ol > li > a
St. Miltiades div > ol > li > a
St. Sylvester I div > ol > li > a
St. Marcus div > ol > li > a
St. Julius I div > ol > li > a
Liberius div > ol > li > a
St. Damasus I div > ol > li > a
St. Siricius div > ol > li > a
St. Anastasius I div > ol > li > a
St. Innocent I div > ol > li > a
St. Zosimus div > ol > li > a
St. Boniface I div > ol > li > a
St. Celestine I div > ol > li > a
St. Sixtus III div > ol > li > a
St. Leo I (the Great) div > ol > li > a
St. Hilarius div > ol > li > a
St. Simplicius div > ol > li > a
St. Felix III (II) div > ol > li > a
St. Gelasius I div > ol > li > a
Anastasius II div > ol > li > a
St. Symmachus div > ol > li > a
St. Hormisdas div > ol > li > a
St. John I div > ol > li > a
St. Felix IV (III) div > ol > li > a
Boniface II div > ol > li > a
John II div > ol > li > a
St. Agapetus I div > ol > li > a
St. Silverius div > ol > li > a
Vigilius div > ol > li > a
Pelagius I div > ol > li > a
John III div > ol > li > a
Benedict I div > ol > li > a
Pelagius II div > ol > li > a
St. Gregory I (the Great) div > ol > li > a
Sabinian div > ol > li > a
Boniface III div > ol > li > a
St. Boniface IV div > ol > li > a
St. Deusdedit (Adeodatus I) div > ol > li > a
Boniface V div > ol > li > a
Honorius I div > ol > li > a
Severinus div > ol > li > a
John IV div > ol > li > a
Theodore I div > ol > li > a
St. Martin I div > ol > li > a
St. Eugene I div > ol > li > a
St. Vitalian div > ol > li > a
Adeodatus (II) div > ol > li > a
Donus div > ol > li > a
St. Agatho div > ol > li > a
St. Leo II div > ol > li > a
St. Benedict II div > ol > li > a
John V div > ol > li > a
Conon div > ol > li > a
St. Sergius I div > ol > li > a
John VI div > ol > li > a
John VII div > ol > li > a
Sisinnius div > ol > li > a
Constantine div > ol > li > a
St. Gregory II div > ol > li > a
St. Gregory III div > ol > li > a
St. Zachary div > ol > li > a
Stephen II (III) div > ol > li > a
St. Paul I div > ol > li > a
Stephen III (IV) div > ol > li > a
Adrian I div > ol > li > a
St. Leo III div > ol > li > a
Stephen IV (V) div > ol > li > a
St. Paschal I div > ol > li > a
Eugene II div > ol > li > a
Valentine div > ol > li > a
Gregory IV div > ol > li > a
Sergius II div > ol > li > a
St. Leo IV div > ol > li > a
Benedict III div > ol > li > a
St. Nicholas I (the Great) div > ol > li > a
Adrian II div > ol > li > a
John VIII div > ol > li > a
Marinus I div > ol > li > a
St. Adrian III div > ol > li > a
Stephen V (VI) div > ol > li > a
Formosus div > ol > li > a
Boniface VI div > ol > li > a
Stephen VI (VII) div > ol > li > a
Romanus div > ol > li > a
Theodore II div > ol > li > a
John IX div > ol > li > a
Benedict IV div > ol > li > a
Leo V div > ol > li > a
Sergius III div > ol > li > a
Anastasius III div > ol > li > a
Lando div > ol > li > a
John X div > ol > li > a
Leo VI div > ol > li > a
Stephen VIII div > ol > li > a
John XI div > ol > li > a
Leo VII div > ol > li > a
Stephen IX div > ol > li > a
Marinus II div > ol > li > a
Agapetus II div > ol > li > a
John XII div > ol > li > a
Leo VIII div > ol > li > a
Benedict V div > ol > li > a
John XIII div > ol > li > a
Benedict VI div > ol > li > a
Benedict VII div > ol > li > a
John XIV div > ol > li > a
John XV div > ol > li > a
Gregory V div > ol > li > a
Sylvester II div > ol > li > a
John XVII div > ol > li > a
John XVIII div > ol > li > a
Sergius IV div > ol > li > a
Benedict VIII div > ol > li > a
John XIX div > ol > li > a
Benedict IX div > ol > li > a
Benedict IX div > ol > li > a
Gregory VI div > ol > li > a
Clement II div > ol > li > a
Benedict IX div > ol > li > a
Damasus II div > ol > li > a
St. Leo IX div > ol > li > a
Victor II div > ol > li > a
Stephen X div > ol > li > a
Nicholas II div > ol > li > a
Alexander II div > ol > li > a
St. Gregory VII div > ol > li > a
Blessed Victor III div > ol > li > a
Blessed Urban II div > ol > li > a
Paschal II div > ol > li > a
Gelasius II div > ol > li > a
Callistus II div > ol > li > a
Honorius II div > ol > li > a
Innocent II div > ol > li > a
Celestine II div > ol > li > a
Lucius II div > ol > li > a
Blessed Eugene III div > ol > li > a
Anastasius IV div > ol > li > a
Adrian IV div > ol > li > a
Alexander III div > ol > li > a
Lucius III div > ol > li > a
Urban III div > ol > li > a
Gregory VIII div > ol > li > a
Clement III div > ol > li > a
Celestine III div > ol > li > a
Innocent III div > ol > li > a
Honorius III div > ol > li > a
Gregory IX div > ol > li > a
Celestine IV div > ol > li > a
Innocent IV div > ol > li > a
Alexander IV div > ol > li > a
Urban IV div > ol > li > a
Clement IV div > ol > li > a
Blessed Gregory X div > ol > li > a
Blessed Innocent V div > ol > li > a
Adrian V div > ol > li > a
John XXI div > ol > li > a
Nicholas III div > ol > li > a
Martin IV div > ol > li > a
Honorius IV div > ol > li > a
Nicholas IV div > ol > li > a
St. Celestine V div > ol > li > a
Boniface VIII div > ol > li > a
Blessed Benedict XI div > ol > li > a
Clement V div > ol > li > a
John XXII div > ol > li > a
Benedict XII div > ol > li > a
Clement VI div > ol > li > a
Innocent VI div > ol > li > a
Blessed Urban V div > ol > li > a
Gregory XI div > ol > li > a
Urban VI div > ol > li > a
Boniface IX div > ol > li > a
Innocent VII div > ol > li > a
Gregory XII div > ol > li > a
Martin V div > ol > li > a
Eugene IV div > ol > li > a
Nicholas V div > ol > li > a
Callistus III div > ol > li > a
Pius II div > ol > li > a
Paul II div > ol > li > a
Sixtus IV div > ol > li > a
Innocent VIII div > ol > li > a
Alexander VI div > ol > li > a
Pius III div > ol > li > a
Julius II div > ol > li > a
Leo X div > ol > li > a
Adrian VI div > ol > li > a
Clement VII div > ol > li > a
Paul III div > ol > li > a
Julius III div > ol > li > a
Marcellus II div > ol > li > a
Paul IV div > ol > li > a
Pius IV div > ol > li > a
St. Pius V div > ol > li > a
Gregory XIII div > ol > li > a
Sixtus V div > ol > li > a
Urban VII div > ol > li > a
Gregory XIV div > ol > li > a
Innocent IX div > ol > li > a
Clement VIII div > ol > li > a
Leo XI div > ol > li > a
Paul V div > ol > li > a
Gregory XV div > ol > li > a
Urban VIII div > ol > li > a
Innocent X div > ol > li > a
Alexander VII div > ol > li > a
Clement IX div > ol > li > a
Clement X div > ol > li > a
Blessed Innocent XI div > ol > li > a
Alexander VIII div > ol > li > a
Innocent XII div > ol > li > a
Clement XI div > ol > li > a
Innocent XIII div > ol > li > a
Benedict XIII div > ol > li > a
Clement XII div > ol > li > a
Benedict XIV div > ol > li > a
Clement XIII div > ol > li > a
Clement XIV div > ol > li > a
Pius VI div > ol > li > a
Pius VII div > ol > li > a
Leo XII div > ol > li > a
Pius VIII div > ol > li > a
Gregory XVI div > ol > li > a
Blessed Pius IX div > ol > li > a
Leo XIII div > ol > li > a
St. Pius X div > ol > li > a
Benedict XV (1914-22) div > ol > li > a
Pius XI (1922-39) div > ol > li > a
Pius XII (1939-58) div > ol > li > a
St. John XXIII (1958-63) div > ol > li > a
St. Paul VI (1963-78) div > ol > li > a
John Paul I (1978) div > ol > li > a
St. John Paul II (1978-2005) div > ol > li > a
Benedict XVI (2005-2013) div > ol > li > a
Francis (2013-2025) div > ol > li > a
Leo XIV div > ol > li > a

These are opportunities to improve the legibility of your content.

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.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div.homecenter > p > a > img div.homecenter > p > a > img
div#canmobileanchoradclick > div#CANclsbtnb > a > img div#canmobileanchoradclick > div#CANclsbtnb > a > img

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#home-728x90-top > div > ins#INS30849120230911T170547990DCAA8A20DB8F4A4E94974084761DDD8B_Q8qC51776895659528 > iframe#INS30849120230911T170547990DCAA8A20DB8F4A4E94974084761DDD8B_Q8qC51776895659528_mainframe div#home-728x90-top > div > ins#INS30849120230911T170547990DCAA8A20DB8F4A4E94974084761DDD8B_Q8qC51776895659528 > iframe#INS30849120230911T170547990DCAA8A20DB8F4A4E94974084761DDD8B_Q8qC51776895659528_mainframe
div#home-300x250-sidebar > div > ins#INS30849120180430T122628683406C68808B5C4AB28F495E73E92F86EA_BCh931776895659538 > iframe#INS30849120180430T122628683406C68808B5C4AB28F495E73E92F86EA_BCh931776895659538_mainframe div#home-300x250-sidebar > div > ins#INS30849120180430T122628683406C68808B5C4AB28F495E73E92F86EA_BCh931776895659538 > iframe#INS30849120180430T122628683406C68808B5C4AB28F495E73E92F86EA_BCh931776895659538_mainframe
div > ins > ins#INS30849120240117T161552937459B53ABBADB43FB8BE12AC176458FF7_6YGjj1776895659553 > iframe#INS30849120240117T161552937459B53ABBADB43FB8BE12AC176458FF7_6YGjj1776895659553_mainframe div > ins > ins#INS30849120240117T161552937459B53ABBADB43FB8BE12AC176458FF7_6YGjj1776895659553 > iframe#INS30849120240117T161552937459B53ABBADB43FB8BE12AC176458FF7_6YGjj1776895659553_mainframe

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#article > div.homecenter > p > a div#article > div.homecenter > p > a
body.home > div#canmobileanchoradclick > div#CANclsbtnb > a body.home > div#canmobileanchoradclick > div#CANclsbtnb > 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
A body.home > div#capitalcity > nav#alpha-bar > a
B body.home > div#capitalcity > nav#alpha-bar > a
C body.home > div#capitalcity > nav#alpha-bar > a
D body.home > div#capitalcity > nav#alpha-bar > a
E body.home > div#capitalcity > nav#alpha-bar > a
F body.home > div#capitalcity > nav#alpha-bar > a
G body.home > div#capitalcity > nav#alpha-bar > a
H body.home > div#capitalcity > nav#alpha-bar > a
I body.home > div#capitalcity > nav#alpha-bar > a
J body.home > div#capitalcity > nav#alpha-bar > a
K body.home > div#capitalcity > nav#alpha-bar > a
L body.home > div#capitalcity > nav#alpha-bar > a
M body.home > div#capitalcity > nav#alpha-bar > a
N body.home > div#capitalcity > nav#alpha-bar > a
O body.home > div#capitalcity > nav#alpha-bar > a
P body.home > div#capitalcity > nav#alpha-bar > a
Q body.home > div#capitalcity > nav#alpha-bar > a
R body.home > div#capitalcity > nav#alpha-bar > a
S body.home > div#capitalcity > nav#alpha-bar > a
T body.home > div#capitalcity > nav#alpha-bar > a
U body.home > div#capitalcity > nav#alpha-bar > a
V body.home > div#capitalcity > nav#alpha-bar > a
W body.home > div#capitalcity > nav#alpha-bar > a
X body.home > div#capitalcity > nav#alpha-bar > a
Y body.home > div#capitalcity > nav#alpha-bar > a
Z body.home > div#capitalcity > nav#alpha-bar > 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.
Form elements have associated labels
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
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.
The page contains a heading, skip link, or landmark region
`[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-hidden="true"]` elements do not contain focusable descendents
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
`<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
Heading elements appear in a sequentially-descending order
`<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">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
`<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.
Identical links have the same purpose.
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.
77

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
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/8888-mcdo.jpg90 x 9088 x 88135 x 135
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/8888-phil.jpg90 x 9088 x 88135 x 135
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/8888-torr.jpg90 x 9088 x 88135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-cald.jpg90 x 9090 x 90135 x 135
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-dugi.jpg90 x 9090 x 90135 x 135
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-harr.jpg90 x 9090 x 90135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-rocc.jpg90 x 9090 x 90135 x 135
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-scal.jpg90 x 9090 x 90135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-towe.jpg90 x 9090 x 90135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9191-cudd.jpg90 x 9091 x 91135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9292-cond.jpg90 x 9092 x 92135 x 135
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9292-hoop.jpg90 x 9092 x 92135 x 135
New Advent div#capitalcity > div#header-top > a > img
www.newadvent.org/images/logo.gif153 x 36153 x 36230 x 54
div#canmobileanchoradclick > div#CANclsbtnb > a > img div#canmobileanchoradclick > div#CANclsbtnb > a > img
dtyry4ejybx0.cloudfront.net/mb/mbclose01.png16 x 1616 x 1624 x 24

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
Topics
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
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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

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.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div.homecenter > p > a > img div.homecenter > p > a > img
div#canmobileanchoradclick > div#CANclsbtnb > a > img div#canmobileanchoradclick > div#CANclsbtnb > a > 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
Document has a meta description
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.
68
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.
92
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.

633 ms

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

882 ms

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

3 ms

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.

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

2.57 s

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.

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

URLTransfer SizeDuration
www.newadvent.org/utility/screen8.css3.8 KiB70 ms

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
div > div > a > img div > div > a > img
/ads/1904-5692-6703-7f6aa45e-93ec-4b44-b671-5d67698ac5d2.gif124.3 KiB59.7 KiB
div.homecenter > p > a > img div.homecenter > p > a > img
www.newadvent.org/images/cdimage3.jpg19.7 KiB18.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/8888-phil.jpg10.6 KiB9.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-scal.jpg10.6 KiB9.3 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/8888-mcdo.jpg9.2 KiB7.9 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-towe.jpg7.7 KiB6.4 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-dugi.jpg6.1 KiB4.8 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-harr.jpg5.7 KiB4.4 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9191-cudd.jpg5.6 KiB4.3 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-cald.jpg5.5 KiB4.1 KiB
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
www.newadvent.org/images/9090-rocc.jpg5.4 KiB4.1 KiB
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
www.newadvent.org/images/9090-brun.jpg5.4 KiB4.1 KiB

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: 291 ms
URLTime Spent
newadvent.org/291 ms
www.newadvent.org/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

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
An iframe on the page started a navigation that did not complete.Not 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
div.homecenter > p > a > img div.homecenter > p > a > img
www.newadvent.org/images/cdimage3.jpg

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 705 KiB
JavaScript execution time 0.5 s
Minimizes main-thread work 0.9 s
Avoid long main-thread tasks 5 long tasks found
Network Requests
Network Round Trip Times 130 ms
Server Backend Latencies 410 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 60 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
68

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
The Complete List of Popes div#article > div.homeright > div > p
Click here to see the list of 133 cardinal electors (“WHO WILL BE THE NEXT POPE… div.homeright > div > p > a
St. Peter div > ol > li > a
St. Linus div > ol > li > a
St. Anacletus (Cletus) div > ol > li > a
St. Clement I div > ol > li > a
St. Evaristus div > ol > li > a
St. Alexander I div > ol > li > a
St. Sixtus I div > ol > li > a
St. Telesphorus div > ol > li > a
St. Hyginus div > ol > li > a
St. Pius I div > ol > li > a
St. Anicetus div > ol > li > a
St. Soter div > ol > li > a
St. Eleutherius div > ol > li > a
St. Victor I div > ol > li > a
St. Zephyrinus div > ol > li > a
St. Callistus I div > ol > li > a
St. Urban I div > ol > li > a
St. Pontian div > ol > li > a
St. Anterus div > ol > li > a
St. Fabian div > ol > li > a
St. Cornelius div > ol > li > a
St. Lucius I div > ol > li > a
St. Stephen I div > ol > li > a
St. Sixtus II div > ol > li > a
St. Dionysius div > ol > li > a
St. Felix I div > ol > li > a
St. Eutychian div > ol > li > a
St. Caius div > ol > li > a
St. Marcellinus div > ol > li > a
St. Marcellus I div > ol > li > a
St. Eusebius div > ol > li > a
St. Miltiades div > ol > li > a
St. Sylvester I div > ol > li > a
St. Marcus div > ol > li > a
St. Julius I div > ol > li > a
Liberius div > ol > li > a
St. Damasus I div > ol > li > a
St. Siricius div > ol > li > a
St. Anastasius I div > ol > li > a
St. Innocent I div > ol > li > a
St. Zosimus div > ol > li > a
St. Boniface I div > ol > li > a
St. Celestine I div > ol > li > a
St. Sixtus III div > ol > li > a
St. Leo I (the Great) div > ol > li > a
St. Hilarius div > ol > li > a
St. Simplicius div > ol > li > a
St. Felix III (II) div > ol > li > a
St. Gelasius I div > ol > li > a
Anastasius II div > ol > li > a
St. Symmachus div > ol > li > a
St. Hormisdas div > ol > li > a
St. John I div > ol > li > a
St. Felix IV (III) div > ol > li > a
Boniface II div > ol > li > a
John II div > ol > li > a
St. Agapetus I div > ol > li > a
St. Silverius div > ol > li > a
Vigilius div > ol > li > a
Pelagius I div > ol > li > a
John III div > ol > li > a
Benedict I div > ol > li > a
Pelagius II div > ol > li > a
St. Gregory I (the Great) div > ol > li > a
Sabinian div > ol > li > a
Boniface III div > ol > li > a
St. Boniface IV div > ol > li > a
St. Deusdedit (Adeodatus I) div > ol > li > a
Boniface V div > ol > li > a
Honorius I div > ol > li > a
Severinus div > ol > li > a
John IV div > ol > li > a
Theodore I div > ol > li > a
St. Martin I div > ol > li > a
St. Eugene I div > ol > li > a
St. Vitalian div > ol > li > a
Adeodatus (II) div > ol > li > a
Donus div > ol > li > a
St. Agatho div > ol > li > a
St. Leo II div > ol > li > a
St. Benedict II div > ol > li > a
John V div > ol > li > a
Conon div > ol > li > a
St. Sergius I div > ol > li > a
John VI div > ol > li > a
John VII div > ol > li > a
Sisinnius div > ol > li > a
Constantine div > ol > li > a
St. Gregory II div > ol > li > a
St. Gregory III div > ol > li > a
St. Zachary div > ol > li > a
Stephen II (III) div > ol > li > a
St. Paul I div > ol > li > a
Stephen III (IV) div > ol > li > a
Adrian I div > ol > li > a
St. Leo III div > ol > li > a
Stephen IV (V) div > ol > li > a
St. Paschal I div > ol > li > a
Eugene II div > ol > li > a
Valentine div > ol > li > a
Gregory IV div > ol > li > a
Sergius II div > ol > li > a
St. Leo IV div > ol > li > a
Benedict III div > ol > li > a
St. Nicholas I (the Great) div > ol > li > a
Adrian II div > ol > li > a
John VIII div > ol > li > a
Marinus I div > ol > li > a
St. Adrian III div > ol > li > a
Stephen V (VI) div > ol > li > a
Formosus div > ol > li > a
Boniface VI div > ol > li > a
Stephen VI (VII) div > ol > li > a
Romanus div > ol > li > a
Theodore II div > ol > li > a
John IX div > ol > li > a
Benedict IV div > ol > li > a
Leo V div > ol > li > a
Sergius III div > ol > li > a
Anastasius III div > ol > li > a
Lando div > ol > li > a
John X div > ol > li > a
Leo VI div > ol > li > a
Stephen VIII div > ol > li > a
John XI div > ol > li > a
Leo VII div > ol > li > a
Stephen IX div > ol > li > a
Marinus II div > ol > li > a
Agapetus II div > ol > li > a
John XII div > ol > li > a
Leo VIII div > ol > li > a
Benedict V div > ol > li > a
John XIII div > ol > li > a
Benedict VI div > ol > li > a
Benedict VII div > ol > li > a
John XIV div > ol > li > a
John XV div > ol > li > a
Gregory V div > ol > li > a
Sylvester II div > ol > li > a
John XVII div > ol > li > a
John XVIII div > ol > li > a
Sergius IV div > ol > li > a
Benedict VIII div > ol > li > a
John XIX div > ol > li > a
Benedict IX div > ol > li > a
Benedict IX div > ol > li > a
Gregory VI div > ol > li > a
Clement II div > ol > li > a
Benedict IX div > ol > li > a
Damasus II div > ol > li > a
St. Leo IX div > ol > li > a
Victor II div > ol > li > a
Stephen X div > ol > li > a
Nicholas II div > ol > li > a
Alexander II div > ol > li > a
St. Gregory VII div > ol > li > a
Blessed Victor III div > ol > li > a
Blessed Urban II div > ol > li > a
Paschal II div > ol > li > a
Gelasius II div > ol > li > a
Callistus II div > ol > li > a
Honorius II div > ol > li > a
Innocent II div > ol > li > a
Celestine II div > ol > li > a
Lucius II div > ol > li > a
Blessed Eugene III div > ol > li > a
Anastasius IV div > ol > li > a
Adrian IV div > ol > li > a
Alexander III div > ol > li > a
Lucius III div > ol > li > a
Urban III div > ol > li > a
Gregory VIII div > ol > li > a
Clement III div > ol > li > a
Celestine III div > ol > li > a
Innocent III div > ol > li > a
Honorius III div > ol > li > a
Gregory IX div > ol > li > a
Celestine IV div > ol > li > a
Innocent IV div > ol > li > a
Alexander IV div > ol > li > a
Urban IV div > ol > li > a
Clement IV div > ol > li > a
Blessed Gregory X div > ol > li > a
Blessed Innocent V div > ol > li > a
Adrian V div > ol > li > a
John XXI div > ol > li > a
Nicholas III div > ol > li > a
Martin IV div > ol > li > a
Honorius IV div > ol > li > a
Nicholas IV div > ol > li > a
St. Celestine V div > ol > li > a
Boniface VIII div > ol > li > a
Blessed Benedict XI div > ol > li > a
Clement V div > ol > li > a
John XXII div > ol > li > a
Benedict XII div > ol > li > a
Clement VI div > ol > li > a
Innocent VI div > ol > li > a
Blessed Urban V div > ol > li > a
Gregory XI div > ol > li > a
Urban VI div > ol > li > a
Boniface IX div > ol > li > a
Innocent VII div > ol > li > a
Gregory XII div > ol > li > a
Martin V div > ol > li > a
Eugene IV div > ol > li > a
Nicholas V div > ol > li > a
Callistus III div > ol > li > a
Pius II div > ol > li > a
Paul II div > ol > li > a
Sixtus IV div > ol > li > a
Innocent VIII div > ol > li > a
Alexander VI div > ol > li > a
Pius III div > ol > li > a
Julius II div > ol > li > a
Leo X div > ol > li > a
Adrian VI div > ol > li > a
Clement VII div > ol > li > a
Paul III div > ol > li > a
Julius III div > ol > li > a
Marcellus II div > ol > li > a
Paul IV div > ol > li > a
Pius IV div > ol > li > a
St. Pius V div > ol > li > a
Gregory XIII div > ol > li > a
Sixtus V div > ol > li > a
Urban VII div > ol > li > a
Gregory XIV div > ol > li > a
Innocent IX div > ol > li > a
Clement VIII div > ol > li > a
Leo XI div > ol > li > a
Paul V div > ol > li > a
Gregory XV div > ol > li > a
Urban VIII div > ol > li > a
Innocent X div > ol > li > a
Alexander VII div > ol > li > a
Clement IX div > ol > li > a
Clement X div > ol > li > a
Blessed Innocent XI div > ol > li > a
Alexander VIII div > ol > li > a
Innocent XII div > ol > li > a
Clement XI div > ol > li > a
Innocent XIII div > ol > li > a
Benedict XIII div > ol > li > a
Clement XII div > ol > li > a
Benedict XIV div > ol > li > a
Clement XIII div > ol > li > a
Clement XIV div > ol > li > a
Pius VI div > ol > li > a
Pius VII div > ol > li > a
Leo XII div > ol > li > a
Pius VIII div > ol > li > a
Gregory XVI div > ol > li > a
Blessed Pius IX div > ol > li > a
Leo XIII div > ol > li > a
St. Pius X div > ol > li > a
Benedict XV (1914-22) div > ol > li > a
Pius XI (1922-39) div > ol > li > a
Pius XII (1939-58) div > ol > li > a
St. John XXIII (1958-63) div > ol > li > a
St. Paul VI (1963-78) div > ol > li > a
John Paul I (1978) div > ol > li > a
St. John Paul II (1978-2005) div > ol > li > a
Benedict XVI (2005-2013) div > ol > li > a
Francis (2013-2025) div > ol > li > a
Leo XIV div > ol > li > a

These are opportunities to improve the legibility of your content.

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.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div.homecenter > p > a > img div.homecenter > p > a > img
div#canmobileanchoradclick > div#CANclsbtnb > a > img div#canmobileanchoradclick > div#CANclsbtnb > a > img

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#home-728x90-top > div > ins#INS30849120180430T122717150415836098F5944F3AB43B31EC3967310_FWWKR1776895681255 > iframe#INS30849120180430T122717150415836098F5944F3AB43B31EC3967310_FWWKR1776895681255_mainframe div#home-728x90-top > div > ins#INS30849120180430T122717150415836098F5944F3AB43B31EC3967310_FWWKR1776895681255 > iframe#INS30849120180430T122717150415836098F5944F3AB43B31EC3967310_FWWKR1776895681255_mainframe
div#home-300x250-sidebar > div > ins#INS30849120180430T122551060AFDB07655D8342D99D8AF7676C0EACF4_tuLwA1776895681264 > iframe#INS30849120180430T122551060AFDB07655D8342D99D8AF7676C0EACF4_tuLwA1776895681264_mainframe div#home-300x250-sidebar > div > ins#INS30849120180430T122551060AFDB07655D8342D99D8AF7676C0EACF4_tuLwA1776895681264 > iframe#INS30849120180430T122551060AFDB07655D8342D99D8AF7676C0EACF4_tuLwA1776895681264_mainframe
div > ins > ins#INS30849120240110T154429220EAEFD5C5425149CE8AAB5D91A65864CF_BvXkw1776895681276 > iframe#INS30849120240110T154429220EAEFD5C5425149CE8AAB5D91A65864CF_BvXkw1776895681276_mainframe div > ins > ins#INS30849120240110T154429220EAEFD5C5425149CE8AAB5D91A65864CF_BvXkw1776895681276 > iframe#INS30849120240110T154429220EAEFD5C5425149CE8AAB5D91A65864CF_BvXkw1776895681276_mainframe

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#article > div.homecenter > p > a div#article > div.homecenter > p > a
body.home > div#canmobileanchoradclick > div#CANclsbtnb > a body.home > div#canmobileanchoradclick > div#CANclsbtnb > 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
A body.home > div#capitalcity > nav#alpha-bar > a
B body.home > div#capitalcity > nav#alpha-bar > a
C body.home > div#capitalcity > nav#alpha-bar > a
D body.home > div#capitalcity > nav#alpha-bar > a
E body.home > div#capitalcity > nav#alpha-bar > a
F body.home > div#capitalcity > nav#alpha-bar > a
G body.home > div#capitalcity > nav#alpha-bar > a
H body.home > div#capitalcity > nav#alpha-bar > a
I body.home > div#capitalcity > nav#alpha-bar > a
J body.home > div#capitalcity > nav#alpha-bar > a
K body.home > div#capitalcity > nav#alpha-bar > a
L body.home > div#capitalcity > nav#alpha-bar > a
M body.home > div#capitalcity > nav#alpha-bar > a
N body.home > div#capitalcity > nav#alpha-bar > a
O body.home > div#capitalcity > nav#alpha-bar > a
P body.home > div#capitalcity > nav#alpha-bar > a
Q body.home > div#capitalcity > nav#alpha-bar > a
R body.home > div#capitalcity > nav#alpha-bar > a
S body.home > div#capitalcity > nav#alpha-bar > a
T body.home > div#capitalcity > nav#alpha-bar > a
U body.home > div#capitalcity > nav#alpha-bar > a
V body.home > div#capitalcity > nav#alpha-bar > a
W body.home > div#capitalcity > nav#alpha-bar > a
X body.home > div#capitalcity > nav#alpha-bar > a
Y body.home > div#capitalcity > nav#alpha-bar > a
Z body.home > div#capitalcity > nav#alpha-bar > 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.
Form elements have associated labels
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
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.
The page contains a heading, skip link, or landmark region
`[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-hidden="true"]` elements do not contain focusable descendents
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
`<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
Heading elements appear in a sequentially-descending order
`<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">`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
`<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.
Identical links have the same purpose.
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.
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
Topics
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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

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.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div.homecontainer > div.homeleft > p > img div.homecontainer > div.homeleft > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div#article > div.homecenter > p > img div#article > div.homecenter > p > img
div.homecenter > p > a > img div.homecenter > p > a > img
div#canmobileanchoradclick > div#CANclsbtnb > a > img div#canmobileanchoradclick > div#CANclsbtnb > a > 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
Document has a meta description
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