C — https://latimes.com | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

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.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon ELB sites average 70

At average

Better than 64% of Amazon ELB sites See full Amazon ELB benchmark →

Amazon Route 53 sites average 72

At average

Better than 29% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

HSTS header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

No <main> landmark found

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

Accessibility › Landmark Structure

55 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Flatimes.com)](https://beavercheck.com/results/8d273542-2150-4987-937f-f1ee3d15c4e7)

HTML

<a href="https://beavercheck.com/results/8d273542-2150-4987-937f-f1ee3d15c4e7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flatimes.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Flatimes.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.8s 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.

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

1 accessibility issue excludes users who rely on assistive technology.

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

Conversion Barriers

3 critical 7 warning

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

Speed (2)

Page takes 4.8s to load

+12% bounce

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

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

Page feels frozen for 744ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

No viewport meta tag

+15% bounce

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

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

Content (3)

No Open Graph tags

+2% bounce

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

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

No structured data

+2% bounce

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

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

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Return on Investment

$500 investment → $3,592/month returns + USD 157,500 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$3,592 /mo

~$43,108 / year

Conversions recovered $3,592
Bandwidth savings $0.35

Regulatory risk avoided

USD 157,500

if kept compliant

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

Payback period

0 12mo 24mo

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

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

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,504 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+5 more

Bandwidth Waste

$0.35 /mo

4324.7 MB/mo × 0.080 USD/GB

Optimize transfer: save ~432 KB per page load
Saves $0.35/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.12 s

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

4.77 s

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

744 ms

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

0.178

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

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

9.73 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	300.0 s	87.1 KiB
cdn.speedcurve.com/js/lux.js?id=20201913	3600.0 s	11.3 KiB
libs.platform.latimes.com/newsletter-campaign-manager/latest.js	900.0 s	8.5 KiB
libs.platform.latimes.com/modalityjs/latest.js	900.0 s	3.3 KiB
www.latimes.com/styleguide/assets/icon-play-circle-outline-14x14-333333.svg	86400.0 s	2.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.177875] map[node:map[boundingRect:map[bottom:551 height:481 left:0 right:412 top:70 width:412] lhId:page-1-DIV nodeLabel:LATMG Streaming Now LA Times Media Group Streaming Produced by LA Times Studio… path:1,HTML,1,BODY,3,DIV,0,MAIN,1,DIV selector:body.page-body > div.page-ad-margins > main.page-main > div.column-container snippet:<div class="column-container two-column-container-7030 studios-stream-outer-container" data-split-mobile=""> type:node] score:0.177875]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:69.048 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Los Angeles , CA - December 19: The Automated People Mover makes it way past a …

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

selector: div.promo-media > a.link > picture > img.image

snippet: <img class="image" alt="Los Angeles , CA - December 19: The Automated People Mover makes it way pa…" srcset="https://ca-times.brightspotcdn.com/dims4/default/15457c9/2147483647/strip/…" sizes="100vw" width="840" height="560" src="https://ca-times.brightspotcdn.com/dims4/default/e89ce8f/2147483647/strip/…" decoding="async" loading="lazy">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	87.1 KiB	1.4 s

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Van Nuys, CA - October 30: Construction continues at a Department of Water and … `div.promo-media > a.link > picture > img.image`	/dims4/default/33ea445/2147483647/strip/true/crop/5815x38...	150.3 KiB	145.5 KiB
People drive their motorbikes past billboards showing the Iran's Supreme Leader… `div.promo-media > a.link > picture > img.image`	/dims4/default/35dc040/2147483647/strip/true/crop/8640x57...	63.1 KiB	59.2 KiB
CLB 500: Critical Loop's container-sized battery units can be transported on th… `div.promo-media > a.link > picture > img.image`	/dims4/default/71b509f/2147483647/strip/true/crop/7728x51...	40.6 KiB	38.0 KiB
FILE - A health worker administers a measles test on Fernando Tarin, of Seagrav… `div.promo-media > a.link > picture > img.image`	/dims4/default/fc95e8c/2147483647/strip/true/crop/2892x19...	36.3 KiB	34.1 KiB
Front Page of Today's L.A. Times `div.promo-media > a.link > picture > img.image`	/dims4/default/6592d52/2147483647/strip/true/crop/1200x12...	76.9 KiB	21.6 KiB
Hermosa Beach, CA - April 15: A bird flies near the Hermosa Beach Pier on Wedne… `div.promo-media > a.link > picture > img.image`	/dims4/default/f209cb0/2147483647/strip/true/crop/6000x40...	19.6 KiB	18.3 KiB
FILE - Rep. Jackie Speier, D-Calif., speaks during a news conference on Capitol… `div.promo-media > a.link > picture > img.image`	/dims4/default/6525223/2147483647/strip/true/crop/6000x40...	19.1 KiB	17.9 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 906 ms

URL	Time Spent
latimes.com/	906 ms
www.latimes.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
LATMG Streaming Now LA Times Media Group Streaming Produced by LA Times Studio… `body.page-body > div.page-ad-margins > main.page-main > div.column-container`	0.178

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 190 ms 43.6 KiB

URL	Transfer Size	Est Savings
.sr-only{height:1px;margin:-1px;overflow:hidden;padding:0;position:absolute;width:1px; … } …	20.1 KiB	16.9 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	16.1 KiB	15.8 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	11.4 KiB	10.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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 370 ms 276.4 KiB

URL	Transfer Size	Est Savings
www.latimes.com/styleguide/8250-d5c05034.bundle.js	217.0 KiB	192.0 KiB
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	86.7 KiB	48.5 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	50.3 KiB	35.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.latimes.com/	1.4 s	23 ms	5.7 ms
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	1.2 s	1.1 s	39 ms
Unattributable	482 ms	9.8 ms	0.0 ms
www.latimes.com/styleguide/8250-d5c05034.bundle.js	310 ms	219 ms	90 ms
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	235 ms	112 ms	14 ms
/caltimes/latimes/code/25071cf7a5575dcc9563c2de75955ff2.j...	113 ms	101 ms	10 ms
/caltimes/latimes/code/7bef0406d3d28127dd256b08467e9033.j...	64 ms	54 ms	9.2 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.8 s
Style & Layout	916 ms
Other	594 ms
Parse HTML & CSS	301 ms
Rendering	191 ms
Script Parsing & Compilation	190 ms
Garbage Collection	55 ms

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

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,408 KiB

●User Timing marks and measures 1 user timing

●Avoid long main-thread tasks 18 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FOR SUBSCRIBERS `div.promo-content > div.promo-title-container > div.relative > a.link`
FOR SUBSCRIBERS `div.promo-content > div.promo-title-container > div.relative > a.link`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

○`[role]` values are valid

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.latimes.com/styleguide/8250-d5c05034.bundle.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.25 s

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

1.50 s

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

6 ms

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

0.167

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

1.40 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.21 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	300.0 s	87.1 KiB
cdn.speedcurve.com/js/lux.js?id=20201913	3600.0 s	11.3 KiB
libs.platform.latimes.com/newsletter-campaign-manager/latest.js	900.0 s	8.5 KiB
libs.platform.latimes.com/modalityjs/latest.js	900.0 s	3.3 KiB
www.latimes.com/styleguide/assets/icon-play-circle-outline-14x14-333333.svg	86400.0 s	2.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

items: [map[node:map[type:text value:Total] score:0.167296] map[node:map[boundingRect:map[bottom:13747 height:13610 left:140 right:1210 top:137 width:1070] lhId:page-18-DIV nodeLabel:LATMG Streaming Now LA Times Media Group Streaming Produced by LA Times Studio… path:1,HTML,1,BODY,5,DIV selector:body.page-body > div.page-ad-margins snippet:<div class="page-ad-margins"> type:node] score:0.160326] map[node:map[boundingRect:map[bottom:136 height:58 left:204 right:337 top:78 width:133] lhId:page-11-LI nodeLabel:Entertainment path:1,HTML,1,BODY,3,DIV,0,DIV,0,NAV,0,GN-QUICKLINKS,0,UL,1,LI selector:nav.lg:flex > gn-quicklinks.block > ul.flex > li.inline-flex snippet:<li data-element="quick-links-item" class="inline-flex items-center px-2 xl:px-3" data-click="ql1"> type:node] score:0.006429] map[node:map[boundingRect:map[bottom:136 height:58 left:204 right:337 top:78 width:133] lhId:page-11-LI nodeLabel:Entertainment path:1,HTML,1,BODY,3,DIV,0,DIV,0,NAV,0,GN-QUICKLINKS,0,UL,1,LI selector:nav.lg:flex > gn-quicklinks.block > ul.flex > li.inline-flex snippet:<li data-element="quick-links-item" class="inline-flex items-center px-2 xl:px-3" data-click="ql1"> type:node] score:0.000541]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:30.896 source:map[column:48568 line:1 type:source-location url:https://ca-times.brightspotcdn.com/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide/Core.min.e930c837cb013d6a7bc26ce01b284470.gz.js urlProvider:network]]]

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

items: [map[reflowTime:28.336 source:map[column:3781 line:0 type:source-location url:https://www.latimes.com/styleguide/grapheneCarousels-035d4b89.bundle.js urlProvider:network]] map[reflowTime:2.56 source:map[column:4030 line:0 type:source-location url:https://www.latimes.com/styleguide/grapheneCarousels-035d4b89.bundle.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Front Page of Today's L.A. Times `div.promo-media > a.link > picture > img.image`	/dims4/default/66b748c/2147483647/strip/true/crop/1200x12...	49.4 KiB	38.2 KiB
Los Angeles, CA - December 31: USPS postal carrier John Ayala embraces Los Ange… `div.promo-media > a.link > picture > img.image`	/dims4/default/f22856e/2147483647/strip/true/crop/4851x32...	43.3 KiB	31.9 KiB
div.promo-media > div.custom-poster-image > picture > img.image `div.promo-media > div.custom-poster-image > picture > img.image`	/dims4/default/abc0825/2147483647/strip/true/crop/1080x19...	45.7 KiB	28.7 KiB
Photo composite of works of art at LACMA's new David Geffen Galleries `div.promo-media > a.link > picture > img.image`	/dims4/default/e60b3db/2147483647/strip/true/crop/3000x20...	27.1 KiB	21.0 KiB
Van Nuys, CA - October 30: Construction continues at a Department of Water and … `div.promo-media > a.link > picture > img.image`	/dims4/default/86d333a/2147483647/strip/true/crop/5815x38...	25.1 KiB	20.2 KiB
Los Angeles, CA - April 02, 2026: The steak au poivre with a side of Electric f… `div.promo-media > a.link > picture > img.image`	/dims4/default/d3ef835/2147483647/strip/true/crop/6605x44...	29.3 KiB	19.4 KiB
LOS ANGELES, CA - JULY 01: Los Angeles Police Headquarters located at First and… `div.promo-media > a.link > picture > img.image`	/dims4/default/5cbb537/2147483647/strip/true/crop/4000x26...	25.2 KiB	16.7 KiB
A collage of Thomas Pynchon book covers, including Thomas Pynchon book covers: … `div.promo-media > a.link > picture > img.image`	/dims4/default/51b49d0/2147483647/strip/true/crop/3000x20...	19.2 KiB	15.3 KiB
The 2025 Los Angeles Times Festival of Books celebrates all things books `div.promo-media > a.link > picture > img.image`	/dims4/default/e938f35/2147483647/strip/true/crop/3000x20...	19.0 KiB	15.0 KiB
Two men at a museum. `div.promo-media > a.link > picture > img.image`	/dims4/default/838745b/2147483647/strip/true/crop/4910x32...	19.7 KiB	13.0 KiB
illustration of readers discussing books in a cafe `div.promo-media > a.link > picture > img.image`	/dims4/default/4f244b2/2147483647/strip/true/crop/1825x12...	15.9 KiB	4.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Front Page of Today's L.A. Times

path: 1,HTML,1,BODY,5,DIV,0,MAIN,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,A,0,PICTURE,1,IMG

selector: div.promo-media > a.link > picture > img.image

snippet: <img class="image" alt="Front Page of Today's L.A. Times" srcset="https://ca-times.brightspotcdn.com/dims4/default/fe36bc2/2147483647/strip/…" sizes="(min-width: 1024px) and (max-width: 1239px) 768px, (min-width: 1240px) 568…" width="560" height="560" src="https://ca-times.brightspotcdn.com/dims4/default/66b748c/2147483647/strip/…" decoding="async" loading="lazy">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	87.1 KiB	460 ms

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 40 ms 249.6 KiB

URL	Transfer Size	Est Savings
www.latimes.com/styleguide/8250-d5c05034.bundle.js	217.0 KiB	165.4 KiB
activate.platform.californiatimes.com/caltimes/latimes/Bootstrap.js	86.7 KiB	48.5 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	50.3 KiB	35.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 41.0 KiB

URL	Transfer Size	Est Savings
.sr-only{height:1px;margin:-1px;overflow:hidden;padding:0;position:absolute;width:1px; … } …	20.5 KiB	15.1 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	16.1 KiB	15.1 KiB
/resource/0000016e-6bb5-d505-abef-fbb7e4420000/styleguide...	11.4 KiB	10.8 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 355 ms

URL	Time Spent
latimes.com/	355 ms
www.latimes.com/	0.0 ms

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
LATMG Streaming Now LA Times Media Group Streaming Produced by LA Times Studio… `body.page-body > div.page-ad-margins`	0.160
Entertainment `nav.lg:flex > gn-quicklinks.block > ul.flex > li.inline-flex`	0.006
Entertainment `nav.lg:flex > gn-quicklinks.block > ul.flex > li.inline-flex`	0.001

●Time to Interactive 2.2 s

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,583 KiB

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

Accessibility

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`
gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block `gn-quicklinks.block > ul.flex > li.inline-flex > button.inline-block`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FOR SUBSCRIBERS `div.promo-content > div.promo-title-container > div.relative > a.link`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Image elements have `[alt]` attributes

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

100

Best Practices

General

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.latimes.com/styleguide/8250-d5c05034.bundle.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Results for https://latimes.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (2)

Content (3)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Keyboard Shortcuts