Skip to content
Audit Complete

Results for https://www.khanacademy.org

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:13 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D68

Site Health

Score: 68 / 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)

1

Content-Security-Policy header is missing

Security › Security Headers
2

Cookie '_fs_ch_st_FSBmUei20MqUiJb9' is missing the Secure flag

Security › Cookie Security
3

HSTS header is missing

Security › Security Headers
4

No Content-Security-Policy header found

Security › Content Security Policy
5

No <main> landmark found

Accessibility › Landmark Structure
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.khanacademy.org)](https://beavercheck.com/results/15411427-b0dd-504b-7a6c-fb22a1117eea)
<a href="https://beavercheck.com/results/15411427-b0dd-504b-7a6c-fb22a1117eea"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.khanacademy.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.khanacademy.org

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

43
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

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

10.12 s

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

658 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.43 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.47 s

Detailed Report

Audit breakdown by category with detailed findings.

43

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.

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

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.

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

RequestCache TTLTransfer Size
/api/badges/download-on-the-app-store/black/en-us?release...604800.0 s11.3 KiB

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.

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

URLResource SizeEst Savings
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/faces_collage_2@2x.png666.4 KiB623.2 KiB
Learners Teachers Parents Back div._vtegui > div._e296pg > div#last-chance-lohp > div._18iqadbp
cdn.kastatic.org/images/lohp/last_chance_collage@2x.png373.4 KiB177.1 KiB
div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1 div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1
cdn.kastatic.org/images/lohp/laptop_collage@2x.png181.6 KiB138.7 KiB
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/math-unicorn-donate-collage.png158.3 KiB120.7 KiB
div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1 div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1
cdn.kastatic.org/images/lohp/anjali-3.png75.7 KiB70.2 KiB
Get it on Google Play ul > li._ouyp5ih > a._wilhdph > img._1iym5ly
cdn.kastatic.org/images/store-badges/google-play/en.png5.9 KiB5.3 KiB
Bill and Melinda Gates Foundation div._51yg8mt > div._vuhkxie > div._1t9h51bq > img._55m9r6s
cdn.kastatic.org/images/supporters-logos/gates-foundation-dark-gray@2x.png8.2 KiB5.2 KiB

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

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.

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

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: 2.5 s 508.4 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.

URLTotal CPU TimeScript EvaluationScript Parse
cdn.kastatic.org/khanacademy/khanacademy.d010d00049edb0e5.js1.6 s1.3 s193 ms
Unattributable436 ms40 ms0.0 ms
www.khanacademy.org/319 ms33 ms29 ms
cdn.kastatic.org/khanacademy/82289.7eff447bec28ae13.js201 ms167 ms2.5 ms
www.googletagmanager.com/gtm.js?id=GTM-WSX5PBP136 ms92 ms43 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

CategoryTime Spent
Script Evaluation1.6 s
Other498 ms
Script Parsing & Compilation315 ms
Style & Layout306 ms
Rendering50 ms
Parse HTML & CSS20 ms
Garbage Collection15 ms

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

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

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

URL
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/faces_collage_2@2x.png
div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1 div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1
cdn.kastatic.org/images/lohp/laptop_collage@2x.png
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/math-unicorn-donate-collage.png
Get it on Google Play ul > li._ouyp5ih > a._wilhdph > img._1iym5ly
cdn.kastatic.org/images/store-badges/google-play/en.png
div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1 div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1
cdn.kastatic.org/images/lohp/anjali-3.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp
cdn.kastatic.org/images/lohp/trusted_content_icon.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/personalized_learning_icon.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/empower_teachers_icon.png
Download on the App Store ul > li._ouyp5ih > a._wilhdph > img._1iym5ly
/api/badges/download-on-the-app-store/black/en-us?release...

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

Layout shift culprits
Document request latency
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 2 user timings
Avoid long main-thread tasks 5 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 210 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 220 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
Avoid large layout shifts
100

Accessibility

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

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.

Failing Elements
English div._s6za34 > div._1bvnlzk > div._6kyiev1 > button#:r2:
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.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

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

SourceDescription
Uncaught (in promise) KANotFoundError: Failed to load https://cdn.cookielaw.org/scripttemplates/otSDKStub.js.
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
3 <head>Syntax not understood
4 <metaSyntax not understood
5 http-equiv="Content-Security-Policy"Syntax not understood
6 content="default-src 'self'; img-src 'self' data:; media-src 'self' data:; object-src 'none'; style-src 'self' 'sha256-o4vzfmmUENEg4chMjjRP9EuW9ucGnGIGVdbl8d0SHQQ='; script-src 'self' 'sha256-KXex2o39zxtnzVWK4H5rW07g2+BlwSPtn+aguzsWkNg=';"Unknown directive
7 />Syntax not understood
8 <linkSyntax not understood
9 href="/_fs-ch-1T1wmsGaOgGaSxcX/assets/inter-var.woff2"Syntax not understood
10 rel="preload"Syntax not understood
11 as="font"Syntax not understood
12 type="font/woff2"Syntax not understood
13 crossoriginSyntax not understood
14 />Syntax not understood
15 <link href="/_fs-ch-1T1wmsGaOgGaSxcX/assets/styles.css" rel="stylesheet" />Syntax not understood
16 <meta name="viewport" content="width=device-width, initial-scale=1" />Syntax not understood
17 <title>Client Challenge</title>Syntax not understood
18 <style>Syntax not understood
20 font-size: 16px;Unknown directive
21 font-family: 'Inter', sans-serif;Unknown directive
22 margin-top: 10px;Unknown directive
23 margin-left: 10px;Unknown directive
24 display: none;Unknown directive
25 }Syntax not understood
26 </style>Syntax not understood
27 </head>Syntax not understood
28 <body>Syntax not understood
29 <noscript>Syntax not understood
30 <div class="noscript-container">Syntax not understood
31 <div class="noscript-content">Syntax not understood
32 <imgSyntax not understood
33 src="/_fs-ch-1T1wmsGaOgGaSxcX/assets/errorIcon.svg"Syntax not understood
34 alt=""Syntax not understood
35 role="presentation"Syntax not understood
36 class="error-icon"Syntax not understood
37 />Syntax not understood
38 <span class="noscript-span"Syntax not understood
39 >JavaScript is disabled in your browser.</spanSyntax not understood
40 >Syntax not understood
41 <p>Please enable JavaScript to proceed.</p>Syntax not understood
42 </div>Syntax not understood
43 </div>Syntax not understood
44 </noscript>Syntax not understood
45 <div id="loading-error" role="alert" aria-live="polite">Syntax not understood
46 A required part of this site couldn’t load. This may be due to a browserSyntax not understood
47 extension, network issues, or browser settings. Please check yourSyntax not understood
48 connection, disable any ad blockers, or try using a different browser.Syntax not understood
49 </div>Syntax not understood
50 <script>Syntax not understood
51 function loadScript(src) {Syntax not understood
52 return new Promise((resolve, reject) => {Syntax not understood
53 const script = document.createElement('script');Syntax not understood
54 script.onload = resolve;Syntax not understood
55 script.onerror = (event) => {Syntax not understood
56 console.error('Script load error event:', event);Unknown directive
57 document.getElementById('loading-error').style.display = 'block';Syntax not understood
58 loadingError.setAttribute('aria-hidden', 'false');Syntax not understood
59 reject(Syntax not understood
60 new Error(Syntax not understood
61 `Failed to load script: ${src}, Please contact the service administrator.`Unknown directive
62 )Syntax not understood
63 );Syntax not understood
64 };Syntax not understood
65 script.src = src;Syntax not understood
66 document.body.appendChild(script);Syntax not understood
67 });Syntax not understood
68 }Syntax not understood
70 loadScript('/_fs-ch-1T1wmsGaOgGaSxcX/errors.js')Syntax not understood
71 .then(() => {Syntax not understood
72 const script = document.createElement('script');Syntax not understood
73 script.src = '/_fs-ch-1T1wmsGaOgGaSxcX/script.js?reload=true';Syntax not understood
74 script.onerror = (event) => {Syntax not understood
75 console.error('Script load error event:', event);Unknown directive
76 const errorMsg = new Error(Syntax not understood
77 `Failed to load script: ${script.src}. Please contact the service administrator.`Unknown directive
78 );Syntax not understood
79 console.error(errorMsg);Syntax not understood
80 handleScriptError();Syntax not understood
81 };Syntax not understood
82 document.body.appendChild(script);Syntax not understood
83 })Syntax not understood
84 .catch((error) => {Syntax not understood
85 console.error(error);Syntax not understood
86 });Syntax not understood
87 </script>Syntax not understood
88 </body>Syntax not understood
89</html>Syntax not understood

To appear in search results, crawlers need access to your app.

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

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

2.37 s

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

120 ms

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

0.010

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

1.81 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.43 s

Detailed Report

Audit breakdown by category with detailed findings.

78

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 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:43.56 source:map[column:472634 line:21 type:source-location url:https://cdn.kastatic.org/khanacademy/khanacademy.d010d00049edb0e5.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:33.709 source:map[column:634977 line:20 type:source-location url:https://cdn.kastatic.org/khanacademy/khanacademy.d010d00049edb0e5.js urlProvider:network]] map[reflowTime:9.851 source:map[column:634859 line:20 type:source-location url:https://cdn.kastatic.org/khanacademy/khanacademy.d010d00049edb0e5.js urlProvider:network]]]

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

lhId: page-0-IMG
nodeLabel: div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51
path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,IMG
selector: div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51
snippet: <img src="https://cdn.kastatic.org/images/lohp/boost-scores.png" alt="" class="_82vv51">

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

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.

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

RequestCache TTLTransfer Size
/api/badges/download-on-the-app-store/black/en-us?release...604800.0 s11.3 KiB

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.

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

URLResource SizeEst Savings
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/faces_collage_2@2x.png666.4 KiB618.9 KiB
div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51 div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51
cdn.kastatic.org/images/lohp/boost-scores.png210.2 KiB180.0 KiB
div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1 div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1
cdn.kastatic.org/images/lohp/laptop_collage@2x.png181.6 KiB134.5 KiB
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/empower_teachers_icon.png9.0 KiB7.3 KiB
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/personalized_learning_icon.png8.8 KiB7.0 KiB
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp
cdn.kastatic.org/images/lohp/trusted_content_icon.png9.1 KiB7.0 KiB
cdn.kastatic.org/images/store-badges/google-play/en.png5.9 KiB5.7 KiB

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

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.

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.

Estimated savings: 400 ms 508.3 KiB

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

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

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

URL
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/faces_collage_2@2x.png
div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1 div._e296pg > div._mg36wky > div._et3ir1 > img._1k6dqj1
cdn.kastatic.org/images/lohp/laptop_collage@2x.png
div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1 div._e296pg > div._1b4n03jl > div._hoh1o6o > img._1k6dqj1
cdn.kastatic.org/images/lohp/math-unicorn-donate-collage.png
div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51 div._1s6u9f56 > div._8plbkmf > div._1lnhlk8u > img._82vv51
cdn.kastatic.org/images/lohp/boost-scores.png
Get it on Google Play ul > li._ouyp5ih > a._wilhdph > img._1iym5ly
cdn.kastatic.org/images/store-badges/google-play/en.png
div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1 div._8iuiziq > div._1wqqgcad > div._46s8e9s > img._1k6dqj1
cdn.kastatic.org/images/lohp/anjali-3.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._14srqcp
cdn.kastatic.org/images/lohp/trusted_content_icon.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/personalized_learning_icon.png
div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7 div._3vgeo5o > div._5hffmqw > div._xnpl0ze > img._zdxht7
cdn.kastatic.org/images/lohp/empower_teachers_icon.png
Download on the App Store ul > li._ouyp5ih > a._wilhdph > img._1iym5ly
/api/badges/download-on-the-app-store/black/en-us?release...

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

Time to Interactive 2.4 s
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 2 user timings
JavaScript execution time 0.8 s
Minimizes main-thread work 1.3 s
Avoid long main-thread tasks 3 long tasks found
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 240 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 240 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
100

Accessibility

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

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.

Failing Elements
English div._s6za34 > div._1bvnlzk > div._6kyiev1 > button#:r2:
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.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

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

SourceDescription
Uncaught (in promise) KANotFoundError: Failed to load https://cdn.cookielaw.org/scripttemplates/otSDKStub.js.
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
3 <head>Syntax not understood
4 <metaSyntax not understood
5 http-equiv="Content-Security-Policy"Syntax not understood
6 content="default-src 'self'; img-src 'self' data:; media-src 'self' data:; object-src 'none'; style-src 'self' 'sha256-o4vzfmmUENEg4chMjjRP9EuW9ucGnGIGVdbl8d0SHQQ='; script-src 'self' 'sha256-KXex2o39zxtnzVWK4H5rW07g2+BlwSPtn+aguzsWkNg=';"Unknown directive
7 />Syntax not understood
8 <linkSyntax not understood
9 href="/_fs-ch-1T1wmsGaOgGaSxcX/assets/inter-var.woff2"Syntax not understood
10 rel="preload"Syntax not understood
11 as="font"Syntax not understood
12 type="font/woff2"Syntax not understood
13 crossoriginSyntax not understood
14 />Syntax not understood
15 <link href="/_fs-ch-1T1wmsGaOgGaSxcX/assets/styles.css" rel="stylesheet" />Syntax not understood
16 <meta name="viewport" content="width=device-width, initial-scale=1" />Syntax not understood
17 <title>Client Challenge</title>Syntax not understood
18 <style>Syntax not understood
20 font-size: 16px;Unknown directive
21 font-family: 'Inter', sans-serif;Unknown directive
22 margin-top: 10px;Unknown directive
23 margin-left: 10px;Unknown directive
24 display: none;Unknown directive
25 }Syntax not understood
26 </style>Syntax not understood
27 </head>Syntax not understood
28 <body>Syntax not understood
29 <noscript>Syntax not understood
30 <div class="noscript-container">Syntax not understood
31 <div class="noscript-content">Syntax not understood
32 <imgSyntax not understood
33 src="/_fs-ch-1T1wmsGaOgGaSxcX/assets/errorIcon.svg"Syntax not understood
34 alt=""Syntax not understood
35 role="presentation"Syntax not understood
36 class="error-icon"Syntax not understood
37 />Syntax not understood
38 <span class="noscript-span"Syntax not understood
39 >JavaScript is disabled in your browser.</spanSyntax not understood
40 >Syntax not understood
41 <p>Please enable JavaScript to proceed.</p>Syntax not understood
42 </div>Syntax not understood
43 </div>Syntax not understood
44 </noscript>Syntax not understood
45 <div id="loading-error" role="alert" aria-live="polite">Syntax not understood
46 A required part of this site couldn’t load. This may be due to a browserSyntax not understood
47 extension, network issues, or browser settings. Please check yourSyntax not understood
48 connection, disable any ad blockers, or try using a different browser.Syntax not understood
49 </div>Syntax not understood
50 <script>Syntax not understood
51 function loadScript(src) {Syntax not understood
52 return new Promise((resolve, reject) => {Syntax not understood
53 const script = document.createElement('script');Syntax not understood
54 script.onload = resolve;Syntax not understood
55 script.onerror = (event) => {Syntax not understood
56 console.error('Script load error event:', event);Unknown directive
57 document.getElementById('loading-error').style.display = 'block';Syntax not understood
58 loadingError.setAttribute('aria-hidden', 'false');Syntax not understood
59 reject(Syntax not understood
60 new Error(Syntax not understood
61 `Failed to load script: ${src}, Please contact the service administrator.`Unknown directive
62 )Syntax not understood
63 );Syntax not understood
64 };Syntax not understood
65 script.src = src;Syntax not understood
66 document.body.appendChild(script);Syntax not understood
67 });Syntax not understood
68 }Syntax not understood
70 loadScript('/_fs-ch-1T1wmsGaOgGaSxcX/errors.js')Syntax not understood
71 .then(() => {Syntax not understood
72 const script = document.createElement('script');Syntax not understood
73 script.src = '/_fs-ch-1T1wmsGaOgGaSxcX/script.js?reload=true';Syntax not understood
74 script.onerror = (event) => {Syntax not understood
75 console.error('Script load error event:', event);Unknown directive
76 const errorMsg = new Error(Syntax not understood
77 `Failed to load script: ${script.src}. Please contact the service administrator.`Unknown directive
78 );Syntax not understood
79 console.error(errorMsg);Syntax not understood
80 handleScriptError();Syntax not understood
81 };Syntax not understood
82 document.body.appendChild(script);Syntax not understood
83 })Syntax not understood
84 .catch((error) => {Syntax not understood
85 console.error(error);Syntax not understood
86 });Syntax not understood
87 </script>Syntax not understood
88 </body>Syntax not understood
89</html>Syntax not understood

To appear in search results, crawlers need access to your app.

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`

Send Feedback