C — https://code.org | BeaverCheck Audit

Site Health

Score: 75 / 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.

Strong compliance posture across regulations.

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

Amazon Route 53 · 836 peers

You 75

Avg 72

At average

0 50 100

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

Facebook · 1153 peers

You 75

Avg 72

At average

0 50 100

Better than 72% of Facebook sites See full Facebook benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Cookie 'language_' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

103 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

28 third-party resources (46% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fcode.org)](https://beavercheck.com/results/74ed30f4-ce92-4f0d-b7d9-412c4803ce41)

HTML

<a href="https://beavercheck.com/results/74ed30f4-ce92-4f0d-b7d9-412c4803ce41"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcode.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fcode.org

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 6.4s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute 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 6.4s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 3 warning

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

Speed (2)

Page takes 6.4s to load

+12% bounce

Users abandon at ~3s — you're 3.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.5s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Return on Investment

$550 investment → $4,597/month returns + USD 150,000 risk avoided

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

Investment

$550

6h · 5 findings

Monthly returns

$4,597 /mo

~$55,168 / year

Conversions recovered $4,597
Bandwidth savings $0.42

Regulatory risk avoided

USD 150,000

if kept compliant

ADA Title III USD 150,000

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,500 / month at risk

~$150,005 / year if left unfixed

Compliance Risk

$150,000

ADA Title III

Skip navigation link is missing (WCAG 2.4.1)
ADA Title III: USD 25,000 – USD 150,000
Multiple H1 headings (13 found)
ADA Title III: USD 25,000 – USD 150,000
Heading level skipped: H2 → H5 (missing H3)
ADA Title III: USD 25,000 – USD 150,000

+2 more

Bandwidth Waste

$0.42 /mo

5255.8 MB/mo × 0.080 USD/GB

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

100

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

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

6.42 s

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

1.46 s

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

0.305

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

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

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

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.304937] map[node:map[boundingRect:map[bottom:7408 height:6716 left:0 right:412 top:692 width:412] lhId:page-1-DIV nodeLabel:WHO WE ARE We are the experts in preparing students for an AI-driven world. C… path:1,HTML,1,BODY,7,MAIN,2,DIV selector:body > main > div.cf-69444be9a7e4f01e0cabcf50af08d6e9 snippet:<div style="display:flex" class="cf-69444be9a7e4f01e0cabcf50af08d6e9 contentful-container" data-test-id="contentful-container"> type:node] score:0.283582] map[node:map[boundingRect:map[bottom:692 height:268 left:0 right:412 top:424 width:412] lhId:page-6-::after nodeLabel:div.cf-5c1c11cc9d6348b9402354ba1afa6063 > div.cf-92267537f53a65bb63c5bb229c0cd918 > div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > ::after path:1,HTML,1,BODY,7,MAIN,1,DIV,0,DIV,1,DIV,0,::after selector:div.cf-5c1c11cc9d6348b9402354ba1afa6063 > div.cf-92267537f53a65bb63c5bb229c0cd918 > div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > ::after snippet:<::after> type:node] score:0.021355]]

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
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	65 ms
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	40 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:46.597 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: AI is reshaping the world Education must lead what comes next AI is transformi…

path: 1,HTML,1,BODY,7,MAIN,1,DIV

selector: body > main > div.cf-5c1c11cc9d6348b9402354ba1afa6063

snippet: <div style="display:flex" class="cf-5c1c11cc9d6348b9402354ba1afa6063 contentful-container" data-test-id="contentful-container">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
code.org/_next/static/css/fc9bd2059a10c6bf.css	4.8 KiB
code.org/_next/static/css/a07c7ae1d7733746.css	2.2 KiB
code.org/_next/static/css/ccdbab6f669c4427.css	6.6 KiB
code.org/_next/static/css/5d3778b73b07efeb.css	4.8 KiB	150 ms
code.org/_next/static/css/cd681a87f39631fa.css	4.7 KiB
code.org/_next/static/css/6cad3d0b054b25aa.css	2.9 KiB	150 ms
code.org/_next/static/css/428ae77ce7d5f063.css	2.4 KiB
code.org/_next/static/css/3649fad98a5c4288.css	3.3 KiB
code.org/_next/static/css/98e7c9d886edde2d.css	2.2 KiB
code.org/_next/static/css/1ca261cdc7d789e1.css	8.5 KiB	150 ms
code.org/_next/static/css/54ab74348ea3e55f.css	8.5 KiB
code.org/_next/static/css/bee4ec13ee316a5e.css	2.9 KiB
code.org/_next/static/css/39446bf7eb31383c.css	934 B	150 ms
code.org/_next/static/css/4f32e6447ded6c32.css	5.2 KiB	150 ms
code.org/_next/static/css/94fa8b0ad645af3b.css	1.9 KiB
code.org/_next/static/css/a05adaee2ff82ff8.css	4.3 KiB
code.org/_next/static/css/7f5925cac80368ee.css	1.7 KiB
code.org/_next/static/css/6e1eefb1dec4ec64.css	4.5 KiB
code.org/_next/static/css/a479fafba9d943bd.css	4.8 KiB
code.org/_next/static/css/f6c2429bc3b51ee0.css	5.5 KiB	150 ms
code.org/_next/static/css/fd9143fa9538c881.css	8.6 KiB	150 ms
code.org/_next/static/css/28d87e222cb9076d.css	4.7 KiB
code.org/_next/static/css/a8091194558206ff.css	2.6 KiB	150 ms
code.org/_next/static/css/4bba0c0c0877b0da.css	1.6 KiB
code.org/_next/static/css/3fb483857a8c9bc6.css	840 B
code.org/_next/static/css/0f0cc336d30f5fb2.css	2.4 KiB
code.org/_next/static/css/b62f7b4ad22470af.css	2.1 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
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	604800.0 s	253.8 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	604800.0 s	138.7 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	604800.0 s	99.4 KiB
global.localizecdn.com/localize.js	259200.0 s	27.1 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	604800.0 s	15.3 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/custom-icons.min.css	604800.0 s	2.6 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/duotone.min.css	604800.0 s	1.9 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/regular.min.css	604800.0 s	1.2 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/solid.min.css	604800.0 s	1.2 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
div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > div.cf-d442defc83cbe049355e312f4bc523d4 > figure.image--hasRoundedCorners > img.mui-t3ax9v `div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > div.cf-d442defc83cbe049355e312f4bc523d4 > figure.image--hasRoundedCorners > img.mui-t3ax9v`	/_next/image?url=https%3A%2F%2Fcontentful-images.code.org...	59.3 KiB	48.1 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
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/solid.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/regular.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/duotone.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/custom-icons.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	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: 830 ms

URL	Time Spent
code.org/	830 ms
code.org/en-US	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
WHO WE ARE We are the experts in preparing students for an AI-driven world. C… `body > main > div.cf-69444be9a7e4f01e0cabcf50af08d6e9`	0.284
div.cf-5c1c11cc9d6348b9402354ba1afa6063 > div.cf-92267537f53a65bb63c5bb229c0cd918 > div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > ::after `div.cf-5c1c11cc9d6348b9402354ba1afa6063 > div.cf-92267537f53a65bb63c5bb229c0cd918 > div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > ::after`	0.021

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.

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 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: 660 ms 160.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-L9HT5MZ3HD	178.1 KiB	67.7 KiB
code.org/_next/static/chunks/326-7f1023f63cd41f9f.js	67.7 KiB	34.9 KiB
code.org/_next/static/chunks/5670-318ba52a6b4cab24.js	57.5 KiB	34.2 KiB
/_next/static/chunks/app/[brand]/[locale]/[[...paths]]/pa...	65.2 KiB	23.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
code.org/_next/static/chunks/1902-09bbc0137809353d.js	1.8 s	1.7 s	12 ms
code.org/en-US	845 ms	16 ms	87 ms
Unattributable	485 ms	15 ms	0.0 ms
code.org/_next/static/chunks/4445.c2d7ef35f9eae3f6.js	413 ms	282 ms	5.0 ms
www.googletagmanager.com/gtag/js?id=G-L9HT5MZ3HD	322 ms	275 ms	39 ms
code.org/_next/static/chunks/webpack-7a387c03fc9bc55e.js	228 ms	226 ms	1.5 ms
code.org/_next/static/chunks/326-7f1023f63cd41f9f.js	207 ms	3.9 ms	18 ms
code.org/_next/static/chunks/5670-318ba52a6b4cab24.js	184 ms	164 ms	20 ms
code.org/_next/static/chunks/87c73c54-095cf9a90cf9ee03.js	151 ms	138 ms	13 ms
code.org/_next/static/chunks/7450.c23ebe5a26c30870.js	94 ms	90 ms	1.9 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.0 s
Other	828 ms
Style & Layout	646 ms
Script Parsing & Compilation	301 ms
Parse HTML & CSS	138 ms
Garbage Collection	92 ms
Rendering	79 ms

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

URL	Transfer Size	Est Savings
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	138.1 KiB	136.5 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	14.7 KiB	14.4 KiB
.mui-tyipns{background-color:var(--background-neutral-primary-inverse); … } …	13.1 KiB	10.4 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
Powered by AWS Cloud Computing `footer.mui-tyipns > div.MuiGrid-root > a.MuiTypography-root > img`	code.org/_next/static/media/powered-by-aws.f274900a.webp

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

●Optimize DOM size

●LCP breakdown

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 15 long tasks found

●Avoid non-composited animations 23 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

Accessibility

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

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
WHO WE ARE `div.cf-4c41f6a4d0f6d9764d017cb615a0857c > div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-c3206da2b9ad45bfcd0bb3b3549acb47 > p.MuiTypography-root`
FLAGSHIP WORK `section.section-background-secondary > div.MuiContainer-root > div.cf-ad95f457ade13bd9c8fd2226396dce62 > p.MuiTypography-root`
OUR SUPPORTERS `div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-d6e4617d602895b466c7440880251b1f > p.MuiTypography-root`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Curriculum for the AI era `div.cf-a7c8dbcf2b8e47039ae8d687b4f06d99 > div.cf-63e35c8243004acac65b04828fdd9a47 > div.cf-f6a86e00f23d5ad8f796977a686bc25c > h4.MuiTypography-root`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn about Code.org `div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-19fa17c745ec096b6396c78685291e49 > a.genericButton-module__button___-ZvEw`
Explore more stats `div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-793ea3ccffb5860a2e85fc3fc0a1a02e > a.genericButton-module__button___-ZvEw`
Partner with us `div.cf-c75c47033e830504de35b5df5840ea5f > div.cf-1664d88001345c4955b130e4604c0a1d > div.cf-d63c92cb905caad3d90b4c391c27ebc8 > a.genericButton-module__button___-ZvEw`
Explore curriculum catalog `div.cf-503a38a75061122bc5d2aa1222d3213a > div.cf-a318afa9f3a81b1b7a0bb62e50593924 > div.cf-8fef7fbb8527341d663afedbed841ef3 > a.genericButton-module__button___-ZvEw`
Get started now `div.cf-6d9929e522f0aa34377f6efce0f8c247 > div.cf-25973a64a5784700b2a80e055ebfcfb5 > div.cf-883b8fa4bbcfcecabbee156469550e16 > a.genericButton-module__button___-ZvEw`
Read the Framework `div.cf-81eb36cf5c15490dae991c5d843279a1 > div.cf-670a77c1bf4aec010c56b582328319f6 > div.cf-4a29891aecab19aa62b4e710ca426272 > a.genericButton-module__button___-ZvEw`
Meet our supporters `div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-ae51a5a9e52d3cdce5283a41fb9a6798 > a.genericButton-module__button___-ZvEw`
Sign up for free `section.section-background-patternPrimary > div.MuiContainer-root > div.cf-3c6501cbcaeb07b42da6b85d8ed7c835 > a.genericButton-module__button___-ZvEw`

○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

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

●Select elements have associated label elements.

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
code.org/_next/static/chunks/4445.c2d7ef35f9eae3f6.js	`[object Event]`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
code.org/en-US

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

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.

747 ms

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

1.40 s

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

77 ms

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

0.045

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

762 ms

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.17 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
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	75 ms
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	45 ms

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:82.901 source:map[type:text value:[unattributed]]]]

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
div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > div.cf-d442defc83cbe049355e312f4bc523d4 > figure.mui-1c10u4r > img.mui-t3ax9v `div.cf-fe544dd2deb4dddb8ba27b4b4f5679ea > div.cf-d442defc83cbe049355e312f4bc523d4 > figure.mui-1c10u4r > img.mui-t3ax9v`	/_next/image?url=https%3A%2F%2Fcontentful-images.code.org...	59.3 KiB	54.5 KiB
div.cf-c8b92fcfae6c8e2f89c239f16ce0580f > div.cf-4f32cd0c22d3e721f89c11ea630f7894 > figure.image--hasRoundedCorners > img.mui-t3ax9v `div.cf-c8b92fcfae6c8e2f89c239f16ce0580f > div.cf-4f32cd0c22d3e721f89c11ea630f7894 > figure.image--hasRoundedCorners > img.mui-t3ax9v`	/_next/image?url=https%3A%2F%2Fcontentful-images.code.org...	51.5 KiB	49.6 KiB
div.cf-94e9c4b3889d8ef68f2e07b9b3d20876 > div.cf-21ae972b34af61357b4c01b59eede86a > figure.image--hasRoundedCorners > img.mui-t3ax9v `div.cf-94e9c4b3889d8ef68f2e07b9b3d20876 > div.cf-21ae972b34af61357b4c01b59eede86a > figure.image--hasRoundedCorners > img.mui-t3ax9v`	/_next/image?url=https%3A%2F%2Fcontentful-images.code.org...	17.8 KiB	15.4 KiB
div.cf-e1f3f1c9a6352ed29ec0ee3d002cd7e8 > div.cf-37fb84308ab20792fae9b81791f19e7c > figure.image--hasRoundedCorners > img.mui-t3ax9v `div.cf-e1f3f1c9a6352ed29ec0ee3d002cd7e8 > div.cf-37fb84308ab20792fae9b81791f19e7c > figure.image--hasRoundedCorners > img.mui-t3ax9v`	/_next/image?url=https%3A%2F%2Fcontentful-images.code.org...	12.4 KiB	12.4 KiB
Powered by AWS Cloud Computing `footer.mui-tyipns > div.MuiGrid-root > a.MuiTypography-root > img`	code.org/_next/static/media/powered-by-aws.f274900a.webp	5.6 KiB	5.4 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-5-DIV

nodeLabel: AI is reshaping the world Education must lead what comes next AI is transformi…

path: 1,HTML,1,BODY,7,MAIN,1,DIV

selector: body > main > div.cf-5c1c11cc9d6348b9402354ba1afa6063

snippet: <div style="display:flex" class="cf-5c1c11cc9d6348b9402354ba1afa6063 contentful-container" data-test-id="contentful-container">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	604800.0 s	253.8 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	604800.0 s	138.7 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	604800.0 s	99.4 KiB
global.localizecdn.com/localize.js	259200.0 s	27.1 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	604800.0 s	15.3 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/custom-icons.min.css	604800.0 s	2.6 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/duotone.min.css	604800.0 s	1.9 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/regular.min.css	604800.0 s	1.2 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/solid.min.css	604800.0 s	1.2 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
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/solid.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/regular.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/duotone.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/css/custom-icons.min.css	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-brands-400.woff2	http/1.1
dsco.code.org/assets/font-awesome-pro/1764885473/webfonts/fa-solid-900.woff2	http/1.1

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
code.org/_next/static/css/3649fad98a5c4288.css	3.3 KiB
code.org/_next/static/css/fc9bd2059a10c6bf.css	4.8 KiB
code.org/_next/static/css/6cad3d0b054b25aa.css	2.9 KiB
code.org/_next/static/css/cd681a87f39631fa.css	4.7 KiB
code.org/_next/static/css/ccdbab6f669c4427.css	6.6 KiB
code.org/_next/static/css/a07c7ae1d7733746.css	2.2 KiB
code.org/_next/static/css/98e7c9d886edde2d.css	2.2 KiB
code.org/_next/static/css/428ae77ce7d5f063.css	2.4 KiB
code.org/_next/static/css/28d87e222cb9076d.css	4.7 KiB
code.org/_next/static/css/4f32e6447ded6c32.css	5.2 KiB
code.org/_next/static/css/a8091194558206ff.css	2.6 KiB
code.org/_next/static/css/54ab74348ea3e55f.css	8.5 KiB
code.org/_next/static/css/fd9143fa9538c881.css	8.6 KiB
code.org/_next/static/css/5d3778b73b07efeb.css	4.8 KiB
code.org/_next/static/css/39446bf7eb31383c.css	936 B
code.org/_next/static/css/1ca261cdc7d789e1.css	8.5 KiB
code.org/_next/static/css/f6c2429bc3b51ee0.css	5.5 KiB
code.org/_next/static/css/a479fafba9d943bd.css	4.8 KiB
code.org/_next/static/css/bee4ec13ee316a5e.css	2.9 KiB
code.org/_next/static/css/6e1eefb1dec4ec64.css	4.5 KiB
code.org/_next/static/css/a05adaee2ff82ff8.css	4.3 KiB
code.org/_next/static/css/7f5925cac80368ee.css	1.7 KiB
code.org/_next/static/css/94fa8b0ad645af3b.css	1.9 KiB
code.org/_next/static/css/4bba0c0c0877b0da.css	1.6 KiB
code.org/_next/static/css/0f0cc336d30f5fb2.css	2.4 KiB
code.org/_next/static/css/b62f7b4ad22470af.css	2.1 KiB
code.org/_next/static/css/3fb483857a8c9bc6.css	838 B

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

URL	Time Spent
code.org/	264 ms
code.org/en-US	0.0 ms

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 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: 110 ms 161.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-L9HT5MZ3HD	178.1 KiB	67.7 KiB
code.org/_next/static/chunks/326-7f1023f63cd41f9f.js	67.7 KiB	34.9 KiB
code.org/_next/static/chunks/5670-318ba52a6b4cab24.js	57.5 KiB	34.2 KiB
/_next/static/chunks/app/[brand]/[locale]/[[...paths]]/pa...	65.2 KiB	24.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 161.2 KiB

URL	Transfer Size	Est Savings
dsco.code.org/assets/font-awesome-pro/1764885473/css/fontawesome.min.css	138.1 KiB	136.4 KiB
dsco.code.org/assets/font-awesome-pro/1764885473/css/brands.min.css	14.7 KiB	14.4 KiB
.mui-tyipns{background-color:var(--background-neutral-primary-inverse); … } …	13.1 KiB	10.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Powered by AWS Cloud Computing `footer.mui-tyipns > div.MuiGrid-root > a.MuiTypography-root > img`	code.org/_next/static/media/powered-by-aws.f274900a.webp

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

●Time to Interactive 2.2 s

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 6 user timings

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 32 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

Accessibility

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
Learn `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li > a`
Teach `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li > a`
Districts `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li > a`
Stats `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li.header-module__hasDisplayLogic___J-YPW > a`
Donate `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li.header-module__hasDisplayLogic___J-YPW > a`
Incubator `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li.header-module__hasDisplayLogic___J-YPW > a`
About `nav.header-module__mainLinksWrapper___K-T4u > ul.header-module__mainLinks___0WyP9 > li.header-module__hasDisplayLogic___J-YPW > a`
New Project `nav.header-module__buttonLinks___0IdUj > div > button.genericButton-module__button___-ZvEw > span`
Sign In `nav.header-module__buttonLinks___0IdUj > div.header-module__accountLinks___QoFXK > a.genericButton-module__button___-ZvEw > span`
Create Account `nav.header-module__buttonLinks___0IdUj > div.header-module__accountLinks___QoFXK > a.genericButton-module__button___-ZvEw > span`
WHO WE ARE `div.cf-4c41f6a4d0f6d9764d017cb615a0857c > div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-c3206da2b9ad45bfcd0bb3b3549acb47 > p.MuiTypography-root`
FLAGSHIP WORK `section.section-background-secondary > div.MuiContainer-root > div.cf-ad95f457ade13bd9c8fd2226396dce62 > p.MuiTypography-root`
OUR SUPPORTERS `div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-d6e4617d602895b466c7440880251b1f > p.MuiTypography-root`

These are opportunities to improve the legibility of your content.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Curriculum for the AI era `div.cf-a7c8dbcf2b8e47039ae8d687b4f06d99 > div.cf-63e35c8243004acac65b04828fdd9a47 > div.cf-f6a86e00f23d5ad8f796977a686bc25c > h4.MuiTypography-root`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
New Project `header.header-module__headerNavigation___GWCIp > nav.header-module__buttonLinks___0IdUj > div > button.genericButton-module__button___-ZvEw`
Learn about Code.org `div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-19fa17c745ec096b6396c78685291e49 > a.genericButton-module__button___-ZvEw`
Explore more stats `div.cf-97f92044dc40a2f5f0093c31861b9841 > div.cf-5171f0cd3bd370039acfda30d9bd4c01 > div.cf-793ea3ccffb5860a2e85fc3fc0a1a02e > a.genericButton-module__button___-ZvEw`
Partner with us `div.cf-c75c47033e830504de35b5df5840ea5f > div.cf-1664d88001345c4955b130e4604c0a1d > div.cf-d63c92cb905caad3d90b4c391c27ebc8 > a.genericButton-module__button___-ZvEw`
Explore curriculum catalog `div.cf-503a38a75061122bc5d2aa1222d3213a > div.cf-a318afa9f3a81b1b7a0bb62e50593924 > div.cf-8fef7fbb8527341d663afedbed841ef3 > a.genericButton-module__button___-ZvEw`
Get started now `div.cf-6d9929e522f0aa34377f6efce0f8c247 > div.cf-25973a64a5784700b2a80e055ebfcfb5 > div.cf-883b8fa4bbcfcecabbee156469550e16 > a.genericButton-module__button___-ZvEw`
Read the Framework `div.cf-81eb36cf5c15490dae991c5d843279a1 > div.cf-670a77c1bf4aec010c56b582328319f6 > div.cf-4a29891aecab19aa62b4e710ca426272 > a.genericButton-module__button___-ZvEw`
Meet our supporters `div.cf-8b4434df2a9778b5ef0b45338ad7044d > div.cf-98672fd7b4fe05d51c848acf6d8959b1 > div.cf-ae51a5a9e52d3cdce5283a41fb9a6798 > a.genericButton-module__button___-ZvEw`
Sign up for free `section.section-background-patternPrimary > div.MuiContainer-root > div.cf-3c6501cbcaeb07b42da6b85d8ed7c835 > a.genericButton-module__button___-ZvEw`

○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

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

●Select elements have associated label elements.

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
code.org/_next/static/chunks/4445.c2d7ef35f9eae3f6.js	`[object Event]`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
code.org/en-US

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Results for https://code.org

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)

Usability (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

Navigation

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Best Practices

General

SEO

Keyboard Shortcuts