Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Performance issues directly impact user engagement and conversion rates.

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
www.washingtonpost.com/zeus/main.js	3600.0 s	159.6 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.8 KiB
news.google.com/swg/js/v1/swg.js	3000.0 s	71.4 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	86400.0 s	128.5 KiB
g.3gl.net/jp/3543/v3.3.9/M	2634.0 s	34.5 KiB
www.washingtonpost.com/subscribe/static/tetro-client/fusion/tetro.min.js	600.0 s	25.9 KiB
pagead2.googlesyndication.com/pagead/js/rum.js	3600.0 s	25.1 KiB
/scripts/bundle/65568.js?sid=1ce8beea-3b4c-4621-93e6-7e1e...	3600.0 s	18.0 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otTCF.js	86400.0 s	17.7 KiB
www.washingtonpost.com/akam/13/22785e63	21600.0 s	9.5 KiB
s.go-mpulse.net/boomerang/2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF	604800.0 s	56.2 KiB
cdn.cookielaw.org/consent/a093b275-a057-4549-b897-a7cbac8afa1d/otSDKStub.js	86400.0 s	12.6 KiB
rumcdn.geoedge.be/09d3a988-6f0e-4f65-9970-88d250fb501d/grumi-ip.js	14400.0 s	7.4 KiB
www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js	600.0 s	5.0 KiB
news.google.com/swg/js/v1/swg-button.css	3000.0 s	5.2 KiB
static.chartbeat.com/js/chartbeat_mab.js	86400.0 s	10.1 KiB
cdn.brandmetrics.com/tag/c54a422f00744a569e47bf1f904b718e/washingtonpost.js	3600.0 s	3.1 KiB
config.aps.amazon-adsystem.com/configs/3041	3600.0 s	987 B
/c.js?siteid=1ce8beea-3b4c-4621-93e6-7e1ee915a33b&toploc=...	0.0 ms	271 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.washingtonpost.com/wp-stat/assets/fonts/ITC_Franklin-Bold.woff2	120 ms
www.washingtonpost.com/wp-stat/assets/fonts/ITC_Franklin-Light.woff2	60 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:36.636 source:map[column:138000 line:1 type:source-location url:https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:87.3 source:map[type:text value:[unattributed]]] map[reflowTime:0.042 source:map[column:44658 line:10 type:source-location url:https://securepubads.g.doubleclick.net/tag/js/gpt.js urlProvider:network]] map[reflowTime:35.415 source:map[column:7054 line:0 type:source-location url:https://www.washingtonpost.com/assembler/_next/static/chunks/1065.ff59e743b4104519.js urlProvider:network]] map[reflowTime:1.221 source:map[column:339630 line:176 type:source-location url:https://www.washingtonpost.com/assembler/_next/static/chunks/9301-fdb71a1a1c24410f.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:12125.269 label:Time to first byte subpart:timeToFirstByte] map[duration:13.001 label:Resource load delay subpart:resourceLoadDelay] map[duration:34.166 label:Resource load duration subpart:resourceLoadDuration] map[duration:174.463 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: figure.w-100 > div.dib > a.art-link > img.border-box

path: 6,MAIN,3,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,A,0,IMG

selector: figure.w-100 > div.dib > a.art-link > img.border-box

snippet: <img style="width:100%;height:100%" srcset="https://www.washingtonpost.com/wp-apps/imrs.php?src=https%3A%2F%2Farc-angl…" src="https://www.washingtonpost.com/wp-apps/imrs.php?src=https%3A%2F%2Farc-angl…" alt="" width="628" height="419" class="border-box db">

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: figure.w-100 > div.dib > a.art-link > img.border-box

path: 6,MAIN,3,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,A,0,IMG

selector: figure.w-100 > div.dib > a.art-link > img.border-box

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
figure.w-100 > div.dib > a.art-link > img.border-box `figure.w-100 > div.dib > a.art-link > img.border-box`	/wp-apps/imrs.php?src=https%3A%2F%2Farc-anglerfish-washpo...	52.6 KiB	25.9 KiB
figure.w-100 > div.dib > a.art-link > img.border-box `figure.w-100 > div.dib > a.art-link > img.border-box`	/wp-apps/imrs.php?src=https%3A%2F%2Farc-anglerfish-washpo...	31.3 KiB	4.6 KiB

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.

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

URL	Time Spent
washingtonpost.com/	351 ms
www.washingtonpost.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 240 ms 1.2 MiB

URL	Transfer Size	Est Savings
/assembler/_next/static/chunks/pages/_app-d0be26829892b38...	411.4 KiB	242.4 KiB
/assembler/_next/static/chunks/1c616b8c-1959175d299606b5.js	138.1 KiB	129.0 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	186.4 KiB	127.0 KiB
www.washingtonpost.com/assembler/_next/static/chunks/9301-fdb71a1a1c24410f.js	185.7 KiB	102.2 KiB
www.washingtonpost.com/zeus/main.js	158.8 KiB	95.6 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	128.2 KiB	72.9 KiB
/assembler/_next/static/chunks/fec483df-3ff4dbca1b9b2fa8.js	99.3 KiB	70.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHNNX8B	200.2 KiB	60.2 KiB
www.washingtonpost.com/assembler/_next/static/chunks/2721-1caac149cd4aa30d.js	88.3 KiB	48.0 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.4 KiB	37.2 KiB
news.google.com/swg/js/v1/swg.js	68.9 KiB	37.0 KiB
s.go-mpulse.net/boomerang/2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF	56.0 KiB	36.7 KiB
www.washingtonpost.com/assembler/_next/static/chunks/7432.c5867328f842b334.js	40.8 KiB	33.3 KiB
www.washingtonpost.com/assembler/_next/static/chunks/8178-6a7ae34a23fbb624.js	36.1 KiB	29.4 KiB
www.washingtonpost.com/assembler/_next/static/chunks/3858-46e3a952cf31a4d0.js	115.9 KiB	28.3 KiB
www.washingtonpost.com/assembler/_next/static/chunks/3039-739d6628ad738b7b.js	31.0 KiB	24.3 KiB
www.washingtonpost.com/assembler/_next/static/chunks/main-5dae8a7b163ecf2e.js	44.5 KiB	24.2 KiB
live.primis.tech/live/liveView.php?s=121284&cbuster=1776294038177	36.4 KiB	20.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
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	1.5 s	1.4 s	3.4 ms
www.googletagmanager.com/gtm.js?id=GTM-WHNNX8B	556 ms	500 ms	24 ms
www.washingtonpost.com/	554 ms	60 ms	5.9 ms
Unattributable	237 ms	16 ms	0.0 ms
/assembler/_next/static/chunks/pages/render/[slug]-0fbc09...	194 ms	194 ms	0.1 ms
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	179 ms	136 ms	12 ms
/assembler/_next/static/chunks/pages/_app-d0be26829892b38...	175 ms	137 ms	33 ms
www.washingtonpost.com/zeus/main.js	93 ms	79 ms	11 ms
c.amazon-adsystem.com/aax2/apstag.js	54 ms	39 ms	13 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
Style & Layout	333 ms
Other	318 ms
Script Parsing & Compilation	224 ms
Parse HTML & CSS	129 ms
Garbage Collection	87 ms
Rendering	83 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 the main frame.	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 2.4 KiB

URL	Transfer Size	Est Savings
--sxs{--sxs:0 wpds-t-crrfKS wpds-dark.wpds-dark wpds-light} …	33.8 KiB	2.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.5 KiB

URL	Transfer Size	Est Savings
live.primis.tech/live/liveView.php?s=121284&cbuster=1776294038177	36.4 KiB	5.5 KiB

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: 0.0 ms 42.9 KiB

URL	Transfer Size	Est Savings
--sxs{--sxs:0 wpds-t-crrfKS wpds-dark.wpds-dark wpds-light} …	33.6 KiB	24.3 KiB
www.washingtonpost.com/assembler/_next/static/css/ebb15ca6e4fd7829.css	22.1 KiB	18.6 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
www.washingtonpost.com/	436.6 KiB
/assembler/_next/static/chunks/pages/_app-d0be26829892b38...	411.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHNNX8B	200.5 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	186.4 KiB
www.washingtonpost.com/assembler/_next/static/chunks/9301-fdb71a1a1c24410f.js	186.4 KiB
www.washingtonpost.com/zeus/main.js	159.6 KiB
/assembler/_next/static/chunks/1c616b8c-1959175d299606b5.js	138.6 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js	128.5 KiB
www.washingtonpost.com/assembler/_next/static/chunks/3858-46e3a952cf31a4d0.js	116.4 KiB
rumcdn.geoedge.be/09d3a988-6f0e-4f65-9970-88d250fb501d/grumi.js	116.2 KiB

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

●Layout shift culprits

●Optimize DOM size

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●User Timing marks and measures 52 user timings

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 130 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 11 layout shifts found

○INP breakdown

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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find a recipe `div > div.wpds-c-jwIEZH > div.wpds-c-iQOSPq > span#radix-:r9:`

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.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > iframe `body > iframe`

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.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-right > figure.w-100 > div.dib > a.art-link `div.card-right > figure.w-100 > div.dib > a.art-link`
div.card-right > figure.w-100 > div.dib > a.art-link `div.card-right > figure.w-100 > div.dib > a.art-link`
div.card-top > figure.w-100 > div.dib > a.art-link `div.card-top > figure.w-100 > div.dib > a.art-link`
div.card-right > figure.w-100 > div.dib > a.art-link `div.card-right > figure.w-100 > div.dib > a.art-link`
div.card-right > figure.w-100 > div.dib > a.art-link `div.card-right > figure.w-100 > div.dib > a.art-link`
div.card-right > figure.w-100 > div.dib > a.art-link `div.card-right > figure.w-100 > div.dib > a.art-link`
div.card-left > div.w-100 > div.dib > a.art-link `div.card-left > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
div.card-right > div.w-100 > div.dib > a.art-link `div.card-right > div.w-100 > div.dib > a.art-link`
footer.hpgrid-max-width > footer.wpds-c-goYfNd > div.wpds-c-Kzyvj > a.wpds-c-bEBODO `footer.hpgrid-max-width > footer.wpds-c-goYfNd > div.wpds-c-Kzyvj > a.wpds-c-bEBODO`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Trending Exercise timing Commanders uniform Eric Swalwell Dog gardening Baby el… `main#main-content > div.PJLV > div.wpds-c-bzYzZp > ul.wpds-c-qdpUL`
About The Post Newsroom Policies & Standards WP Creative Group Diversity & Incl… `footer.wpds-c-goYfNd > div.wpds-c-gjdxqp > div.wpds-c-bPNjhd > ul.wpds-c-cpmugS`
Trending Politics Elections Opinions National World Style Sports Business Clima… `footer.wpds-c-goYfNd > div.wpds-c-gjdxqp > div.wpds-c-bPNjhd > ul.wpds-c-cpmugS`
WP Intelligence Enterprise Subscriptions Become a Subscriber Gift Subscriptions… `footer.wpds-c-goYfNd > div.wpds-c-gjdxqp > div.wpds-c-bPNjhd > ul.wpds-c-cpmugS`
Contact the Newsroom Contact Customer Care Contact the Opinions Team Advertise … `footer.wpds-c-goYfNd > div.wpds-c-gjdxqp > div.wpds-c-bPNjhd > ul.wpds-c-cpmugS`
Digital Products Terms of Sale Print Products Terms of Sale Terms of Service Pr… `footer.wpds-c-goYfNd > div.wpds-c-gjdxqp > div.wpds-c-bPNjhd > ul.wpds-c-cpmugS`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About The Post `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Newsroom Policies & Standards `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
WP Creative Group `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Diversity & Inclusion `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Careers `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Media & Community Relations `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Accessibility Statement `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Trending `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Politics `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Elections `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Opinions `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
National `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
World `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Style `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Sports `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Business `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Climate `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Well+Being `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
D.C., Md., & Va. `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Obituaries `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Weather `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Arts & Entertainment `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Recipes `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
WP Intelligence `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Enterprise Subscriptions `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Become a Subscriber `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Gift Subscriptions `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Mobile & Apps `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Newsletters & Alerts `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Washington Post Live `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Reprints & Permissions `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Post Store `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Books & E-Books `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Print Special Editions Store `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Today’s Paper `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Public Notices `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Contact the Newsroom `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Contact Customer Care `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Contact the Opinions Team `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Advertise `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Licensing & Syndication `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Request a Correction `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Send a News Tip `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Report a Vulnerability `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Digital Products Terms of Sale `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Print Products Terms of Sale `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Terms of Service `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Privacy Policy `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Cookie Settings `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Submissions & Discussion Policy `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
RSS Terms of Service `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Sitemap `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`
Ad Choices `div.wpds-c-bPNjhd > ul.wpds-c-cpmugS > span.wpds-c-PJLV > li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○No form fields have multiple labels

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

○Input buttons have discernible text.

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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
Unload event listeners are deprecated and will be removed.	line 1, col 8843

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 maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Source	Description
www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js	`Error updating the status via PrivacyAPI: TypeError: Cannot read properties of null (reading 'Dt') at s.updateStatus (https://www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js:1:5623)`
www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js	`Error updating the status via PrivacyAPI: TypeError: Cannot read properties of null (reading 'Dt') at s.updateStatus (https://www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js:1:5623)`
www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js	`Error updating the status via PrivacyAPI: TypeError: Cannot read properties of null (reading 'Dt') at s.updateStatus (https://www.washingtonpost.com/subscribe/privacy-fe-api/privacy-fe-api.min.js:1:5623)`
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at lg (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46435) at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:121150) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at ly (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:46889) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:100009 at oD (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:106229) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99177) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94030) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)
/assembler/_next/static/chunks/framework-c6ee5607585ef091.js	Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at i (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:120819) at oO (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:99117) at https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98984 at oF (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:98991) at ox (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:95743) at oS (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:94298) at x (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:137528) at MessagePort.T (https://www.washingtonpost.com/assembler/_next/static/chunks/framework-c6ee5607585ef091.js:1:138058)