Lighthouse Desktop

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
We deliver cutting edge solutions to power modern digital experiences. Scoped m… `body.flex > div.flex > main.flex-grow > footer.footer`	ahealthplace.com/images/footer.png	1011.5 KiB	755.4 KiB
About Us `div.footer-grid > div.footer-brand > a.logo-link-footer > img.logo-img`	ahealthplace.com/images/Logo-web.png	19.4 KiB	17.5 KiB
MySite Logo `div.header-container > div.flex-1 > a.logo-link > img.logo-img`	ahealthplace.com/api/media/view?key=site-AHP/1785922878791-4ovdoim.webp	11.8 KiB	11.1 KiB
About Us `div.footer-grid > div.footer-brand > a.logo-link-footer > img.logo-img`	ahealthplace.com/api/media/view?key=site-AHP/1785840000616-ytvkidb.webp	11.8 KiB	10.6 KiB

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
ahealthplace.com/quizzes	http/1.1
ahealthplace.com/_next/static/media/0484562807a97172-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/4c285fdca692ea22-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/6245472ced48d3be-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/78d0dd042ac6d54d-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/7db6c35d839a711c-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/8888a3826f4a3af4-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/b957ea75a84b6ea7-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/eaead17c7dbfcd5d-s.p.woff2	http/1.1
ahealthplace.com/_next/static/media/eafabf029ad39a43-s.p.woff2	http/1.1
ahealthplace.com/_next/static/css/50074081284c2ad0.css	http/1.1
ahealthplace.com/_next/static/css/9fefcb6f85f3184c.css	http/1.1
ahealthplace.com/_next/static/chunks/webpack-d31cbd99e39b3752.js	http/1.1
ahealthplace.com/_next/static/chunks/5d015edf-0b6b4c1594e984d1.js	http/1.1
ahealthplace.com/_next/static/chunks/4bd1b696-427c9ac60bb407ee.js	http/1.1
ahealthplace.com/_next/static/chunks/8058-09f30a0c2c75940c.js	http/1.1
ahealthplace.com/_next/static/chunks/main-app-c7606db0fd11d90f.js	http/1.1
ahealthplace.com/_next/static/chunks/app/global-error-5b7de3415934d87b.js	http/1.1
ahealthplace.com/_next/static/chunks/4804-b24d8def46edb26b.js	http/1.1
ahealthplace.com/_next/static/chunks/9094-915cefcd1f6cfd6b.js	http/1.1
ahealthplace.com/_next/static/chunks/4142-3f7753f6011ca268.js	http/1.1
ahealthplace.com/_next/static/chunks/app/layout-69c986a014c5d93b.js	http/1.1
ahealthplace.com/_next/static/chunks/app/error-77888b481a708143.js	http/1.1
ahealthplace.com/_next/static/chunks/bd904a5c-8373896e8b4dba99.js	http/1.1
ahealthplace.com/_next/static/chunks/b79b7286-5dcdad861d0ded19.js	http/1.1
ahealthplace.com/_next/static/chunks/b536a0f1-699a1e48ab8607db.js	http/1.1
ahealthplace.com/_next/static/chunks/3549-f0598b5e0686b8ba.js	http/1.1
ahealthplace.com/_next/static/chunks/8631-2c430a50f51a45c1.js	http/1.1
ahealthplace.com/_next/static/chunks/5191-45f35f2ca8c0fe10.js	http/1.1
ahealthplace.com/_next/static/chunks/6492-0e779c8c7d5bc7fd.js	http/1.1
ahealthplace.com/_next/static/chunks/5339-a4e76f0a18cf5cbc.js	http/1.1
ahealthplace.com/_next/static/chunks/9645-1138524e2e434c10.js	http/1.1
ahealthplace.com/_next/static/chunks/9826-b41c180068e65127.js	http/1.1
ahealthplace.com/_next/static/chunks/9761-58eebb954d60c6b6.js	http/1.1
ahealthplace.com/_next/static/chunks/7138-6f9cb1b3ea1f3400.js	http/1.1
ahealthplace.com/_next/static/chunks/4008-0d132d371f315c28.js	http/1.1
ahealthplace.com/_next/static/chunks/8714-cc85e78208f0561a.js	http/1.1
ahealthplace.com/_next/static/chunks/1902-f7225ab14398d178.js	http/1.1
ahealthplace.com/_next/static/chunks/app/page-8fe249b6ef84f8a4.js	http/1.1
ahealthplace.com/images/Logo-web.png	http/1.1
ahealthplace.com/_next/static/chunks/3518-3f526b488f6ccebf.js	http/1.1
ahealthplace.com/_next/static/chunks/app/quizzes/page-becdcbfcdf144941.js	http/1.1
ahealthplace.com/images/footer.png	http/1.1
ahealthplace.com/api/visitors/ping	http/1.1
ahealthplace.com/api/auth/frontend/session	http/1.1
ahealthplace.com/api/crm/push/active	http/1.1
ahealthplace.com/api/posts?limit=4	http/1.1
ahealthplace.com/api/magazine?limit=4	http/1.1
ahealthplace.com/api/quizzes/types	http/1.1
ahealthplace.com/api/header	http/1.1
ahealthplace.com/api/navigation/main	http/1.1
ahealthplace.com/api/footer	http/1.1
ahealthplace.com/api/navigation/footer	http/1.1
ahealthplace.com/login?callbackUrl=/quizzes&_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/login?_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/blogs?_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/publication?_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/api/media/view?key=site-AHP/1785922878791-4ovdoim.webp	http/1.1
ahealthplace.com/api/media/view?key=site-AHP/1785840000616-ytvkidb.webp	http/1.1
ahealthplace.com/favicon.ico	http/1.1
ahealthplace.com/recipes?_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/?_rsc=AAKPyoLZ-bRixpIB	http/1.1
ahealthplace.com/quizzes?_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/login?callbackUrl=/quizzes&_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/recipes?_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/login?_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/blogs?_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/publication?_rsc=YHxzuvVZXsYCf_bJ	http/1.1
ahealthplace.com/?_rsc=YHxzuvVZXsYCf_bJ	http/1.1

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
ahealthplace.com/_next/static/css/9fefcb6f85f3184c.css	41.9 KiB	172 ms
ahealthplace.com/_next/static/css/50074081284c2ad0.css	1.5 KiB	52 ms

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
ahealthplace.com/api/media/view?key=site-AHP/1785922878791-4ovdoim.webp	604800.0 s	12.4 KiB
ahealthplace.com/api/media/view?key=site-AHP/1785840000616-ytvkidb.webp	604800.0 s	12.4 KiB

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

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 321.0 KiB

URL	Transfer Size	Est Savings
ahealthplace.com/_next/static/chunks/bd904a5c-8373896e8b4dba99.js	97.5 KiB	88.7 KiB
ahealthplace.com/_next/static/chunks/8058-09f30a0c2c75940c.js	139.4 KiB	85.4 KiB
ahealthplace.com/_next/static/chunks/b536a0f1-699a1e48ab8607db.js	83.8 KiB	44.7 KiB
ahealthplace.com/_next/static/chunks/b79b7286-5dcdad861d0ded19.js	44.9 KiB	40.7 KiB
ahealthplace.com/_next/static/chunks/5339-a4e76f0a18cf5cbc.js	39.6 KiB	35.2 KiB
ahealthplace.com/_next/static/chunks/9645-1138524e2e434c10.js	28.6 KiB	26.3 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
About Us `div.footer-grid > div.footer-brand > a.logo-link-footer > img.logo-img`	ahealthplace.com/api/media/view?key=site-AHP/1785840000616-ytvkidb.webp

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

●Time to Interactive 1.4 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 2 long tasks found

●Network Requests

●Network Round Trip Times 120 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 5 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
div.flex-1 > div.flex > div.relative > button.relative `div.flex-1 > div.flex > div.relative > button.relative`
header.fixed > div.fixed > div.flex > button.p-1 `header.fixed > div.fixed > div.flex > button.p-1`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search... `div.flex-1 > div.flex > button.flex > span.hidden`
EXCLUSIVE MEMBER BENEFITS `div.container > div.grid > div.text-left > span.text-[#0f7c85]`

These are opportunities to improve the legibility of your content.

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
Interactive Health Checks `div.space-y-4 > div.flex > div > h4.font-heading`

These are opportunities to improve keyboard navigation in your application.

○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

●Form elements have associated labels

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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
ahealthplace.com/favicon.ico	`Failed to load resource: the server responded with a status of 404 (Not Found)`

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`