C — https://jdpower.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.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Amazon Route 53 · 857 peers

You 72

Avg 72

At average

0 50 100

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

Apple · 1067 peers

You 72

Avg 73

At average

0 50 100

Better than 32% of Apple sites See full Apple 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

65 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%2Fjdpower.com)](https://beavercheck.com/results/d5d7c112-5d6c-4c79-9803-e06896bd95b8)

HTML

<a href="https://beavercheck.com/results/d5d7c112-5d6c-4c79-9803-e06896bd95b8"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjdpower.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fjdpower.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 3.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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 3.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 7 warning

8 barrier(s) likely increasing bounce by ~24%.

Speed (2)

Page loads in 3.7s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 1.2s over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Page feels frozen for 676ms

+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

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 → $2,272/month returns + USD 157,500 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$2,272 /mo

~$27,267 / year

Conversions recovered $2,272
Bandwidth savings $0.51

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,126 / month at risk

~$157,506 / 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

+4 more

Bandwidth Waste

$0.51 /mo

6391.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~639 KB per page load
Saves $0.51/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

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.

3.21 s

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

3.71 s

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

676 ms

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

0.004

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

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.jdpower.com/themes/custom/themekit/dist/fonts/icomoon/fonts/icomoon.woff	40 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:29.469 source:map[column:156 line:13 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA 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:0.809 source:map[column:49637 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:0.256 source:map[column:50335 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:0.168 source:map[column:50393 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:0.171 source:map[column:50457 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:16.131 source:map[column:49615 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:11.872 source:map[column:168686 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_MtX0pMkxnwOKSSMfckKrmKCl9i2V8RVthNU5n8zmxjI.js?scope=footer&delta=4&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:0.347 source:map[column:51395 line:2 type:source-location url:https://www.jdpower.com/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-hmBfAPcemKyn8.js?scope=footer&delta=0&language=en&theme=themekit&include=eJxLTEkpyU_Mq9RPhDL00ory80p0SjJSc1OzM0v0YQwAU84QQA urlProvider:network]] map[reflowTime:1.226 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: Vehicle driving in the fastlane

path: 1,HTML,1,BODY,2,DIV,0,DIV,2,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,4,IMG

selector: div.field > div.paragraph > picture > img

snippet: <img src="https://www.jdpower.com/sites/default/files/styles/large/public/image/2026…" alt="Vehicle driving in the fastlane">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

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
fonts.googleapis.com/css?family=Roboto:400,700,900&display=swap	2.1 KiB	832 ms
/sites/default/files/css/css_donWm6kR_n8DQP-kk_vbONLsIS8m...	4.0 KiB
/sites/default/files/css/css_4Gh9U1t-sWzlk4d6xQ57ycanzSED...	60.2 KiB	1.2 s
cdn.cookielaw.org/scripttemplates/otSDKStub.js	0 B	780 ms
cdn.cookielaw.org/consent/503d6d4c-5130-4af9-bccb-dd494ae5b0d6/OtAutoBlock.js	0 B	780 ms
/sites/default/files/css/css_f8MCz2m2OpEPtoWbYI5Ti2mji-XO...	1.6 KiB

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
js.hsforms.net/forms/v2.js	300.0 s	193.8 KiB
player.vimeo.com/api/player.js	1800.0 s	9.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
static.addtoany.com/menu/page.js	86400.0 s	2.2 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
www.gstatic.com/recaptcha/api2/info_2x.png	604800.0 s	689 B
www.gstatic.com/recaptcha/api2/refresh_2x.png	604800.0 s	624 B
www.gstatic.com/recaptcha/api2/audio_2x.png	604800.0 s	554 B

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
Busy indoor car showroom with multiple rows of parked vehicles in different col… `div.paragraph > div.card-image > div.field > img`	/sites/default/files/styles/large_card/public/image/2026-...	87.8 KiB	31.7 KiB
Three JD Power customer satisfaction trophies with gold bases and plaques readi… `div.layout__region > div.block > div.block-content > img`	/sites/default/files/styles/large_hq/public/image/2026-01...	52.3 KiB	14.7 KiB
Abstract digital illustration of a car outlined in teal and orange neon lines, … `div.paragraph > div.card-image > div.field > img`	/sites/default/files/styles/large_card/public/image/2026-...	62.4 KiB	13.7 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: 1.0 s

URL	Time Spent
jdpower.com/	1.0 s
www.jdpower.com/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 517 ms

URL	Time Spent
www.jdpower.com/	617 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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: 330 ms 45.7 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_4Gh9U1t-sWzlk4d6xQ57ycanzSED...	60.1 KiB	45.7 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.jdpower.com/	1.1 s	24 ms	3.5 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	939 ms	849 ms	67 ms
/sites/default/files/js/js_-Y9pL2R33D_IXxzcoqasrlCSBAsP9-...	642 ms	382 ms	6.7 ms
Unattributable	411 ms	9.6 ms	0.0 ms
js.hsforms.net/forms/v2.js	385 ms	273 ms	58 ms
www.googletagmanager.com/gtag/js?id=G-0SRLMX84DV&cx=c&gtm=4e64k0h1	251 ms	205 ms	35 ms
www.googletagmanager.com/gtm.js?id=GTM-KFGX26	163 ms	130 ms	31 ms
/sites/default/files/js/js_klI2-RHF_KZfp0eqb7LlNXhSKBYmiS...	63 ms	56 ms	7.6 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.0 s
Other	833 ms
Style & Layout	650 ms
Script Parsing & Compilation	233 ms
Rendering	223 ms
Parse HTML & CSS	133 ms
Garbage Collection	42 ms

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

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	162.5 KiB
js.hsforms.net/forms/v2.js	186.4 KiB	68.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KFGX26	140.2 KiB	67.3 KiB
www.googletagmanager.com/gtag/js?id=G-0SRLMX84DV&cx=c&gtm=4e64k0h1	159.1 KiB	65.1 KiB
/sites/default/files/js/js_MtX0pMkxnwOKSSMfckKrmKCl9i2V8R...	62.2 KiB	35.9 KiB
static.addtoany.com/menu/modules/core.ydpp7jcu.js	25.7 KiB	21.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Home `div.region-content > div#block-themekit-branding > a.site-logo > img`	www.jdpower.com/themes/custom/themekit/logo.svg

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,081 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 17 long tasks found

●Avoid non-composited animations 3 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

Accessibility

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

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Main Menu Automotive Automotive Benchmarks, Insights & Awards Benchmarks, Insig… `body.site-main > div.dialog-off-canvas-main-canvas > div.off-canvas-wrapper > div#offCanvas`

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

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OEMS `div.field__item > div.paragraph > div.paragraph-content > h4#oems`
JD Power connects customer truth, advanced analytics, and industry expertise to… `div.layout__region > div.block > div.clearfix > h6`

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How Long Can the Industry Stretch Affordability? The Rise of 84-Month Financing… `div.slick-track > div#slick-slide00 > div > a.node`
2026 U.S. Healthcare Digital Experience Study 07 April 2026 HEALTHCARE READ MOR… `div.slick-track > div#slick-slide10 > div > a.node`

○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

●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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

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

●Select elements have associated label elements.

●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

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

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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

○`<object>` elements have alternate text

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

100

Best Practices

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
li.menu-item > ul.menu > li.js-drilldown-back > a `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`

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

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

996 ms

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

1.13 s

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

24 ms

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

0.009

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

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.jdpower.com/themes/custom/themekit/dist/fonts/icomoon/fonts/icomoon.woff	40 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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: Vehicle driving in the fastlane

path: 1,HTML,1,BODY,2,DIV,0,DIV,2,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,1,DIV,0,DIV,0,PICTURE,4,IMG

selector: div.field > div.paragraph > picture > img

snippet: <img src="https://www.jdpower.com/sites/default/files/styles/large/public/image/2026…" alt="Vehicle driving in the fastlane">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

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
fonts.googleapis.com/css?family=Roboto:400,700,900&display=swap	2.1 KiB	218 ms
cdn.cookielaw.org/consent/503d6d4c-5130-4af9-bccb-dd494ae5b0d6/OtAutoBlock.js	0 B	236 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	0 B	236 ms
/sites/default/files/css/css_4Gh9U1t-sWzlk4d6xQ57ycanzSED...	60.1 KiB	240 ms
/sites/default/files/css/css_donWm6kR_n8DQP-kk_vbONLsIS8m...	3.7 KiB
/sites/default/files/css/css_f8MCz2m2OpEPtoWbYI5Ti2mji-XO...	1.5 KiB

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
js.hsforms.net/forms/v2.js	300.0 s	193.8 KiB
player.vimeo.com/api/player.js	1800.0 s	9.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
static.addtoany.com/menu/page.js	86400.0 s	2.2 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
www.gstatic.com/recaptcha/api2/info_2x.png	604800.0 s	689 B
www.gstatic.com/recaptcha/api2/refresh_2x.png	604800.0 s	624 B
www.gstatic.com/recaptcha/api2/audio_2x.png	604800.0 s	554 B

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
Busy indoor car showroom with multiple rows of parked vehicles in different col… `div.paragraph > div.card-image > div.field > img`	/sites/default/files/styles/large_card/public/image/2026-...	87.8 KiB	34.0 KiB
Abstract digital illustration of a car outlined in teal and orange neon lines, … `div.paragraph > div.card-image > div.field > img`	/sites/default/files/styles/large_card/public/image/2026-...	62.4 KiB	15.7 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: 461 ms

URL	Time Spent
jdpower.com/	461 ms
www.jdpower.com/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 506 ms

URL	Time Spent
www.jdpower.com/	606 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused 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: 50 ms 49.1 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_4Gh9U1t-sWzlk4d6xQ57ycanzSED...	60.0 KiB	49.1 KiB

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

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 419.7 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	162.5 KiB
js.hsforms.net/forms/v2.js	186.4 KiB	68.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KFGX26	140.2 KiB	67.3 KiB
www.googletagmanager.com/gtag/js?id=G-0SRLMX84DV&cx=c&gtm=4e64k0	159.1 KiB	65.2 KiB
/sites/default/files/js/js_MtX0pMkxnwOKSSMfckKrmKCl9i2V8R...	62.2 KiB	35.1 KiB
static.addtoany.com/menu/modules/core.ydpp7jcu.js	25.7 KiB	21.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Home `div.region-content > div#block-themekit-branding > a.site-logo > img`	www.jdpower.com/themes/custom/themekit/logo.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 70 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,113 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Solutions `div.region > div.region-content > nav#block-toplevelinsurance > ul.menu`
Industries Insights About Us For Vehicle Shoppers Log In Search Global Site `div.region > div.region-content > nav#block-headermenu > ul.menu`

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

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OEMS `div.field__item > div.paragraph > div.paragraph-content > h4#oems`
JD Power connects customer truth, advanced analytics, and industry expertise to… `div.layout__region > div.block > div.clearfix > h6`

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How Long Can the Industry Stretch Affordability? The Rise of 84-Month Financing… `div.block > div.block-content > div.summary-output > a.node`
Vehicle Configuration Complexity and Strong Used-Vehicle Market Wreak Havoc on … `div.block > div.block-content > div.summary-output > a.node`
Financial Health of U.S. Consumers Improves, But Spending Changes Hint at More … `div.block > div.block-content > div.summary-output > a.node`
2026 U.S. Healthcare Digital Experience Study 07 April 2026 HEALTHCARE READ MOR… `div.block > div.block-content > div.summary-output > a.node`
2026 Canada Investor Satisfaction Study 02 April 2026 FINANCIAL SERVICES READ M… `div.block > div.block-content > div.summary-output > a.node`
2026 China New Energy Vehicle Initial Quality Study (NEV-IQS) 02 April 2026 REA… `div.block > div.block-content > div.summary-output > a.node`

○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]`s are contained by their required parent element

●`[role]` values are valid

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

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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

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

●Select elements have associated label elements.

●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

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

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

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

○`<object>` elements have alternate text

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
cdn.cookielaw.org/consent/34134ffc-ab3f-46e8-9a5d-5b1855379eba.js	`Failed to load resource: the server responded with a status of 404 ()`

●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 issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Crawling and Indexing

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Automotive Automotive `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
Financial Services Financial Services `li.menu-item > ul.menu > li.js-drilldown-back > a`
Financial Services Financial Services `li.menu-item > ul.menu > li.js-drilldown-back > a`
Financial Services Financial Services `li.menu-item > ul.menu > li.js-drilldown-back > a`
Financial Services Financial Services `li.menu-item > ul.menu > li.js-drilldown-back > a`
BackBack Solutions `li.menu-item > ul.menu > li.js-drilldown-back > a`
BackBack Solutions `li.menu-item > ul.menu > li.js-drilldown-back > a`
BackBack Solutions `li.menu-item > ul.menu > li.js-drilldown-back > a`
BackBack Solutions `li.menu-item > ul.menu > li.js-drilldown-back > a`
BackBack Solutions `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
undefined `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`
Main Menu `li.menu-item > ul.menu > li.js-drilldown-back > a`

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

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://jdpower.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)

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

ARIA

Navigation

Best Practices

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Best Practices

General

SEO

Crawling and Indexing

Keyboard Shortcuts