Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A 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:280.067 source:map[type:text value:[unattributed]]] map[reflowTime:130.472 source:map[column:20381 line:15 type:source-location url:https://github.githubassets.com/assets/26533-f22c29ae5e9b1ed2.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
github.githubassets.com/assets/high-contrast-cookie-218067197ba03c91.js	1002 B
github.githubassets.com/assets/site-8e580c38ab6535be.css	82.3 KiB
github.githubassets.com/assets/global-81a5f61ff87ac6f0.css	40.4 KiB
github.githubassets.com/assets/github-f825c0edd7ad57f8.css	24.0 KiB
github.githubassets.com/assets/primer-b48faa60c69660fa.css	42.6 KiB
github.githubassets.com/assets/marketing-navigation.9c460dc5436e5da3.module.css	2.2 KiB
/assets/keyboard-shortcuts-dialog.670668115736ecbc.module...	393 B
github.githubassets.com/assets/landing-pages.95e52e4789131d48.module.css	12.9 KiB
github.githubassets.com/assets/primer-react-css.48c74afb1f96b5a7.module.css	32.4 KiB
github.githubassets.com/assets/landing-pages-270babc3e592e1db.css	440 B
github.githubassets.com/assets/home-b65ad196250a1364.css	8.4 KiB
github.githubassets.com/assets/react-core.0c5a60be620dab14.module.css	433 B
github.githubassets.com/assets/light_high_contrast-f7f95d7633592089.css	6.6 KiB
github.githubassets.com/assets/light-2ff56e1b36116ee2.css	6.8 KiB	235 ms
github.githubassets.com/assets/dark_high_contrast-d530ee188d165539.css	6.7 KiB
github.githubassets.com/assets/dark-2d1fe43dbc9adf1f.css	6.6 KiB
github.githubassets.com/assets/primer-primitives-7f694b60439d06c0.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 193.9 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/site-8e580c38ab6535be.css	82.1 KiB	69.9 KiB
github.githubassets.com/assets/global-81a5f61ff87ac6f0.css	39.9 KiB	39.2 KiB
github.githubassets.com/assets/primer-react-css.48c74afb1f96b5a7.module.css	32.0 KiB	32.0 KiB
github.githubassets.com/assets/github-f825c0edd7ad57f8.css	23.6 KiB	23.6 KiB
github.githubassets.com/assets/primer-b48faa60c69660fa.css	42.1 KiB	16.6 KiB
github.githubassets.com/assets/landing-pages.95e52e4789131d48.module.css	12.7 KiB	12.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 120 ms 788.6 KiB

URL	Transfer Size	Est Savings
github.githubassets.com/assets/landing-pages-29d9816a92404e81.js	438.0 KiB	409.3 KiB
github.githubassets.com/assets/primer-react-0eccd57ee759dfd8.js	122.3 KiB	67.0 KiB
github.githubassets.com/assets/react-lib-1353f2cef82bcdc0.js	87.2 KiB	51.3 KiB
github.githubassets.com/assets/48761-e0d707ef4ac523be.js	113.3 KiB	48.0 KiB
github.githubassets.com/assets/react-core-b2929a643e0ecc05.js	65.8 KiB	46.3 KiB
github.githubassets.com/assets/behaviors-d9f0cee1f9e3eb0f.js	54.0 KiB	43.9 KiB
github.githubassets.com/assets/37826-36074ccbdf2fd58c.js	58.1 KiB	42.9 KiB
github.githubassets.com/assets/70641-df7d286b6e757eb5.js	101.7 KiB	32.8 KiB
github.githubassets.com/assets/63050-9f22093e0909629c.js	27.1 KiB	24.0 KiB
github.githubassets.com/assets/67466-79abcbf599986a00.js	30.2 KiB	23.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	5.1 s
Script Evaluation	1.4 s
Style & Layout	797 ms
Script Parsing & Compilation	255 ms
Parse HTML & CSS	97 ms
Rendering	82 ms
Garbage Collection	32 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
github.githubassets.com/assets/landing-pages-29d9816a92404e81.js	438.4 KiB
github.githubassets.com/assets/cat-53c4522f687c1719.glb	268.1 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.4 KiB
/8aevphvgewt8/3xzVZaJhqo3B62R8NeHjX2/e37c81e4f26e9dac2aff...	187.4 KiB
github.githubassets.com/assets/duck-b3412913788eaa25.glb	170.9 KiB
/8aevphvgewt8/1Dt1ncaR6ZM4dQvknFzfBI/e5c2092be5bd53881622...	163.1 KiB
github.githubassets.com/assets/head_sss-29270cf59da664ea.jpg	139.8 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
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 101 user timings

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 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 30 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●`[lang]` attributes have a valid value

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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`