B — https://www.anthropic.com

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

'unsafe-inline' found in script source

Security › Content Security Policy

7 link(s) with no accessible text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

External script from cdn.intellimize.co lacks integrity attribute

Security › Subresource Integrity

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.anthropic.com)](https://beavercheck.com/results/fc14a9ff-08e8-d995-d6d0-a354d4dba45a)

HTML

<a href="https://beavercheck.com/results/fc14a9ff-08e8-d995-d6d0-a354d4dba45a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.anthropic.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

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.

6.33 s

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

7.96 s

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

14 ms

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

0.000

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

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

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

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

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

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

Request	Cache TTL	Transfer Size
/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...	84600.0 s	135.1 KiB
cdn.prod.website-files.com/gsap/3.14.2/gsap.min.js	0.0 ms	29.1 KiB
cdn.prod.website-files.com/gsap/3.14.2/ScrollTrigger.min.js	0.0 ms	18.2 KiB
www.anthropic.com/scripts/webflow-privacy-banner.js	14400.0 s	7.0 KiB
cdn.prod.website-files.com/gsap/3.14.2/SplitText.min.js	0.0 ms	4.0 KiB
cdn.prod.website-files.com/gsap/3.14.2/TextPlugin.min.js	0.0 ms	3.9 KiB
www.anthropic.com/scripts/webflow-custom-tracking.js	14400.0 s	5.3 KiB

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.

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:12.105 source:map[column:26391 line:1 type:source-location url:https://cdn.prod.website-files.com/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.f2efb3c5440a81cf.js urlProvider:network]]]

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

items: [map[reflowTime:51.702 source:map[column:254661 line:3 type:source-location url:https://cdn.intellimize.co/snippet/117895469.js urlProvider:network]] map[reflowTime:12.105 source:map[column:107581 line:0 type:source-location url:https://cdn.prod.website-files.com/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.9ebbe4e3f7d60657.js urlProvider:network]] map[reflowTime:1.441 source:map[column:13690 line:9 type:source-location url:https://cdn.prod.website-files.com/gsap/3.14.2/ScrollTrigger.min.js urlProvider:network]] map[reflowTime:8.836 source:map[type:text value:[unattributed]]] map[reflowTime:0.079 source:map[column:87016 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:1.119 source:map[column:52520 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:0.251 source:map[column:52578 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:0.239 source:map[column:52642 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:5.563 source:map[column:51866 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:1.483 source:map[column:51844 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:0.848 source:map[column:53473 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:0.789 source:map[column:81423 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]] map[reflowTime:0.076 source:map[column:85979 line:1 type:source-location url:https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b733f8a52 urlProvider:network]]]

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

	URL	Resource Size	Est Savings
div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image `div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image`	/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...	134.6 KiB	93.1 KiB

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.

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

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.

URL	Transfer Size	Duration
www.anthropic.com/scripts/webflow-custom-tracking.js	5.3 KiB	300 ms
www.anthropic.com/scripts/webflow-privacy-banner.js	7.0 KiB	450 ms
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.9ebbe4e3f7d...	84.3 KiB	4.0 s
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.f2efb3c5440...	89.3 KiB	4.2 s
/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b7...	30.9 KiB	2.5 s
/67ce28cfec624e2b733f8a52/css/ant-brand.shared.1edf03cd8....	36.8 KiB	2.0 s
cdn.prod.website-files.com/gsap/3.14.2/ScrollTrigger.min.js	18.2 KiB	1.4 s
cdn.prod.website-files.com/gsap/3.14.2/SplitText.min.js	4.0 KiB	951 ms
cdn.prod.website-files.com/gsap/3.14.2/TextPlugin.min.js	3.9 KiB	951 ms
hubspotonwebflow.com/assets/js/form-124.js	2.6 KiB	799 ms
cdn.prod.website-files.com/gsap/3.14.2/gsap.min.js	29.1 KiB	2.3 s
/67ce28cfec624e2b733f8a52/js/ant-brand.a2ef681e.469cb5551...	1.5 KiB	780 ms

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

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.

TTI

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 170 ms 5.6 KiB

URL	Transfer Size	Est Savings
www.anthropic.com/scripts/webflow-privacy-banner.js	6.8 KiB	3.3 KiB
www.anthropic.com/scripts/webflow-custom-tracking.js	5.2 KiB	2.3 KiB

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

Estimated savings: 0.0 ms 30.3 KiB

URL	Transfer Size	Est Savings
/67ce28cfec624e2b733f8a52/css/ant-brand.shared.1edf03cd8....	36.3 KiB	30.3 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.

Estimated savings: 1.0 s 149.6 KiB

URL	Transfer Size	Est Savings
cdn.intellimize.co/snippet/117895469.js	85.1 KiB	54.4 KiB
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.f2efb3c5440...	88.8 KiB	53.7 KiB
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.9ebbe4e3f7d...	83.8 KiB	41.5 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

Category	Time Spent
Script Evaluation	913 ms
Other	561 ms
Style & Layout	539 ms
Script Parsing & Compilation	160 ms
Rendering	86 ms
Parse HTML & CSS	49 ms

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

	URL
div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image `div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image`	/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 962 KiB

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 9 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 170 ms

●Server Backend Latencies 200 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 80 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid large layout shifts

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.

Failing Elements
Accept `dialog#consent-container > div#consent-banner > div#simple-options > button#accept-btn`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
div#w-node-_1f7589da-b35f-83df-c217-2c60daf900d4-b8ec2927 > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap `div#w-node-_1f7589da-b35f-83df-c217-2c60daf900d4-b8ec2927 > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap`

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.

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

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

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

●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

●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

○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

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

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.

Content Best Practices

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

Link destination	Link Text
www.anthropic.com/legal/cookies	here

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

100

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.

1.62 s

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

2.35 s

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

0 ms

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

0.000

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

1.62 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.35 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.

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

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

Request	Cache TTL	Transfer Size
/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...	84600.0 s	279.6 KiB
cdn.prod.website-files.com/gsap/3.14.2/gsap.min.js	0.0 ms	29.1 KiB
cdn.prod.website-files.com/gsap/3.14.2/ScrollTrigger.min.js	0.0 ms	18.2 KiB
www.anthropic.com/scripts/webflow-privacy-banner.js	14400.0 s	8.3 KiB
www.anthropic.com/scripts/webflow-custom-tracking.js	14400.0 s	6.8 KiB
cdn.prod.website-files.com/gsap/3.14.2/SplitText.min.js	0.0 ms	4.0 KiB
cdn.prod.website-files.com/gsap/3.14.2/TextPlugin.min.js	0.0 ms	3.9 KiB

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

items: [map[reflowTime:29.596 source:map[type:text value:[unattributed]]] map[reflowTime:1.1 source:map[column:255920 line:3 type:source-location url:https://cdn.intellimize.co/snippet/117895469.js urlProvider:network]]]

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

	URL	Resource Size	Est Savings
div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image `div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image`	/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...	279.1 KiB	248.7 KiB

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

lhId: page-0-IMG

nodeLabel: div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image

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

selector: div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image

snippet: <img src="https://cdn.prod.website-files.com/67ce28cfec624e2b733f8a52/69d537c96b8953…" loading="lazy" sizes="(max-width: 1467px) 100vw, 1467px" srcset="https://cdn.prod.website-files.com/67ce28cfec624e2b733f8a52/69d537c96b8953…" alt="" class="duraldar-cta-asset-image" style="translate: none; rotate: none; scale: none; transform: translate(0px, 0%);">

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.

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.

URL	Transfer Size	Duration
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.9ebbe4e3f7d...	84.3 KiB	837 ms
/67ce28cfec624e2b733f8a52/js/ant-brand.a2ef681e.469cb5551...	1.5 KiB	271 ms
/js/jquery-3.5.1.min.dc5e7f18c8.js?site=67ce28cfec624e2b7...	30.9 KiB	522 ms
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.f2efb3c5440...	89.3 KiB	837 ms
cdn.prod.website-files.com/gsap/3.14.2/SplitText.min.js	4.0 KiB	271 ms
cdn.prod.website-files.com/gsap/3.14.2/ScrollTrigger.min.js	18.2 KiB	328 ms
cdn.prod.website-files.com/gsap/3.14.2/gsap.min.js	29.1 KiB	522 ms
cdn.prod.website-files.com/gsap/3.14.2/TextPlugin.min.js	3.9 KiB	271 ms
/67ce28cfec624e2b733f8a52/css/ant-brand.shared.1edf03cd8....	36.9 KiB	534 ms
hubspotonwebflow.com/assets/js/form-124.js	2.6 KiB	243 ms

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

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.

Estimated savings: 0.0 ms 30.0 KiB

URL	Transfer Size	Est Savings
/67ce28cfec624e2b733f8a52/css/ant-brand.shared.1edf03cd8....	36.3 KiB	30.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.

Estimated savings: 330 ms 149.7 KiB

URL	Transfer Size	Est Savings
cdn.intellimize.co/snippet/117895469.js	85.1 KiB	54.4 KiB
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.f2efb3c5440...	88.8 KiB	53.7 KiB
/67ce28cfec624e2b733f8a52/js/ant-brand.schunk.9ebbe4e3f7d...	83.8 KiB	41.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 5.6 KiB

URL	Transfer Size	Est Savings
www.anthropic.com/scripts/webflow-privacy-banner.js	6.7 KiB	3.3 KiB
www.anthropic.com/scripts/webflow-custom-tracking.js	5.2 KiB	2.3 KiB

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

	URL
div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image `div.duraldar-cta_scroll-bg > div.duraldar-cta_container > div.duraldar-cta-asset_wrap > img.duraldar-cta-asset-image`	/67ce28cfec624e2b733f8a52/69d537c96b8953d88ab6bdaf_durand...

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

●Time to Interactive 2.3 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

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

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.8 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 220 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 80 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Contrast

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

Failing Elements
Accept all cookies `dialog#consent-container > div#consent-banner > div#simple-options > button#accept-btn`
all cookies `div#consent-banner > div#simple-options > button#accept-btn > span`

These are opportunities to improve the legibility of your content.

Names and labels

Failing Elements
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link `ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link`
div.footer_bottom_contain > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap `div.footer_bottom_contain > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap`

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.

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

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

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

●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

●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

○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

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

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

Content Best Practices

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

Link destination	Link Text
www.anthropic.com/legal/cookies	here

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`

Browse & Analyze

Learn

Results for https://www.anthropic.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts