Mobile 375 × 812

Desktop 1440 × 900

Score: 71 / 100
Based on 8 categories, 0 sections
Room to improve — your 54.1s load time is above Google's 2.5s 'Good' threshold.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
High page weight means excess energy use and carbon emissions per visit.
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.
Page weighs 29.3 MB (7.6 MB transferred)
Performance issues directly impact user engagement and conversion rates.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
356 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
357 HTTP requests — consider bundling or reducing
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
Nothing in this quadrant — good news.
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/062f286b-9d51-45fd-ad8e-91d5d5e60d7f)<a href="https://beavercheck.com/results/062f286b-9d51-45fd-ad8e-91d5d5e60d7f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnola.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fnola.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 54.1s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute 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 conversion rate.
10 barrier(s) likely increasing bounce by ~40%.
Page takes 54.1s to load
+12% bounceUsers abandon at ~3s — you're 51.6s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 22.7s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Severe layout shift during page load
+6% bounceUsers mis-click when content jumps — converting intent into frustration
Fix: Reserve space for images, ads, and embeds with explicit width/height
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$900 investment → $1.91/month returns + USD 157,500 risk avoided
$900
9h · 5 findings
$1.91 /mo
~$23 / year
USD 157,500
if kept compliant
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.
9.0 developer hours at $100/hr
Based on United States rates ($100/hr)
$13,127 / month at risk
~$157,523 / year if left unfixed
$157,500
+5 more
$1.91 /mo
23828.2 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 3 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.
23.82 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
54.09 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
22.73 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.259
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
25.46 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.
68.99 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.
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.
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.
| URL | Est Savings |
|---|---|
| /s/opensans/v44/memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOS... | 5.0 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings |
|---|---|---|
| assets-jpcust.jwpsrv.com/thumbnails/DuRnTr5u-320.jpg | 64.0 KiB | 34.4 KiB |
| /recaptcha/api2/payload?p=06AFcWeA7VRmqdgXxLv3-t0PucAQ04v... | 30.7 KiB | 16.1 KiB |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
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.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
| 0.116 | |
| 0.090 | |
| 0.033 | |
| 0.020 | |
| 0.015 | |
| 0.006 | |
| 0.005 | |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
body > div#loading_div > div.loader > ::after body > div#loading_div > div.loader > ::after | 0.001 |
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 | 38.9 s |
| Other | 6.5 s |
| Style & Layout | 3.4 s |
| Script Parsing & Compilation | 3.0 s |
| Rendering | 1.3 s |
| Garbage Collection | 1.1 s |
| Parse HTML & CSS | 401 ms |
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.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
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.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
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. | fp.nola.com/prod/nola/fp.min.js?2026321 line 7, col 55748 |
| Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. | engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 465644 |
| SharedStorage | /pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234 |
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 |
|---|---|
Segment snippet included twice. | |
engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 667759 | TypeError: r.findIndex is not a function
at https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:667760
at i (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:128571)
at L.<anonymous> (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:759779)
at Object.next (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:681366)
at r (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:680231) |
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.
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Performance issues directly impact user engagement and conversion rates.
| Blocking Directive Source |
|---|
https://www.nola.com/robots.txt |
To appear in search results, crawlers need access to your app.
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
4.07 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
14.73 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.62 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.190
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.66 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.
20.39 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
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.
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 | |
|---|---|---|---|
| s0.2mdn.net/sadbundle/4973411683441390716/images/img-02_970x250.jpg | 266.9 KiB | 172.1 KiB | |
| s0.2mdn.net/sadbundle/4973411683441390716/images/img-01_970x250.jpg | 99.6 KiB | 38.4 KiB | |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-1 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-1 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/DuRnTr5u-320.jpg | 64.0 KiB | 34.4 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-2 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-2 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/oz1uv1ri-320.jpg | 52.2 KiB | 22.6 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-3 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-3 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/ceitypva-320.jpg | 49.0 KiB | 19.3 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-4 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-4 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/tkvck17a-320.jpg | 48.1 KiB | 18.5 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-6 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-6 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/trKMB6Em-320.jpg | 46.3 KiB | 16.8 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-9 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-9 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/ch94klso-320.jpg | 45.9 KiB | 16.1 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-5 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-5 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/ct04soit-320.jpg | 40.1 KiB | 10.6 KiB |
div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-7 > div.jw-wrapper > div.jw-preview div.player-wrapper > div#jwExperienceDiv_1ni4z9ibsl1c-7 > div.jw-wrapper > div.jw-preview | assets-jpcust.jwpsrv.com/thumbnails/hnn0orlw-320.jpg | 35.1 KiB | 5.5 KiB |
| /ytc/AIdro_mMZTxOoiSgJyaOKndsB6eyGbg_Y6hXYq-kREUCb6MHDg=s... | 5.3 KiB | 5.1 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS
NEWS
SPORTS
ENTERTAINMENT
GAME… body.app-editorial > div#site-container > div.offcanvas-inner | 0.083 |
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS
NEWS
SPORTS
ENTERTAINMENT
GAME… body.app-editorial > div#site-container > div.offcanvas-inner | 0.065 |
| 0.052 | |
| 0.048 | |
| 0.046 | |
| 0.037 | |
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS
NEWS
SPORTS
ENTERTAINMENT
GAME… body.app-editorial > div#site-container > div.offcanvas-inner | 0.033 |
| 0.016 | |
Advertisement section#main-page-container > div.row > div.fixed-col-right > div#sticky-side-primary-spacer | 0.016 |
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS
NEWS
SPORTS
ENTERTAINMENT
GAME… body.app-editorial > div#site-container > div.offcanvas-inner | 0.009 |
| 0.001 | |
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS div#site-navbar-container > nav#main-navigation > div#navbar-collapse > div.pull-right | 0.001 |
| 0.001 | |
LOG IN
SUBSCRIBE
74°
E-EDITION
NEWSLETTERS div#site-navbar-container > nav#main-navigation > div#navbar-collapse > div.pull-right | 0.001 |
| 0.001 |
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.
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 | 14.1 s |
| Other | 2.5 s |
| Script Parsing & Compilation | 1.9 s |
| Style & Layout | 1.1 s |
| Garbage Collection | 719 ms |
| Rendering | 361 ms |
| Parse HTML & CSS | 239 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 |
| The page did not finish loading before navigating away. | Not actionable |
| An iframe on the page started a navigation that did not complete. | Not actionable |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .jw-reset{text-align:left;direction:ltr} … | 18.7 KiB | 12.9 KiB |
| engage.nola.com/prod/nola/t8y9347t.min.css?2026321 | 50.2 KiB | 5.5 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 |
|---|---|---|
| /both_domains/right_rail_newsletter_signup/nl_rr_script.js?6 | 9.5 KiB | 2.3 KiB |
| /both_domains/right_rail_newsletter_signup/nl_rr_script.js?6 | 9.5 KiB | 2.3 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 |
|---|---|---|
| .jw-reset{text-align:left;direction:ltr} … | 18.7 KiB | 18.0 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.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive | tpc.googlesyndication.com/pagead/imgad?id=CICAgJC2q5CKQhABGAEyCBSs1gccyVo9 |
NOLA.com div.nl-rr-flex-column > div.nl-right-rail-top > div.logo-container > img.nl-rr-logo | /images/companyLogos/nola/LOGO-NOLA-dot-com-512x512.png |
NOLA.com div.nl-rr-flex-column > div.nl-right-rail-top > div.logo-container > img.nl-rr-logo | /images/companyLogos/nola/LOGO-NOLA-dot-com-512x512.png |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
reCAPTCHA | Google Privacy Policy and Terms of Service apply section.nl-right-rail-module > div.nl-rr-flex-column > div.recaptcha-policy > span |
Privacy Policy div.nl-rr-flex-column > div.recaptcha-policy > span > a |
Terms of Service div.nl-rr-flex-column > div.recaptcha-policy > span > a |
reCAPTCHA | Google Privacy Policy and Terms of Service apply section.nl-right-rail-module > div.nl-rr-flex-column > div.recaptcha-policy > span |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
GOP state rep accuses Louisiana AG Liz Murrill of ‘coercion:’ ‘Don’t be swayed … div.card-container > div.card-body > div.card-headline > h4.tnt-headline |
THE LATEST div.clearfix > div.block-title > div.block-title-inner > h4 |
SERVICES div.clearfix > div.block-title > div.block-title-inner > h4 |
These are opportunities to improve keyboard navigation in your application.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive |
body.app-editorial > img#06db9294 body.app-editorial > img#06db9294 |
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 |
|---|
body.app-editorial > div#x-reveal-ad > a#x-reveal-ad-link body.app-editorial > div#x-reveal-ad > a#x-reveal-ad-link |
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 |
|---|
LOG IN
SUBSCRIBE
div#tncms-region-main-nav-right-region > div#tncms-block-1491880 > div.header-umbrella-navigation-custom > ul.list-inline |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
HOME div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link |
NEWS div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link |
OPINION div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link |
SPORTS div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link |
DIGITAL ADVERTISING div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
HELP / CONTACT US div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
RSS FEEDS div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
MEDIA KIT div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
EEDITION div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
CAREERS div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
REVIEWING THE RECORD div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
MANAGE YOUR DONATION div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link |
HOMES div#tncms-region-nav-footer-col-three-nav > ul#footer-col-three-nav_menu > li > a.nav-link |
PETS div#tncms-region-nav-footer-col-three-nav > ul#footer-col-three-nav_menu > li > a.nav-link |
Report a delivery issue div#tncms-block-1491628 > ul > li > a |
Create a temporary stop div#tncms-block-1491628 > ul > li > a |
Sign up for recurring payments div#tncms-block-1491628 > ul > li > a |
Pay your bill div#tncms-block-1491628 > ul > li > a |
Update your billing info div#tncms-block-1491628 > ul > li > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
74° div#weather-1491856 > ul.nav > li.current-conditions > a.dropdown-toggle |
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Performance issues directly impact user engagement and conversion rates.
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. | fp.nola.com/prod/nola/fp.min.js?2026321 line 7, col 55748 |
| Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. | engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 465644 |
| SharedStorage | f362.nola.com/script.js line 66, col 205 |
| Unload event listeners are deprecated and will be removed. | fp.nola.com/prod/nola/fp.min.js?2026321 line 7, col 55748 |
| Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. | engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 465644 |
| Unload event listeners are deprecated and will be removed. | fp.nola.com/prod/nola/fp.min.js?2026321 line 7, col 55748 |
| Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. | engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 465644 |
| SharedStorage | f362.nola.com/script.js line 66, col 205 |
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 |
|---|---|
Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
| |
/auth0-redirect/?returnUrl=https%3A%2F%2Fwww.nola.com%2F&... line 64, col 20 | ReferenceError: googletag is not defined
at https://www.nola.com/auth0-redirect/?returnUrl=https%3A%2F%2Fwww.nola.com%2F&error=login_required&error_description=Login%20required&state=aW5hcUZUR2hmQ204Wi1ZblBscmVyTHVXY3BlaU4uT25SbDhJeXo4QnpQUQ%3D%3D:65:21 |
Segment snippet included twice. | |
Segment snippet included twice. | |
engage.nola.com/prod/nola/t8y9347t.min.js?2026321 line 7, col 667759 | TypeError: r.findIndex is not a function
at https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:667760
at i (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:128571)
at L.<anonymous> (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:759779)
at Object.next (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:681366)
at r (https://engage.nola.com/prod/nola/t8y9347t.min.js?2026321:8:680231) |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive div#x-reveal-slides > div.hidden-xs > div#x-reveal-slide-1 > img.img-responsive |
body.app-editorial > img#06db9294 body.app-editorial > img#06db9294 |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback