C — https://whyy.org | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

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

Good foundation, but a few gaps could be exploited.

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

Amazon Webstore · 41 peers

You 75

Avg 71

At average

0 50 100

Better than 92% of Amazon Webstore sites See full Amazon Webstore benchmark →

WordPress · 712 peers

You 75

Avg 74

At average

0 50 100

Better than 55% of WordPress sites See full WordPress benchmark →

Top Priorities (5)

'unsafe-eval' found in script source

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

Security › Content Security Policy

'unsafe-inline' found in script source

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

Security › Content Security Policy

Page weighs 11.4 MB (4.1 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

1 control(s) without accessible label

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

Accessibility › Form Accessibility

4 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

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwhyy.org)](https://beavercheck.com/results/cc64833d-20c1-4ba0-ae89-c7599071dc74)

HTML

<a href="https://beavercheck.com/results/cc64833d-20c1-4ba0-ae89-c7599071dc74"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwhyy.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwhyy.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. Your LCP of 10.3s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

Your LCP is 10.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

2 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

4 critical 3 warning

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

Speed (2)

Page takes 10.3s to load

+12% bounce

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

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

Page feels frozen for 4.0s

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

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

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)

4 broken link(s) on the page

+5% bounce

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

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

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

Return on Investment

$600 investment → $5,176/month returns + USD 157,500 risk avoided

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

Investment

$600

6h · 5 findings

Monthly returns

$5,176 /mo

~$62,118 / year

Conversions recovered $5,175
Bandwidth savings $1.04

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

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

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

Full methodology & sources

Estimated Remediation Cost

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /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,512 / 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
7 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

+9 more

Bandwidth Waste

$1.04 /mo

12945.5 MB/mo × 0.080 USD/GB

Optimize transfer: save ~1.3 MB per page load
Saves $1.04/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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

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

10.30 s

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

3.97 s

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

0.001

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

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

30.84 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
/signals/config/190187641351038?v=2.9.303&r=stable&domain...	1200.0 s	46.7 KiB
/signals/config/427623827650544?v=2.9.303&r=stable&domain...	1200.0 s	44.7 KiB
ads.pubmatic.com/AdServer/js/pwt/157577/2378//pwt.js	147654.0 s	76.4 KiB
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	604800.0 s	216.4 KiB
powerad.ai/208202543264025/script.js	86400.0 s	52.1 KiB
www.redditstatic.com/ads/pixel.js	60.0 s	19.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
/signals/config/220003995782109?v=2.9.303&r=stable&domain...	1200.0 s	16.4 KiB
tagan.adlightning.com/nextmillenium-whyy/op.js	1800.0 s	15.7 KiB
js.adsrvr.org/up_loader.3.0.0.js	0.0 ms	12.3 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	16.1 KiB
c.amazon-adsystem.com/aat/amzn.js	0.0 ms	8.9 KiB
tags.srv.stackadapt.com/events.js	5.0 s	7.7 KiB
static.hotjar.com/c/hotjar-1372354.js?sv=7	60.0 s	6.3 KiB
cse.google.com/cse.js?cx=018124873157799521143:5jp04c3pl9s	0.0 ms	3.1 KiB
pixel.zprk.io/v5/pixeljs/Hc6PdfQeAi.js?dne=1	0.0 ms	3.0 KiB
hb.brainlyads.com/pbjs_wrapper.v3.0.js	604800.0 s	18.3 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	959 B
/rp.gif?ts=1776901442855&id=a2_hqbkzjx0ywfv&event=PageVis...	0.0 ms	666 B
p.cpx.to/p/12967/px.js	2419200.0 s	3.7 KiB
/mw?zpartnerid=1353&env=mWeb&env=mWeb&eventType=map&id_mi...	0.0 ms	245 B
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.6 KiB
/p.css?s=1&k=izx6wme&ht=tk&f=13378.13379.13380.17007.1701...	604800.0 s	172 B
/tr/?id=190187641351038&ev=PageView&dl=https%3A%2F%2Fwhyy...	0.0 ms	16 B
/tr/?id=220003995782109&ev=PageView&dl=https%3A%2F%2Fwhyy...	0.0 ms	16 B
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: An aerial view of Seaside Park, New Jersey

path: 1,HTML,1,BODY,3,DIV,3,DIV,2,MAIN,0,ARTICLE,1,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,ARTICLE,0,DIV,0,A,1,IMG

selector: article.content-mode > div.col-img > a > img.b-lazy

snippet: <img class="b-lazy b-loaded" src="https://whyy.org/wp-content/uploads/2025/07/07-23-2025-k-paynter-south-sea…" alt="An aerial view of Seaside Park, New Jersey" width="750" height="560">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	38.1 KiB	302 ms
whyy.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	35.0 KiB	151 ms
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	2.3 KiB
whyy.org/wp-includes/css/dist/block-library/style.min.css?ver=6.9.1	20.2 KiB	151 ms
whyy.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.6 KiB
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	605 B
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	933 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
whyy.org/wp-content/themes/whyy/fonts/whyy-icons-0218/whyy-icons-0218.woff	20 ms
/af/708bdf/00000000000000003b9acf2e/27/l?primer=7cdcb44be...	20 ms
/af/9ff5df/0000000000000000000131a3/27/l?primer=7cdcb44be...	20 ms
whyy.org/wp-content/themes/whyy/fonts/whyy-icons-v2/icofont.woff	15 ms
/af/9f2f2a/00000000000000003b9acf30/27/l?primer=7cdcb44be...	15 ms
/af/03e1a3/00000000000000003b9acf2d/27/l?primer=7cdcb44be...	15 ms
whyy.org/wp-content/themes/whyy/fonts/whyy-icons/whyy-icons.woff	10 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.

	URL	Resource Size	Est Savings
body > div#google_image_div > a#aw0 > img.img_ad `body > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/10699266238952150655	174.7 KiB	90.9 KiB
An aerial view of Seaside Park, New Jersey `article.content-mode > div.col-img > a > img.b-lazy`	/wp-content/uploads/2025/07/07-23-2025-k-paynter-south-se...	111.8 KiB	61.8 KiB
body > div#google_image_div > a#aw0 > img.img_ad `body > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/17166060665455431863	42.7 KiB	30.5 KiB
Reading Terminal Market was named Best Public Market in America `article.content-mode > div.col-img > a > img.b-lazy`	/wp-content/uploads/2026/04/04-22-2026-k-paynter-reading-...	27.8 KiB	11.4 KiB
WHYY Passport `div.bottom > div.l-container--md > span.f--title > img.alignleft`	/wp-content/uploads/2023/10/WHYY_Passport-Lockup_Horizont...	7.5 KiB	5.5 KiB

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

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: 440 ms 60.8 KiB

URL	Transfer Size	Est Savings
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	37.9 KiB	29.0 KiB
whyy.org/wp-includes/css/dist/block-library/style.min.css?ver=6.9.1	20.0 KiB	19.8 KiB
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	11.9 KiB	11.9 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

Estimated savings: 1.4 s 1.2 MiB

URL	Transfer Size	Est Savings
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	216.2 KiB	177.5 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	156.7 KiB	109.8 KiB
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	187.7 KiB	102.5 KiB
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	102.7 KiB	70.7 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y	156.7 KiB	66.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	170.8 KiB	64.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1	133.7 KiB	62.6 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	146.5 KiB	62.4 KiB
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	151.7 KiB	62.0 KiB
www.googletagmanager.com/gtag/destination?id=DC-8531012&cx=c&gtm=4e64k1	129.1 KiB	61.8 KiB
ads.pubmatic.com/AdServer/js/pwt/157577/2378//pwt.js	76.1 KiB	55.9 KiB
s2.getsitecontrol.com/widgets/es6/runtime.8f6e318.js	67.6 KiB	49.9 KiB
powerad.ai/208202543264025/script.js	51.8 KiB	38.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.1 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	25.2 KiB
securepubads.g.doubleclick.net/tag/js/gpt.js	33.6 KiB	24.0 KiB
securepubads.g.doubleclick.net/tag/js/gpt.js	33.6 KiB	24.0 KiB
tagan.adlightning.com/nextmillenium-whyy/b-2d8eee8-44fede03.js	31.1 KiB	21.5 KiB
whyy.org/wp-content/themes/whyy/js/vendor/plugins.min.js?ver=1.0	42.0 KiB	21.2 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.4 s	262 ms	0.0 ms
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	1.3 s	1.0 s	139 ms
whyy.org/	1.2 s	55 ms	24 ms
/pagead/managed/js/activeview/current/ufs_web_display.js	881 ms	758 ms	90 ms
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	554 ms	448 ms	72 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	553 ms	499 ms	28 ms
whyy.org/wp-content/themes/whyy/js/vendor/plugins.min.js?ver=1.0	495 ms	198 ms	17 ms
whyy.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	464 ms	210 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y	388 ms	323 ms	63 ms
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	343 ms	263 ms	78 ms
www.redditstatic.com/ads/pixel.js	336 ms	311 ms	7.9 ms
cdn.parsely.com/keys/whyy.org/p.js?ver=3.22.0	314 ms	280 ms	7.5 ms
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	307 ms	249 ms	56 ms
tagan.adlightning.com/nextmillenium-whyy/b-2d8eee8-44fede03.js	302 ms	292 ms	10 ms
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	299 ms	245 ms	50 ms
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1	284 ms	179 ms	54 ms
www.googletagmanager.com/gtag/destination?id=DC-8531012&cx=c&gtm=4e64k1	256 ms	208 ms	45 ms
tagan.adlightning.com/nextmillenium-whyy/bl-0d6ee0c-e6b4f856.js	245 ms	196 ms	47 ms
powerad.ai/208202543264025/script.js	234 ms	175 ms	30 ms
connect.facebook.net/en_US/fbevents.js	179 ms	134 ms	44 ms
/signals/config/190187641351038?v=2.9.303&r=stable&domain...	177 ms	150 ms	25 ms
tagan.adlightning.com/nextmillenium-whyy/op.js	165 ms	159 ms	4.7 ms
s2.getsitecontrol.com/widgets/es6/runtime.8f6e318.js	148 ms	116 ms	26 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	142 ms	83 ms	57 ms
js-agent.newrelic.com/nr-rum-1.313.1.min.js	140 ms	117 ms	8.7 ms
static.chartbeat.com/js/chartbeat.js	134 ms	127 ms	5.2 ms
ep2.adtrafficquality.google/sodar/sodar2.js	106 ms	100 ms	2.7 ms
ads.pubmatic.com/AdServer/js/pwt/157577/2378//pwt.js	99 ms	67 ms	31 ms
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	89 ms	32 ms	57 ms
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	86 ms	33 ms	51 ms
www.google-analytics.com/analytics.js	75 ms	63 ms	6.9 ms
js.adsrvr.org/up_loader.3.0.0.js	68 ms	51 ms	8.1 ms
static.ads-twitter.com/uwt.js	65 ms	58 ms	5.9 ms
/wp-content/uploads/cache/autoptimize/js/autoptimize_sing...	64 ms	52 ms	2.7 ms
/signals/config/220003995782109?v=2.9.303&r=stable&domain...	63 ms	51 ms	10 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	7.8 s
Other	1.7 s
Script Parsing & Compilation	1.2 s
Style & Layout	965 ms
Rendering	247 ms
Garbage Collection	226 ms
Parse HTML & CSS	203 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 reason	Failure type
The page has an unload handler in a sub frame.	Actionable
The page did not finish loading before navigating away.	Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.3 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	12.0 KiB	3.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
whyy.org/wp-content/uploads/2024/01/ACGS.jpg	317.5 KiB
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	216.4 KiB
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	187.7 KiB
tpc.googlesyndication.com/simgad/10699266238952150655	175.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	171.2 KiB
tagan.adlightning.com/nextmillenium-whyy/bl-0d6ee0c-e6b4f856.js	158.3 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	156.7 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y	156.7 KiB
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	151.7 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	146.5 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 24 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 80 ms

●Server Backend Latencies 390 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 20 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Primary Menu `div.header--bottom > div.l-container--lg > div.site-nav--top > div.menu-toggle`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SPONSOR `div.jp-title-container > div.jp-title-right > div.jp-sponsor-container > h4.sponsored-tag`
SPONSORED `article.content-mode > div.col-item > div.col-text > h4.sponsored-tag`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Social Responsibility at WHYY `div.col-flex--1 > div.site-intro > p > a`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reported crime on SEPTA continues to drop in 2026 after decade lows last year `article.content-mode > div.col-item > div.col-text > h4.f--title`
Listen now `div.col-text > div.u-faux-table > div.align--bottom > h4`
Subscribe `div.col-text > div.u-faux-table > div.align--bottom > h4`
Contact Us `div.flex-grid > div.col-flex--1 > div.site-contacts > h4.f--label`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > img `body.home > img`

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.l-container--lg > div.jp-gui > div.jp-interface > a.btn `div.l-container--lg > div.jp-gui > div.jp-interface > a.btn`

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
SCIENCE `article.content-mode > div.col-text > div.f--taxonomy > a`
STUDIO 2 `div.align--bottom > div.categories > div.f--taxonomy > a`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Input buttons have discernible text.

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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.

	URL	Displayed size	Actual size	Expected size
An NJ Transit train leaves the Secaucus Junction station `article.content-mode > div.col-img > a > img`	whyy.org/wp-content/uploads/2025/05/NJ-Transit-train-2025-05-14-ap-1-360x280.jpg	367 x 285	360 x 280	551 x 428

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 / Warning	Source
SharedStorage	/pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234
AttributionReporting	c.amazon-adsystem.com/aat/amzn.js line 1, col 8822

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
whyy.org/	`Attestation check for Shared Storage on https://ara.paa-reporting-advertising.amazon failed.`
script.hotjar.com/modules.6a0f3932cb1341a35c18.js line 3, col 129935	`Connecting to 'wss://ws.hotjar.com/api/v2/client/ws?v=7&site_id=1372354' violates the following Content Security Policy directive: "default-src data: 'unsafe-inline' 'unsafe-eval' https:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.`
whyy.org/wp-includes/js/wp-emoji-loader.min.js line 3, col 2289	`Creating a worker from 'blob:https://whyy.org/8b3c8a5d-d389-4a21-a723-cb3ca5487262' violates the following Content Security Policy directive: "default-src data: 'unsafe-inline' 'unsafe-eval' https:". Note that 'worker-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.`
whyy.org/wp-content/themes/whyy/images/icons/y@2x.png	`Failed to load resource: the server responded with a status of 404 ()`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
10	`Allow: .js`	`Pattern should either be empty, start with "/" or "*"`
11	`Allow: .css`	`Pattern should either be empty, start with "/" or "*"`

To appear in search results, crawlers need access to your app.

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
body.home > img `body.home > 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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

680 ms

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

2.24 s

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

584 ms

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

0.004

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

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

7.15 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

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 ▾

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.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
/signals/config/190187641351038?v=2.9.303&r=stable&domain...	1200.0 s	46.7 KiB
/signals/config/427623827650544?v=2.9.303&r=stable&domain...	1200.0 s	44.7 KiB
ads.pubmatic.com/AdServer/js/pwt/157577/2378//pwt.js	147628.0 s	76.4 KiB
/ML/6517cf13d50f5b645bd1e60bb4250742__scv1__622x368.webp	3600.0 s	30.6 KiB
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	604800.0 s	216.4 KiB
powerad.ai/208202543264025/script.js	86400.0 s	52.1 KiB
www.redditstatic.com/ads/pixel.js	60.0 s	19.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
/signals/config/220003995782109?v=2.9.303&r=stable&domain...	1200.0 s	16.4 KiB
tagan.adlightning.com/nextmillenium-whyy/op.js	1800.0 s	15.7 KiB
js.adsrvr.org/up_loader.3.0.0.js	0.0 ms	12.3 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	16.1 KiB
c.amazon-adsystem.com/aat/amzn.js	0.0 ms	8.9 KiB
tags.srv.stackadapt.com/events.js	5.0 s	7.7 KiB
static.hotjar.com/c/hotjar-1372354.js?sv=7	60.0 s	6.3 KiB
cse.google.com/cse.js?cx=018124873157799521143:5jp04c3pl9s	0.0 ms	3.4 KiB
pixel.zprk.io/v5/pixeljs/Hc6PdfQeAi.js?dne=1	0.0 ms	3.0 KiB
hb.brainlyads.com/pbjs_wrapper.v3.0.js	604800.0 s	18.3 KiB
static.mediagotechnology.com/js/mediagotechnology/style/style_banner_a02e55.css	3600.0 s	1.8 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	958 B
/ju/cs/eplist?tn=c910685a5d6ad3a65ba316b604c54d47&gdpr_co...	0.0 ms	878 B
/rp.gif?ts=1776901468425&id=a2_hqbkzjx0ywfv&event=PageVis...	0.0 ms	666 B
hb.brainlyads.com/hb-ad-unit-script.js	604800.0 s	4.7 KiB
p.cpx.to/p/12967/px.js	2419200.0 s	3.7 KiB
/mw?zpartnerid=1353&env=mWeb&env=mWeb&eventType=map&id_mi...	0.0 ms	245 B
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.6 KiB
/ju/log/c?tn=41b6e88a2b85b0e731ef8e73e5558712&app=Google_...	0.0 ms	122 B
/p.css?s=1&k=izx6wme&ht=tk&f=13378.13379.13380.17007.1701...	604800.0 s	173 B
/tr/?id=190187641351038&ev=PageView&dl=https%3A%2F%2Fwhyy...	0.0 ms	16 B
/tr/?id=220003995782109&ev=PageView&dl=https%3A%2F%2Fwhyy...	0.0 ms	16 B
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: An aerial view of Seaside Park, New Jersey

path: 1,HTML,1,BODY,3,DIV,3,DIV,2,MAIN,0,ARTICLE,1,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,ARTICLE,0,DIV,0,A,1,IMG

selector: article.content-mode > div.col-img > a > img.b-lazy

snippet: <img class="b-lazy b-loaded" src="https://whyy.org/wp-content/uploads/2025/07/07-23-2025-k-paynter-south-sea…" alt="An aerial view of Seaside Park, New Jersey" width="750" height="560">

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.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
whyy.org/wp-content/themes/whyy/fonts/whyy-icons/whyy-icons.woff	15 ms
whyy.org/wp-content/themes/whyy/fonts/whyy-icons-0218/whyy-icons-0218.woff	10 ms
whyy.org/wp-content/themes/whyy/fonts/whyy-icons-v2/icofont.woff	10 ms
/af/9f2f2a/00000000000000003b9acf30/27/l?primer=7cdcb44be...	5.0 ms
/af/03e1a3/00000000000000003b9acf2d/27/l?primer=7cdcb44be...	5.0 ms
/af/708bdf/00000000000000003b9acf2e/27/l?primer=7cdcb44be...	5.0 ms
/af/9ff5df/0000000000000000000131a3/27/l?primer=7cdcb44be...	5.0 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.

	URL	Resource Size	Est Savings
Watch or Stream The Forsytes on Masterpiece. Sundays at 9 p.m. on WHYY-TV 12 or… `body > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/3097537109045086265	262.2 KiB	149.5 KiB
An aerial view of Seaside Park, New Jersey `article.content-mode > div.col-img > a > img.b-lazy`	/wp-content/uploads/2025/07/07-23-2025-k-paynter-south-se...	111.8 KiB	89.0 KiB
Most People Don't Use This Tip for Mice in Spring, But it Works Like Magic `body > div#mgcontainer-93c94222586370943d1fd43bfb5f53d5a > a.mediagotechnology-placement-track_a02e55 > img`	/ML/6517cf13d50f5b645bd1e60bb4250742__scv1__622x368.webp	30.1 KiB	23.2 KiB
Reading Terminal Market was named Best Public Market in America `article.content-mode > div.col-img > a > img.b-lazy`	/wp-content/uploads/2026/04/04-22-2026-k-paynter-reading-...	27.8 KiB	16.2 KiB
WHYY Passport `div.bottom > div.l-container--md > span.f--title > img.alignleft`	/wp-content/uploads/2023/10/WHYY_Passport-Lockup_Horizont...	7.5 KiB	5.5 KiB

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.

URL	Transfer Size	Duration
whyy.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	34.9 KiB	82 ms
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	38.2 KiB	82 ms
whyy.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.5 KiB
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	2.2 KiB
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	905 B
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	578 B
whyy.org/wp-includes/css/dist/block-library/style.min.css?ver=6.9.1	20.2 KiB	82 ms

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

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.

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: 60 ms 58.2 KiB

URL	Transfer Size	Est Savings
/wp-content/uploads/cache/autoptimize/css/autoptimize_sin...	37.9 KiB	26.5 KiB
whyy.org/wp-includes/css/dist/block-library/style.min.css?ver=6.9.1	20.0 KiB	19.8 KiB
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	11.9 KiB	11.9 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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 240 ms 1.2 MiB

URL	Transfer Size	Est Savings
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	216.2 KiB	142.0 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y	156.7 KiB	109.5 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB	99.8 KiB
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	102.7 KiB	70.7 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	156.7 KiB	66.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	170.8 KiB	64.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1	133.7 KiB	62.6 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	146.5 KiB	62.4 KiB
www.googletagmanager.com/gtag/destination?id=DC-8531012&cx=c&gtm=4e64k1	129.1 KiB	61.7 KiB
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	151.7 KiB	61.4 KiB
ads.pubmatic.com/AdServer/js/pwt/157577/2378//pwt.js	76.1 KiB	54.8 KiB
s2.getsitecontrol.com/widgets/es6/runtime.8f6e318.js	67.6 KiB	49.9 KiB
powerad.ai/208202543264025/script.js	51.8 KiB	49.4 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.6 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	30.3 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	30.3 KiB
powerad.ai/208202543264025/script.js	51.8 KiB	26.6 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	25.3 KiB
securepubads.g.doubleclick.net/tag/js/gpt.js	33.6 KiB	24.0 KiB
securepubads.g.doubleclick.net/tag/js/gpt.js	33.6 KiB	24.0 KiB
whyy.org/wp-content/themes/whyy/js/vendor/plugins.min.js?ver=1.0	42.0 KiB	21.3 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
powerad.ai/208202543264025/script.js	677 ms	539 ms	49 ms
Unattributable	372 ms	94 ms	0.0 ms
whyy.org/	362 ms	47 ms	8.3 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	355 ms	289 ms	32 ms
/pagead/managed/js/activeview/current/ufs_web_display.js	287 ms	235 ms	23 ms
whyy.org/wp-content/themes/whyy/js/vendor/plugins.min.js?ver=1.0	162 ms	63 ms	4.4 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	162 ms	133 ms	6.9 ms
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	139 ms	116 ms	18 ms
tagan.adlightning.com/nextmillenium-whyy/b-2d8eee8-44fede03.js	119 ms	89 ms	3.1 ms
whyy.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	116 ms	55 ms	2.6 ms
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	111 ms	83 ms	27 ms
www.redditstatic.com/ads/pixel.js	106 ms	97 ms	2.1 ms
cdn.parsely.com/keys/whyy.org/p.js?ver=3.22.0	99 ms	86 ms	5.0 ms
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	81 ms	67 ms	14 ms
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	79 ms	60 ms	19 ms
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	68 ms	55 ms	13 ms
www.googletagmanager.com/gtag/destination?id=DC-8531012&cx=c&gtm=4e64k1	63 ms	51 ms	11 ms
tagan.adlightning.com/nextmillenium-whyy/bl-0d6ee0c-e6b4f856.js	58 ms	47 ms	11 ms
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1	56 ms	43 ms	12 ms
hb.brainlyads.com/pbjs_wrapper.v3.0.js	56 ms	53 ms	2.2 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.8 s
Other	466 ms
Script Parsing & Compilation	372 ms
Style & Layout	297 ms
Garbage Collection	132 ms
Rendering	72 ms
Parse HTML & CSS	57 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 reason	Failure type
The page has an unload handler in a sub frame.	Actionable
An iframe on the page started a navigation that did not complete.	Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.3 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	12.0 KiB	3.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
whyy.org/wp-content/uploads/2024/01/ACGS.jpg	317.5 KiB
tpc.googlesyndication.com/simgad/3097537109045086265	262.7 KiB
//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c...	216.4 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-KBG3KRK	171.2 KiB
tagan.adlightning.com/nextmillenium-whyy/bl-0d6ee0c-e6b4f856.js	158.3 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y	156.7 KiB
www.googletagmanager.com/gtag/js?id=G-CLMZMJED4Y&cx=c&gtm=4e64k1	156.7 KiB
www.googletagmanager.com/gtag/js?id=G-KYFZS88C51&cx=c&_slc=1	151.7 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1	146.5 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 29 user timings

●Avoid long main-thread tasks 14 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 80 ms

●Server Backend Latencies 840 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 10 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

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
SPONSOR `div.jp-title-container > div.jp-title-right > div.jp-sponsor-container > h4.sponsored-tag`
Report Ad `div#div-gpt-ad-1501272111871-1 > div#pa-container-1 > div#pa-unit-1 > a.pa-report-ad-btn`
SPONSORED `article.content-mode > div.col-item > div.col-text > h4.sponsored-tag`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Social Responsibility at WHYY `div.col-flex--1 > div.site-intro > p > 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
body.home > img `body.home > 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#div-gpt-ad-1501272111871-1 > div#pa-container-1 > div#pa-unit-1 > iframe.pa_frame `div#div-gpt-ad-1501272111871-1 > div#pa-container-1 > div#pa-unit-1 > iframe.pa_frame`

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.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reported crime on SEPTA continues to drop in 2026 after decade lows last year `article.content-mode > div.col-item > div.col-text > h4.f--title`
Listen now `div.col-text > div.u-faux-table > div.align--bottom > h4`
Subscribe `div.col-text > div.u-faux-table > div.align--bottom > h4`
Contact Us `div.flex-grid > div.col-flex--1 > div.site-contacts > h4.f--label`

These are opportunities to improve keyboard navigation in your application.

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
WORLD CUP 2026 `div.col-text > div.f--taxonomy > span > a`
MONEY `article.content-mode > div.col-text > div.f--taxonomy > a`
BILLY PENN `div.col-text > div.f--taxonomy > span > a`
COMMUNITY `article.content-mode > div.col-text > div.f--taxonomy > a`
SCIENCE `article.content-mode > div.col-text > div.f--taxonomy > a`

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

●Input buttons have discernible text.

●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 have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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 / Warning	Source
SharedStorage	/pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234
AttributionReporting	c.amazon-adsystem.com/aat/amzn.js line 1, col 8822
Topics	//pbjs/2321/prebid.js?hash=9.30.0/4287587f1206c68c2ed578c... line 88, col 34455
Unload event listeners are deprecated and will be removed.	line 8, col 42

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
whyy.org/	`Attestation check for Shared Storage on https://ara.paa-reporting-advertising.amazon failed.`
script.hotjar.com/modules.6a0f3932cb1341a35c18.js line 3, col 129935	`Connecting to 'wss://ws.hotjar.com/api/v2/client/ws?v=7&site_id=1372354' violates the following Content Security Policy directive: "default-src data: 'unsafe-inline' 'unsafe-eval' https:". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.`
whyy.org/wp-includes/js/wp-emoji-loader.min.js line 3, col 2289	`Creating a worker from 'blob:https://whyy.org/aedea11f-828d-44da-a387-2a48fae8b1ac' violates the following Content Security Policy directive: "default-src data: 'unsafe-inline' 'unsafe-eval' https:". Note that 'worker-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.`
whyy.org/wp-content/themes/whyy/images/icons/y@2x.png	`Failed to load resource: the server responded with a status of 404 ()`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Report Ad `div#div-gpt-ad-1501272111871-1 > div#pa-container-1 > div#pa-unit-1 > a.pa-report-ad-btn`

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
10	`Allow: .js`	`Pattern should either be empty, start with "/" or "*"`
11	`Allow: .css`	`Pattern should either be empty, start with "/" or "*"`

To appear in search results, crawlers need access to your app.

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
body.home > img `body.home > 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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://whyy.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (3)

Usability (1)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Navigation

Names and labels

Best practices

Best Practices

User Experience

General

SEO

Crawling and Indexing

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Navigation

Best practices

Best Practices

General

SEO

Crawling and Indexing

Content Best Practices

Keyboard Shortcuts