C — https://github.com | BeaverCheck Audit

Site Health

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

Page weighs 12.4 MB (5.3 MB transferred)

Performance › Page Weight Budget

1 control(s) without accessible label

Accessibility › Form Accessibility

2 button(s) with no accessible text

Accessibility › Link & Button Quality

3 image-only link(s) without alt text

Accessibility › Link & Button Quality

150 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.com)](https://beavercheck.com/results/b11326d6-eacd-4def-9be5-13d6add1abf9)

HTML

<a href="https://beavercheck.com/results/b11326d6-eacd-4def-9be5-13d6add1abf9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgithub.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

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.

5.48 s

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

20.89 s

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

17.69 s

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.

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

42.45 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

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

A 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:190.375 source:map[column:20381 line:15 type:source-location url:https://github.githubassets.com/assets/26533-4df1172b25427069.js urlProvider:network]]]

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

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

title: Preconnected origins

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

title: Preconnect candidates

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.

URL	Transfer Size	Duration
github.githubassets.com/assets/high-contrast-cookie-fed1d93364101384.js	809 B
github.githubassets.com/assets/github-c94ab8d1f22049a8.css	23.6 KiB	150 ms
github.githubassets.com/assets/global-0bd78641c0a1f3e0.css	40.3 KiB	150 ms
github.githubassets.com/assets/primer-react-css.f296da2f85469022.module.css	31.7 KiB	150 ms
github.githubassets.com/assets/marketing-navigation.5b4138cab2f44179.module.css	2.2 KiB
github.githubassets.com/assets/site-4884328cf1d6633f.css	9.0 KiB
github.githubassets.com/assets/landing-pages-8a6ddfb3febb09cd.css	69.0 KiB	300 ms
github.githubassets.com/assets/landing-pages.76e638001968cfc6.module.css	12.8 KiB
/assets/keyboard-shortcuts-dialog.f581ff34f52b4167.module...	398 B
github.githubassets.com/assets/primer-0fcd9af82350aeda.css	42.6 KiB	300 ms
github.githubassets.com/assets/react-core.d14f70276c05a07b.module.css	450 B
github.githubassets.com/assets/home-1aab590db4b38e90.css	8.4 KiB	150 ms
github.githubassets.com/assets/light-0c8222dcd7a4f9b7.css	6.5 KiB	759 ms
github.githubassets.com/assets/dark-fc6eec18532c3ae0.css	6.8 KiB
github.githubassets.com/assets/dark_high_contrast-96d7b2bab5a6ae4e.css	7.0 KiB
github.githubassets.com/assets/light_high_contrast-51c0c6e0c085cc0f.css	6.6 KiB	150 ms
github.githubassets.com/assets/primer-primitives-10bf9dd67e3d70bd.css	2.1 KiB

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

	URL	Resource Size	Est Savings
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/1uXZYDy7dMcH9QwxuAU06F/1cb167cc60d725b8cf70...	208.3 KiB	162.1 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/3xzVZaJhqo3B62R8NeHjX2/e37c81e4f26e9dac2aff...	186.8 KiB	145.4 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/1Dt1ncaR6ZM4dQvknFzfBI/e5c2092be5bd53881622...	162.5 KiB	126.5 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/3cgNgdKFqflI27vyDh4Gpa/c459dc8690133e7663b8...	120.1 KiB	93.5 KiB
div.lp-SectionBlock-content > div.lp-SectionHero > div.lp-SectionHero-glow > img.particles `div.lp-SectionBlock-content > div.lp-SectionHero > div.lp-SectionHero-glow > img.particles`	github.githubassets.com/assets/particles-170bd1fd231f4669.png	33.7 KiB	31.3 KiB

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

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

TTI

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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 900 ms 177.6 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/landing-pages-8a6ddfb3febb09cd.css	68.9 KiB	58.6 KiB
github.githubassets.com/assets/global-0bd78641c0a1f3e0.css	39.8 KiB	38.8 KiB
github.githubassets.com/assets/primer-react-css.f296da2f85469022.module.css	31.5 KiB	31.5 KiB
github.githubassets.com/assets/github-c94ab8d1f22049a8.css	23.5 KiB	23.5 KiB
github.githubassets.com/assets/primer-0fcd9af82350aeda.css	31.9 KiB	12.8 KiB
github.githubassets.com/assets/landing-pages.76e638001968cfc6.module.css	12.4 KiB	12.3 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 3.6 s 687.7 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	351.6 KiB	303.8 KiB
github.githubassets.com/assets/primer-react-72d2ec7521017972.js	120.8 KiB	63.7 KiB
github.githubassets.com/assets/react-lib-a4cf89fce9a1300a.js	87.3 KiB	51.3 KiB
github.githubassets.com/assets/48761-4941fce410205fe2.js	113.4 KiB	48.1 KiB
github.githubassets.com/assets/behaviors-9ddaeb4e06adcb60.js	56.8 KiB	46.5 KiB
github.githubassets.com/assets/37826-b3ebde81e7762221.js	58.1 KiB	42.9 KiB
github.githubassets.com/assets/6572-01263ee51465ffb1.js	98.2 KiB	38.3 KiB
github.githubassets.com/assets/react-core-2e47687b4310af0f.js	57.2 KiB	38.0 KiB
github.githubassets.com/assets/70641-5a6ec3de78151c22.js	98.1 KiB	30.4 KiB
github.githubassets.com/assets/39130-334926c8365e947c.js	32.2 KiB	24.9 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.

URL	Total CPU Time	Script Evaluation	Script Parse
github.githubassets.com/assets/chunk-39118-a79af489cc7bc7cc.js	16.6 s	490 ms	4.9 ms
github.githubassets.com/assets/46752-46c707717fcbe6a9.js	3.4 s	351 ms	12 ms
github.com/	3.2 s	12 ms	0.8 ms
github.githubassets.com/assets/react-lib-a4cf89fce9a1300a.js	3.1 s	2.3 s	118 ms
Unattributable	1.4 s	148 ms	0.0 ms
github.githubassets.com/assets/behaviors-9ddaeb4e06adcb60.js	1.1 s	302 ms	39 ms
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	1.1 s	868 ms	197 ms
github.githubassets.com/assets/64247-7de91c52a8aca0eb.js	320 ms	264 ms	4.2 ms
github.githubassets.com/assets/github-elements-459d4cd7a0f718d7.js	277 ms	270 ms	6.0 ms
github.githubassets.com/assets/26533-4df1172b25427069.js	275 ms	166 ms	11 ms
github.githubassets.com/assets/chunk-81053-ad578dfd0f4b86f1.js	260 ms	228 ms	8.9 ms
github.githubassets.com/assets/primer-react-72d2ec7521017972.js	142 ms	2.8 ms	138 ms
github.githubassets.com/assets/environment-51c0968cf21c176d.js	94 ms	77 ms	5.6 ms
github.githubassets.com/assets/70641-5a6ec3de78151c22.js	92 ms	3.0 ms	88 ms
github.githubassets.com/assets/48761-4941fce410205fe2.js	90 ms	7.7 ms	80 ms
github.githubassets.com/assets/6572-01263ee51465ffb1.js	86 ms	1.7 ms	83 ms
github.githubassets.com/assets/sessions-2f8b9c6ac9ed412d.js	68 ms	43 ms	3.1 ms
github.githubassets.com/assets/octicons-react-a181826f33dcd4d8.js	64 ms	1.7 ms	62 ms
github.githubassets.com/assets/chunk-57335-95eca4aef7d7626c.js	64 ms	49 ms	13 ms
github.githubassets.com/assets/landing-pages-8a6ddfb3febb09cd.css	57 ms	0.0 ms	0.0 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

Category	Time Spent
Other	20.6 s
Script Evaluation	6.1 s
Style & Layout	3.8 s
Script Parsing & Compilation	1.3 s
Rendering	487 ms
Parse HTML & CSS	392 ms
Garbage Collection	136 ms

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

URL	Transfer Size
github.githubassets.com/assets/code-1_mobile-56dc14fe27999221.mp4	930.5 KiB
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	352.0 KiB
github.githubassets.com/assets/cat-53c4522f687c1719.glb	268.0 KiB
github.githubassets.com/assets/copilot-2addefe0e666acf2.glb	247.7 KiB
github.githubassets.com/assets/MonaSansVF-wdth-wght-opsz-902d64c7ad02.woff2	214.6 KiB
/8aevphvgewt8/1uXZYDy7dMcH9QwxuAU06F/1cb167cc60d725b8cf70...	208.9 KiB
github.githubassets.com/assets/head_sss-b7e053d8d541a414.jpg	189.3 KiB
/8aevphvgewt8/3xzVZaJhqo3B62R8NeHjX2/e37c81e4f26e9dac2aff...	187.4 KiB
github.githubassets.com/assets/duck-b3412913788eaa25.glb	170.8 KiB
/8aevphvgewt8/1Dt1ncaR6ZM4dQvknFzfBI/e5c2092be5bd53881622...	163.1 KiB

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

	URL
Duolingo `div.lp-SectionTemplate-customer > div.Primer_Brand__Pillar-module__Pillar___dHhm7 > span.Primer_Brand__Pillar-module__Pillar__icon___MyYVk > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/g1XhuDG7foMyNWIEIpGJj/b40a790b854d0803704de...
Gartner `div.lp-SectionTemplate-customer > div.Primer_Brand__Pillar-module__Pillar___dHhm7 > span.Primer_Brand__Pillar-module__Pillar__icon___MyYVk > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/6Qr8Snm4JceoMFRJhapgFa/802ded1d2c486a9d0a4c...

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 102 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 130 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 10 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Terms `nav > ul.list-style-none > li > a.Link--secondary`
What is Git? `nav > ul.list-style-none > li > a.Link--secondary`
Manage cookies `ul.list-style-none > li > cookie-consent-link > button.Link--secondary`
Do not share my personal information `ul.list-style-none > li > cookie-consent-link > button.Link--secondary`

These items highlight common accessibility best practices.

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
Code `div.Toggle-wrapper > div > div#_R_2k5b_ > button#_R_2k5b_-button`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

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

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

○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

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

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.

817 ms

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

1.49 s

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

2.73 s

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.

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

9.00 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

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:149.366 source:map[column:534 line:2 type:source-location url:https://github.githubassets.com/assets/96232-69d46a31854353d4.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:175.126 source:map[type:text value:[unattributed]]] map[reflowTime:117.803 source:map[column:20381 line:15 type:source-location url:https://github.githubassets.com/assets/26533-4df1172b25427069.js urlProvider:network]] map[reflowTime:103.447 source:map[column:2237 line:1 type:source-location url:https://github.githubassets.com/assets/22445-1d247a8bf5b6a1d5.js urlProvider:network]] map[reflowTime:45.919 source:map[column:1862 line:1 type:source-location url:https://github.githubassets.com/assets/22445-1d247a8bf5b6a1d5.js urlProvider:network]]]

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

title: Preconnected origins

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

title: Preconnect candidates

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.

URL	Transfer Size	Duration
github.githubassets.com/assets/high-contrast-cookie-fed1d93364101384.js	812 B
github.githubassets.com/assets/landing-pages-8a6ddfb3febb09cd.css	69.0 KiB
github.githubassets.com/assets/primer-react-css.f296da2f85469022.module.css	32.0 KiB
github.githubassets.com/assets/primer-0fcd9af82350aeda.css	42.6 KiB
github.githubassets.com/assets/global-0bd78641c0a1f3e0.css	40.0 KiB
github.githubassets.com/assets/github-c94ab8d1f22049a8.css	23.9 KiB
github.githubassets.com/assets/home-1aab590db4b38e90.css	8.4 KiB
github.githubassets.com/assets/react-core.d14f70276c05a07b.module.css	435 B
github.githubassets.com/assets/site-4884328cf1d6633f.css	9.0 KiB
/assets/keyboard-shortcuts-dialog.f581ff34f52b4167.module...	661 B
github.githubassets.com/assets/landing-pages.76e638001968cfc6.module.css	12.5 KiB
github.githubassets.com/assets/marketing-navigation.5b4138cab2f44179.module.css	2.3 KiB
github.githubassets.com/assets/dark_high_contrast-96d7b2bab5a6ae4e.css	6.7 KiB
github.githubassets.com/assets/dark-fc6eec18532c3ae0.css	6.6 KiB
github.githubassets.com/assets/light_high_contrast-51c0c6e0c085cc0f.css	6.9 KiB
github.githubassets.com/assets/light-0c8222dcd7a4f9b7.css	6.8 KiB	219 ms
github.githubassets.com/assets/primer-primitives-10bf9dd67e3d70bd.css	2.1 KiB

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

	URL	Resource Size	Est Savings
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/1uXZYDy7dMcH9QwxuAU06F/1cb167cc60d725b8cf70...	208.3 KiB	174.9 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/3xzVZaJhqo3B62R8NeHjX2/e37c81e4f26e9dac2aff...	186.8 KiB	156.9 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/1Dt1ncaR6ZM4dQvknFzfBI/e5c2092be5bd53881622...	162.5 KiB	136.5 KiB
div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK `div.lp-SectionBlock-content > div.Primer_Brand__Grid-module__Grid___q48mT > div.Primer_Brand__Grid-module__Grid__column___HTpsw > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/3cgNgdKFqflI27vyDh4Gpa/c459dc8690133e7663b8...	120.1 KiB	100.8 KiB
div.lp-SectionBlock-content > div.lp-SectionHero > div.lp-SectionHero-glow > img.particles `div.lp-SectionBlock-content > div.lp-SectionHero > div.lp-SectionHero-glow > img.particles`	github.githubassets.com/assets/particles-170bd1fd231f4669.png	33.7 KiB	26.1 KiB

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

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

TTI

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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 120 ms 149.5 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/landing-pages-8a6ddfb3febb09cd.css	68.9 KiB	58.0 KiB
github.githubassets.com/assets/global-0bd78641c0a1f3e0.css	39.8 KiB	39.1 KiB
github.githubassets.com/assets/github-c94ab8d1f22049a8.css	23.5 KiB	23.5 KiB
github.githubassets.com/assets/primer-0fcd9af82350aeda.css	42.1 KiB	16.6 KiB
github.githubassets.com/assets/landing-pages.76e638001968cfc6.module.css	12.4 KiB	12.3 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 80 ms 687.9 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	351.6 KiB	303.9 KiB
github.githubassets.com/assets/primer-react-72d2ec7521017972.js	120.8 KiB	63.7 KiB
github.githubassets.com/assets/react-lib-a4cf89fce9a1300a.js	87.3 KiB	51.4 KiB
github.githubassets.com/assets/48761-4941fce410205fe2.js	113.4 KiB	48.0 KiB
github.githubassets.com/assets/behaviors-9ddaeb4e06adcb60.js	56.8 KiB	46.5 KiB
github.githubassets.com/assets/37826-b3ebde81e7762221.js	58.1 KiB	42.9 KiB
github.githubassets.com/assets/6572-01263ee51465ffb1.js	98.2 KiB	38.3 KiB
github.githubassets.com/assets/react-core-2e47687b4310af0f.js	57.2 KiB	38.0 KiB
github.githubassets.com/assets/70641-5a6ec3de78151c22.js	98.1 KiB	30.4 KiB
github.githubassets.com/assets/39130-334926c8365e947c.js	32.2 KiB	24.9 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.

URL	Total CPU Time	Script Evaluation	Script Parse
github.githubassets.com/assets/chunk-39118-a79af489cc7bc7cc.js	4.0 s	118 ms	2.1 ms
github.githubassets.com/assets/react-lib-a4cf89fce9a1300a.js	1.1 s	936 ms	16 ms
github.com/	1.1 s	4.8 ms	0.3 ms
github.githubassets.com/assets/46752-46c707717fcbe6a9.js	698 ms	7.6 ms	2.5 ms
Unattributable	347 ms	32 ms	0.0 ms
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	285 ms	232 ms	48 ms
github.githubassets.com/assets/behaviors-9ddaeb4e06adcb60.js	200 ms	72 ms	9.2 ms
github.githubassets.com/assets/marketing-essentials-9a86288f791548e3.js	166 ms	17 ms	0.2 ms
github.githubassets.com/assets/64247-7de91c52a8aca0eb.js	137 ms	111 ms	1.2 ms
github.githubassets.com/assets/chunk-81053-ad578dfd0f4b86f1.js	53 ms	46 ms	2.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

Category	Time Spent
Other	5.1 s
Script Evaluation	1.8 s
Style & Layout	1.1 s
Script Parsing & Compilation	300 ms
Parse HTML & CSS	139 ms
Rendering	119 ms
Garbage Collection	41 ms

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

URL	Transfer Size
github.githubassets.com/assets/landing-pages-55a9ce378b6db113.js	352.0 KiB
github.githubassets.com/assets/cat-53c4522f687c1719.glb	268.2 KiB
github.githubassets.com/assets/copilot-2addefe0e666acf2.glb	247.6 KiB
github.githubassets.com/assets/MonaSansVF-wdth-wght-opsz-902d64c7ad02.woff2	214.6 KiB
/8aevphvgewt8/1uXZYDy7dMcH9QwxuAU06F/1cb167cc60d725b8cf70...	208.9 KiB
github.githubassets.com/assets/head_sss-b7e053d8d541a414.jpg	189.6 KiB
/8aevphvgewt8/3xzVZaJhqo3B62R8NeHjX2/e37c81e4f26e9dac2aff...	187.4 KiB
github.githubassets.com/assets/duck-b3412913788eaa25.glb	170.8 KiB
/8aevphvgewt8/1Dt1ncaR6ZM4dQvknFzfBI/e5c2092be5bd53881622...	163.1 KiB
github.githubassets.com/assets/head_sss-29270cf59da664ea.jpg	139.7 KiB

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

	URL
Duolingo `div.lp-SectionTemplate-customer > div.Primer_Brand__Pillar-module__Pillar___dHhm7 > span.Primer_Brand__Pillar-module__Pillar__icon___MyYVk > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/g1XhuDG7foMyNWIEIpGJj/b40a790b854d0803704de...
Gartner `div.lp-SectionTemplate-customer > div.Primer_Brand__Pillar-module__Pillar___dHhm7 > span.Primer_Brand__Pillar-module__Pillar__icon___MyYVk > img.Primer_Brand__Image-module__Image___FgVuK`	/8aevphvgewt8/6Qr8Snm4JceoMFRJhapgFa/802ded1d2c486a9d0a4c...

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 102 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 120 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 10 ms

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

Accessibility

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Terms `nav > ul.list-style-none > li > a.Link--secondary`
Privacy `nav > ul.list-style-none > li > a.Link--secondary`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

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

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

○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

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://github.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Keyboard Shortcuts