Skip to content
https://cms.gov

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

91

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.

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.

URLEst Savings
/themes/custom/cms_evo/dist/fonts/fontawesome-pro/webfont...185 ms
/themes/custom/cms_evo/dist/fonts/fontawesome-pro/webfont...185 ms
www.cms.gov/themes/custom/cms_evo/dist/fonts/lexend/Lexend-Bold.ttf180 ms
/themes/custom/cms_evo/dist/fonts/fontawesome-pro/webfont...170 ms
www.cms.gov/themes/custom/cms_evo/dist/fonts/public-sans/PublicSans-Bold.woff2165 ms
www.cms.gov/themes/custom/cms_evo/dist/fonts/lexend/Lexend-Regular.ttf75 ms
www.cms.gov/themes/custom/cms_evo/dist/fonts/lexend/Lexend-SemiBold.ttf75 ms
/themes/custom/cms_evo/dist/fonts/public-sans/PublicSans-...70 ms
/themes/custom/cms_evo/dist/fonts/public-sans/PublicSans-...35 ms

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.

URLResource SizeEst Savings
Two healthcare professionals div.ds-l-col--8 > article.align-center > div.field > img
/sites/default/files/styles/desktop_width/public/2022-12/...668.4 KiB650.5 KiB
a doctor and patient smiling div.ds-u-text-align--center > article.media > div.field > img
/sites/default/files/styles/max_width_tabs/public/2026-03...115.6 KiB99.5 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-1-IMG
nodeLabel: a doctor and patient smiling
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,MAIN,0,DIV,1,DIV,0,DIV,0,INNER,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,ARTICLE,0,DIV,0,IMG
selector: div.ds-u-text-align--center > article.media > div.field > img
snippet: <img loading="lazy" src="/sites/default/files/styles/max_width_tabs/public/2026-03/responsive-tabs-…" width="374" height="265" alt="a doctor and patient smiling">

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.

URLTransfer SizeDuration
tealium-tags.cms.gov/cms-www/prod/utag.sync.js1.0 KiB327 ms
/sites/default/files/css/css_F7_QeRQL13goAJtkrxFn_D-J4mmf...20.7 KiB
/sites/default/files/css/css_j-hR1427NSovf0242U7Bcqgccj-R...53.2 KiB81 ms
/sites/default/files/css/css__Wg7dfwqRmp1uip_kMqtDh4ogaNW...4.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.

RequestCache TTLTransfer Size
tealium-tags.cms.gov/cms-www/prod/utag.js1.0 s23.5 KiB
design.cms.gov/cdn/ds-cms-gov/12.4.3/web-components/bundle/base.js0.0 ms20.8 KiB
cdn1.adoberesources.net/alloy/2.6.4/alloy.min.js3600.0 s20.0 KiB
/Universal-Federated-Analytics-Min.js?agency=DHHS&subagen...0.0 ms9.4 KiB
/dxjsmodule/5.17c364950fcb67448399.chunk.js?Q_CLIENTVERSI...604800.0 s73.5 KiB
tags.tiqcdn.com/utag/cmsgov/cms-www/prod/utag.33.js?utv=ut4.48.202604151345300.0 s4.9 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js0.0 ms4.5 KiB
/WRSiteInterceptEngine/?Q_ZID=ZN_4GdYQQNAoifyULj&Q_LOC=ht...3600.0 s4.8 KiB
/WRSiteInterceptEngine/?Q_ZID=ZN_77ecFuJq2Tt2Srz&Q_LOC=ht...3600.0 s4.8 KiB
/dxjsmodule/17.5339c461e1518fcc3620.chunk.js?Q_CLIENTVERS...604800.0 s38.1 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...604800.0 s36.5 KiB
design.cms.gov/cdn/ds-cms-gov/12.4.3/web-components/bundle/ds-alert.js0.0 ms3.6 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...604800.0 s31.6 KiB
design.cms.gov/cdn/ds-cms-gov/12.4.3/web-components/bundle/ds-usa-banner.js0.0 ms2.5 KiB
/dxjsmodule/FeedbackButtonModule.js?Q_CLIENTVERSION=2.46....604800.0 s20.1 KiB
/dxjsmodule/37.7ea1ffe71ad8c0799cc1.chunk.js?Q_CLIENTVERS...604800.0 s19.2 KiB
tags.tiqcdn.com/utag/cmsgov/cms-www/prod/utag.21.js?utv=ut4.48.202504301455300.0 s1.4 KiB
tags.tiqcdn.com/utag/cmsgov/cms-www/prod/utag.24.js?utv=ut4.48.202504301455300.0 s1.2 KiB
tags.tiqcdn.com/utag/cmsgov/cms-www/prod/utag.10.js?utv=ut4.48.202504301455300.0 s1.2 KiB
tealium-tags.cms.gov/cms-www/prod/utag.sync.js1.0 s1.0 KiB
/dxjsmodule/1.bc67e778235741631577.chunk.js?Q_CLIENTVERSI...604800.0 s7.8 KiB
/utag/tiqapp/utag.v.js?a=cmsgov/cms-www/202604151345&cb=1...300.0 s430 B
/dxjsmodule/7.f7df015b06d8a90ce822.chunk.js?Q_CLIENTVERSI...604800.0 s2.0 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: 278 ms
URLTime Spent
cms.gov/278 ms
www.cms.gov/0.0 ms

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

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: 80 ms 171.2 KiB
URLTransfer SizeEst Savings
html { line-height: 1.15; text-size-adjust: 100%; } …75.1 KiB74.9 KiB
/sites/default/files/css/css_j-hR1427NSovf0242U7Bcqgccj-R...52.7 KiB47.3 KiB
::backdrop, ::after, ::before, :root { --blue-light-bg: #e0eaf8; --button-primary-bg--hover: #122e5…33.5 KiB33.5 KiB
/sites/default/files/css/css_F7_QeRQL13goAJtkrxFn_D-J4mmf...20.1 KiB15.6 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 10.6 KiB
URLTransfer SizeEst Savings
html { line-height: 1.15; text-size-adjust: 100%; } …75.1 KiB7.7 KiB
::backdrop, ::after, ::before, :root { --blue-light-bg: #e0eaf8; --button-primary-bg--hover: #122e5…33.5 KiB2.9 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 172.4 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L147.0 KiB60.2 KiB
/dxjsmodule/5.17c364950fcb67448399.chunk.js?Q_CLIENTVERSI...72.8 KiB56.1 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...35.7 KiB35.2 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...30.8 KiB20.8 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
CMS.gov div#block-cms-evo-sitebranding > div.site-logo > a > img
www.cms.gov/themes/custom/cms_evo/logo.svg
CMS.gov div.ds-u-display--flex > div.footer-logos > a.footer-cms-logo > img
www.cms.gov/themes/custom/cms_evo/logo.svg

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,132 KiB
●User Timing marks and measures 9 user timings
●JavaScript execution time 0.4 s
●Minimizes main-thread work 0.9 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 240 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○Avoid non-composited animations
100

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.

○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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○`<frame>` or `<iframe>` elements have a title
○`<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
○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.
○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
●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
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

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.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.cms.gov/priorities/rural-health-transformation-rht-program/overviewLearn more
www.cms.gov/priorities/health-technology-ecosystem/overviewLearn more
www.cms.gov/fraudLearn more
/priorities/medicare-prescription-drug-affordability/over...Learn more
www.cms.gov/medicaid-chip/community-engagement-support/eligibility-made-easyLearn more
/about-cms/web-policies-important-links/accessibility-non...Learn more

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 are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback