Spain · Madrid Completed: Apr 15, 2026 23:01 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 68 / 100
Based on 8 categories, 0 sections
Room to improve — your 33.3s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 16.1 MB (5.4 MB transferred)
Performance issues directly impact user engagement and conversion rates.
2 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/8f9b5955-f1c5-4152-8337-67601291040f)<a href="https://beavercheck.com/results/8f9b5955-f1c5-4152-8337-67601291040f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwashingtonpost.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwashingtonpost.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 33.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.
$500 investment → $1.36/month returns + USD 157,500 risk avoided
$500
5h · 5 findings
$1.36 /mo
~$16 / year
USD 157,500
if kept compliant
$150 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,516 / year if left unfixed
$157,500
+5 more
$1.36 /mo
16963.9 MB/mo × 0.080 USD/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
3.94 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
33.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5.19 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.024
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
8.94 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.
33.44 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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... | 203.1 KiB | 155.1 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... | 152.4 KiB | 108.7 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... | 105.0 KiB | 74.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... | 122.7 KiB | 74.7 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... | 93.6 KiB | 66.8 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... | 90.2 KiB | 64.3 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... | 63.2 KiB | 30.5 KiB |
An illustration in muted colors of George Washington holding a map. Behind him … figure.w-100 > div.dib > a.art-link > img.border-box | /wp-apps/imrs.php?src=https%3A%2F%2Farc-anglerfish-washpo... | 42.3 KiB | 30.2 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... | 42.1 KiB | 30.0 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... | 58.3 KiB | 28.1 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... | 57.2 KiB | 27.6 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... | 53.1 KiB | 25.6 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... | 23.9 KiB | 17.0 KiB |
An illustration in muted colors of George Washington holding a map. Behind him … figure.w-100 > div.dib > a.art-link > img.border-box | /wp-apps/imrs.php?src=https%3A%2F%2Farc-anglerfish-washpo... | 26.0 KiB | 12.5 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| washingtonpost.com/ | 799 ms |
| www.washingtonpost.com/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| --sxs{--sxs:0 wpds-t-crrfKS wpds-dark.wpds-dark wpds-light} … | 34.1 KiB | 27.3 KiB |
| www.washingtonpost.com/assembler/_next/static/css/ebb15ca6e4fd7829.css | 22.1 KiB | 19.8 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 8.3 s |
| Other | 1.2 s |
| Script Parsing & Compilation | 921 ms |
| Style & Layout | 782 ms |
| Parse HTML & CSS | 365 ms |
| Garbage Collection | 223 ms |
| Rendering | 190 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
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| --sxs{--sxs:0 wpds-t-crrfKS wpds-dark.wpds-dark wpds-light} … | 34.2 KiB | 2.4 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| live.primis.tech/live/liveView.php?s=121284&cbuster=1776294005693 | 36.6 KiB | 5.6 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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-top > 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-top > 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-top > 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-top > 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 > 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.wpds-c-jHFhWE > div.wpds-c-eQbjSQ > div.wpds-c-Kzyvj > a.wpds-c-bEBODO footer.wpds-c-jHFhWE > div.wpds-c-eQbjSQ > 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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Trending
Exercise timing
Commanders uniform
Eric Swalwell
Dog gardening
Baby el… div > div.PJLV > div.wpds-c-bzYzZp > ul.wpds-c-qdpUL |
WP Intelligence
Ask The Post AI
WP Creative Group
Diversity & Inclusion
Careers… div.wpds-c-dCLTmK > div#radix-:rb: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc |
Trending
Politics
Elections
Opinions
National
World
Style
Sports
Business
Clima… div.wpds-c-dCLTmK > div#radix-:rd: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc |
WP Intelligence
Enterprise Subscriptions
Become a Subscriber
Gift Subscriptions… div.wpds-c-dCLTmK > div#radix-:rf: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc |
Contact the Newsroom
Contact Customer Care
Contact the Opinions Team
Advertise
… div.wpds-c-dCLTmK > div#radix-:rh: > div.wpds-c-gsubXz > ul.wpds-c-iYXqXc |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
WP Intelligence div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Ask The Post AI div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
WP Creative Group div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Diversity & Inclusion div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Careers div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Media & Community Relations div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Accessibility Statement div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Trending div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Politics div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Elections div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Opinions div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
National div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
World div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Style div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Sports div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Business div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Climate div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Well+Being div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
D.C., Md., & Va. div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Obituaries div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Weather div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Arts & Entertainment div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Recipes div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
WP Intelligence div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Enterprise Subscriptions div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Become a Subscriber div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Gift Subscriptions div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Mobile & Apps div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Newsletters & Alerts div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Washington Post Live div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Reprints & Permissions div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Post Store div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Books & E-Books div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Print Special Editions Store div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Today’s Paper div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Public Notices div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Contact the Newsroom div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Contact Customer Care div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Contact the Opinions Team div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Advertise div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Licensing & Syndication div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Request a Correction div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Send a News Tip div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Report a Vulnerability div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
Download the Washington Post App div.wpds-c-gsubXz > ul.wpds-c-iYXqXc > span.wpds-c-PJLV > li.wpds-c-laJFlQ |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.04 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.83 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.78 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
10.57 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.
8.08 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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.
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.
Performance issues directly impact user engagement and conversion rates.
| 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.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
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
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
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.
Performance issues directly impact user engagement and conversion rates.
| 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.
Performance issues directly impact user engagement and conversion rates.
| 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.
Performance issues directly impact user engagement and conversion rates.
| 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.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) | |
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) |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Send Feedback