C — https://nist.gov | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

Drupal sites average 75

At average

Better than 45% of Drupal sites See full Drupal benchmark →

Framework sites average 74

At average

Better than 60% of Framework sites

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

Page weighs 9.1 MB (6.5 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

1 button(s) with no accessible text

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

Accessibility › Link & Button Quality

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%2Fnist.gov)](https://beavercheck.com/results/e393a97a-12df-471f-9507-dbd7f9f02896)

HTML

<a href="https://beavercheck.com/results/e393a97a-12df-471f-9507-dbd7f9f02896"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnist.gov" alt="BeaverCheck Score"></a>

Image URL

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

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.2s 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.

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

1 accessibility issue excludes users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

6 warning

6 barrier(s) likely increasing bounce by ~19%.

Speed (2)

Page loads in 3.2s

+5% bounce

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

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

High main-thread blocking time

+2% bounce

Page is non-interactive for 298ms after first paint

Fix: Defer third-party scripts and split large bundles

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 (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

€425 investment → €1,019/month returns + EUR 500,000 risk avoided

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

Investment

€425

5h · 5 findings

Monthly returns

€1,019 /mo

~€12,226 / year

Conversions recovered €1,017
Bandwidth savings €1.52

Regulatory risk avoided

EUR 500,000

if kept compliant

EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — 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

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€128 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

€41,668 / month at risk

~€500,018 / year if left unfixed

Compliance Risk

€500,000

EAA

No <main> landmark found
EAA: EUR 1,000 – EUR 500,000
1 of 3 <nav> elements are unlabeled
EAA: EUR 1,000 – EUR 500,000
No H1 heading found
EAA: EUR 1,000 – EUR 500,000

Bandwidth Waste

€1.52 /mo

20549.2 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~2.1 MB per page load
Saves €1.52/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 5 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

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.

2.36 s

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

3.16 s

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

298 ms

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

0.001

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

4.68 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.84 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
/embed/sdk-iframe-integration.fla9.latest.js	180.0 s	343.1 KiB
/sites/default/files/styles/1152_x_768/public/images/2026...	60.0 s	126.6 KiB
/sites/default/files/styles/homepage_hero_small/public/im...	60.0 s	18.0 KiB
www.nist.gov/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?	14400.0 s	14.2 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
time.gov/web/css/main.css	0.0 ms	1.5 KiB
www.nist.gov/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	2858.0 s	775 B
/84921ef26d48015ab5328c0fcb8c49b7/thumbnails/thumbnail.jp...	864000.0 s	2.8 KiB

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
/libraries/nist-component-library/dist/fonts/source-sans-...	140 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	130 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	125 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	120 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-DIV

nodeLabel: div#block-nist-www-content > section.nist-page__content > div.homepage-hero > div.homepage-hero__fallback-mobile

path: 1,HTML,1,BODY,2,DIV,5,DIV,0,SECTION,1,DIV,0,DIV

selector: div#block-nist-www-content > section.nist-page__content > div.homepage-hero > div.homepage-hero__fallback-mobile

snippet: <div class="homepage-hero__fallback-mobile" style="background-image: url("https://www.nist.gov/sites/default/files/styles/home…");">

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

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
/sites/default/files/css/css_BEbKB4LxuujEPFpD1AfEAFFgDOp9...	75.9 KiB	452 ms
/sites/default/files/js/js_5WbAeKWaHF5M7ZGOm0J4MoiuVLINg4...	431 B
/sites/default/files/js/js_agndrownnWbPAxUFhN_wUh92DTsakn...	409 B
www.nist.gov/modules/contrib/google_tag/js/gtm.js?tdl75h	643 B
/sites/default/files/css/css_ssZ349pFYQBYitUuNabAF3FOqSxl...	8.1 KiB
www.nist.gov/modules/contrib/google_tag/js/gtag.js?tdl75h	836 B
/sites/default/files/css/css_ykRiQh7fbub2hQuiIONx4rSV6slt...	5.6 KiB

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
Two male researchers in casual clothes and protective eyewear stand in the lab,… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/1152_x_768/public/images/2026...	271.1 KiB	223.1 KiB
Actor Ryan Gosling standing in front of a Project Hail Mary movie promotional p… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/1152_x_768/public/images/2026...	139.5 KiB	93.0 KiB
Wide shot shows two researchers on either side of a scientific device made of m… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/1152_x_768/public/images/2026...	135.2 KiB	90.1 KiB
Susana Deustua looks at a large, red telescope located in a dark room. `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/1152_x_768/public/images/2026...	125.1 KiB	83.4 KiB
Circular multicolored graphic showing the symbols for the SI base units and the… `div.circle-teaser__image > div.entity-reference > a > img`	/sites/default/files/styles/140_x_140_crop/public/images/...	23.8 KiB	21.3 KiB
CHIPS for America Investments in innovation, resilience and a more competitive … `div.dialog-off-canvas-main-canvas > div#block-nist-www-content > section.nist-page__content > div.chips-banner`	www.nist.gov/themes/custom/nist_www/img/homepage/circuit_pattern_tile.png	20.7 KiB	6.1 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: 881 ms

URL	Time Spent
nist.gov/	881 ms
www.nist.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

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: 460 ms 73.0 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_BEbKB4LxuujEPFpD1AfEAFFgDOp9...	75.8 KiB	73.0 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: 460 ms 259.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-HEQ0YF2VYL&cx=c&gtm=4e64f0	156.0 KiB	67.7 KiB
/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn...	99.1 KiB	66.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-54VSXXDF	117.1 KiB	63.0 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e64f0	147.1 KiB	62.3 KiB

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	972 ms
Other	932 ms
Style & Layout	491 ms
Rendering	187 ms
Script Parsing & Compilation	164 ms
Parse HTML & CSS	72 ms
Garbage Collection	27 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_4.mp4?p=e...	733.7 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_8.mp4?p=e...	656.9 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_7.mp4?p=e...	656.7 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_5.mp4?p=e...	638.6 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_9.mp4?p=e...	604.4 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_6.mp4?p=e...	573.4 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_3.mp4?p=e...	420.5 KiB
/embed/sdk-iframe-integration.fla9.latest.js	343.1 KiB
/sites/default/files/styles/1152_x_768/public/images/2026...	271.5 KiB
/84921ef26d48015ab5328c0fcb8c49b7/video/480/seg_2.mp4?p=e...	270.7 KiB

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

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 10 user timings

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 7 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 620 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

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

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
See NIST News `div.bg-base-lightest > div.grid-container > div.nist-page-segment > a.usa-button`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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

●Buttons have an accessible name

●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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

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

○Elements with visible text labels have matching accessible names.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

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

Content Best Practices

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 destination	Link Text
www.nist.gov/chips	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

●Document has a meta description

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

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.

947 ms

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

1.79 s

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

15 ms

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

0.026

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

1.77 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.87 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
time.gov/web/fonts/source-sans-pro/sourcesanspro-regular-webfont.woff2	275 ms
time.gov/web/fonts/source-sans-pro/sourcesanspro-bold-webfont.woff2	275 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	145 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	135 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	130 ms
/libraries/nist-component-library/dist/fonts/source-sans-...	125 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:7.458 source:map[column:156 line:12 type:source-location url:https://www.nist.gov/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn_In3NULJj1M6Y.js?scope=footer&delta=0&language=en&theme=nist_www&include=eJxljmEOgzAIhS_UyZEItVg7aTFtTT3-OnWJ2_4AHzzg0VYVKY2z5gJ0A2NpXLBz1RVuNT6L4b1KSAu4vK0kw4XGq3phrOTB9_DLAz1p_25Gk0Kp4EUtyaNfPnBmcpw_iFPoeqctiZLDmruXkPo2neOVPOPE7N4m4b91qurMsX9VFUsZozpwoZDtlw_rh6a1drPS2E6aI1x5cIFE_QuuxnZ3 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:19.511 source:map[type:text value:[unattributed]]] map[reflowTime:5.932 source:map[column:84992 line:2 type:source-location url:https://www.nist.gov/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn_In3NULJj1M6Y.js?scope=footer&delta=0&language=en&theme=nist_www&include=eJxljmEOgzAIhS_UyZEItVg7aTFtTT3-OnWJ2_4AHzzg0VYVKY2z5gJ0A2NpXLBz1RVuNT6L4b1KSAu4vK0kw4XGq3phrOTB9_DLAz1p_25Gk0Kp4EUtyaNfPnBmcpw_iFPoeqctiZLDmruXkPo2neOVPOPE7N4m4b91qurMsX9VFUsZozpwoZDtlw_rh6a1drPS2E6aI1x5cIFE_QuuxnZ3 urlProvider:network]] map[reflowTime:0.315 source:map[column:50335 line:2 type:source-location url:https://www.nist.gov/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn_In3NULJj1M6Y.js?scope=footer&delta=0&language=en&theme=nist_www&include=eJxljmEOgzAIhS_UyZEItVg7aTFtTT3-OnWJ2_4AHzzg0VYVKY2z5gJ0A2NpXLBz1RVuNT6L4b1KSAu4vK0kw4XGq3phrOTB9_DLAz1p_25Gk0Kp4EUtyaNfPnBmcpw_iFPoeqctiZLDmruXkPo2neOVPOPE7N4m4b91qurMsX9VFUsZozpwoZDtlw_rh6a1drPS2E6aI1x5cIFE_QuuxnZ3 urlProvider:network]] map[reflowTime:0.208 source:map[column:50393 line:2 type:source-location url:https://www.nist.gov/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn_In3NULJj1M6Y.js?scope=footer&delta=0&language=en&theme=nist_www&include=eJxljmEOgzAIhS_UyZEItVg7aTFtTT3-OnWJ2_4AHzzg0VYVKY2z5gJ0A2NpXLBz1RVuNT6L4b1KSAu4vK0kw4XGq3phrOTB9_DLAz1p_25Gk0Kp4EUtyaNfPnBmcpw_iFPoeqctiZLDmruXkPo2neOVPOPE7N4m4b91qurMsX9VFUsZozpwoZDtlw_rh6a1drPS2E6aI1x5cIFE_QuuxnZ3 urlProvider:network]] map[reflowTime:1.003 source:map[column:50457 line:2 type:source-location url:https://www.nist.gov/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn_In3NULJj1M6Y.js?scope=footer&delta=0&language=en&theme=nist_www&include=eJxljmEOgzAIhS_UyZEItVg7aTFtTT3-OnWJ2_4AHzzg0VYVKY2z5gJ0A2NpXLBz1RVuNT6L4b1KSAu4vK0kw4XGq3phrOTB9_DLAz1p_25Gk0Kp4EUtyaNfPnBmcpw_iFPoeqctiZLDmruXkPo2neOVPOPE7N4m4b91qurMsX9VFUsZozpwoZDtlw_rh6a1drPS2E6aI1x5cIFE_QuuxnZ3 urlProvider:network]]]

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-DIV

nodeLabel: div#block-nist-www-content > section.nist-page__content > div.homepage-hero > div.homepage-hero__fallback-desktop

path: 1,HTML,1,BODY,2,DIV,5,DIV,0,SECTION,1,DIV,1,DIV

selector: div#block-nist-www-content > section.nist-page__content > div.homepage-hero > div.homepage-hero__fallback-desktop

snippet: <div class="homepage-hero__fallback-desktop" style="background-image: url("https://www.nist.gov/sites/default/files/styles/home…");">

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

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

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
/sites/default/files/css/css_BEbKB4LxuujEPFpD1AfEAFFgDOp9...	75.9 KiB	80 ms
/sites/default/files/js/js_5WbAeKWaHF5M7ZGOm0J4MoiuVLINg4...	431 B
www.nist.gov/modules/contrib/google_tag/js/gtm.js?tdl75h	638 B
www.nist.gov/modules/contrib/google_tag/js/gtag.js?tdl75h	813 B
/sites/default/files/js/js_agndrownnWbPAxUFhN_wUh92DTsakn...	409 B
/sites/default/files/css/css_ykRiQh7fbub2hQuiIONx4rSV6slt...	5.6 KiB
/sites/default/files/css/css_ssZ349pFYQBYitUuNabAF3FOqSxl...	8.2 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
/embed/sdk-iframe-integration.fla9.latest.js	180.0 s	343.2 KiB
/sites/default/files/styles/280_x_184/public/images/2026/...	60.0 s	122.6 KiB
time.gov/web/fonts/source-sans-pro/sourcesanspro-regular-webfont.woff2	0.0 ms	20.5 KiB
time.gov/web/fonts/source-sans-pro/sourcesanspro-bold-webfont.woff2	0.0 ms	20.3 KiB
www.nist.gov/cdn-cgi/challenge-platform/h/g/scripts/jsd/b0a7532ac8ec/main.js?	14400.0 s	14.2 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
time.gov/web/css/main.css	0.0 ms	1.5 KiB
/84921ef26d48015ab5328c0fcb8c49b7/thumbnails/thumbnail.jp...	864000.0 s	12.4 KiB
www.nist.gov/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	2860.0 s	798 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
Photograph of the NIST Gaithersburg Campus `div.nist-in-your-inbox > div.nist-in-your-inbox__image > picture > img`	/themes/custom/nist_www/img/homepage/nist_gaithersburg_ca...	276.2 KiB	159.0 KiB
Two male researchers in casual clothes and protective eyewear stand in the lab,… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/280_x_184/public/images/2026/...	121.0 KiB	112.6 KiB
Wide shot shows two researchers on either side of a scientific device made of m… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/1152_x_768/public/images/2026...	135.2 KiB	101.4 KiB
Image of the NIST 1916 Time Capsule containing five Standard Reference Material… `div.circle-teaser__image > div.entity-reference > a > img`	/sites/default/files/styles/140_x_140_crop/public/images/...	100.8 KiB	100.0 KiB
Kelly Sauerwein poses sitting at a table in the NIST library, leaning forward a… `div.circle-teaser__image > div.entity-reference > a > img`	/sites/default/files/styles/140_x_140_crop/public/images/...	30.6 KiB	29.8 KiB
Susana Deustua looks at a large, red telescope located in a dark room. `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/280_x_184/public/images/2026/...	33.8 KiB	25.4 KiB
Circular multicolored graphic showing the symbols for the SI base units and the… `div.circle-teaser__image > div.entity-reference > a > img`	/sites/default/files/styles/140_x_140_crop/public/images/...	23.8 KiB	23.0 KiB
A postage stamp with a fingerprint on it is shown twice, once in black and whit… `div.circle-teaser__image > div.entity-reference > a > img`	/sites/default/files/styles/140_x_140_crop/public/images/...	22.7 KiB	21.9 KiB
Actor Ryan Gosling standing in front of a Project Hail Mary movie promotional p… `div.entity-reference > figure.nist-image > picture > img`	/sites/default/files/styles/280_x_384/public/images/2026/...	30.1 KiB	12.6 KiB
CHIPS for America Investments in innovation, resilience and a more competitive … `div.dialog-off-canvas-main-canvas > div#block-nist-www-content > section.nist-page__content > div.chips-banner`	www.nist.gov/themes/custom/nist_www/img/homepage/circuit_pattern_tile.png	20.7 KiB	6.1 KiB
	/84921ef26d48015ab5328c0fcb8c49b7/thumbnails/thumbnail.jp...	12.2 KiB	5.4 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
time.gov/web/	http/1.1
time.gov/web/css/main.css	http/1.1
time.gov/web/scripts/jquery-3.7.1.min.js	http/1.1
time.gov/web/scripts/dst-leap-dates.js	http/1.1
time.gov/web/scripts/fullscreen_clock.js	http/1.1
time.gov/web/fonts/source-sans-pro/sourcesanspro-regular-webfont.woff2	http/1.1
time.gov/web/fonts/source-sans-pro/sourcesanspro-bold-webfont.woff2	http/1.1
time.gov/web/auxdata.xml	http/1.1
time.gov/web/nist_use_only.cgi?disablecache=1776359731339	http/1.1

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: 327 ms

URL	Time Spent
nist.gov/	327 ms
www.nist.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: 110 ms 71.5 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_BEbKB4LxuujEPFpD1AfEAFFgDOp9...	75.8 KiB	71.5 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: 170 ms 259.4 KiB

URL	Transfer Size	Est Savings
/sites/default/files/js/js_2I-3XaXSiWCMKsbSi_iqn5nUWVLdDn...	99.1 KiB	66.8 KiB
www.googletagmanager.com/gtag/js?id=G-HEQ0YF2VYL&cx=c&gtm=4e64f0	156.0 KiB	66.0 KiB
www.googletagmanager.com/gtag/js?id=G-CSLL4ZEK4L&cx=c&gtm=4e64f0	147.1 KiB	63.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-54VSXXDF	117.1 KiB	63.0 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_4.mp4?p=...	2.5 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_9.mp4?p=...	2.3 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_5.mp4?p=...	2.3 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_8.mp4?p=...	2.3 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_6.mp4?p=...	2.1 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_7.mp4?p=...	2.0 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_3.mp4?p=...	1.6 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_2.mp4?p=...	1.0 MiB
/84921ef26d48015ab5328c0fcb8c49b7/video/1080/seg_1.mp4?p=...	393.1 KiB
/embed/sdk-iframe-integration.fla9.latest.js	343.2 KiB

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

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 10 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 2 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 440 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 5 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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

●Buttons have an accessible name

●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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

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

○Elements with visible text labels have matching accessible names.

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.nist.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●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

Content Best Practices

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 destination	Link Text
www.nist.gov/chips	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

●Document has a meta description

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

Results for https://nist.gov

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 (1)

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

Contrast

Best practices

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts