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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
s.gravatar.com/videos/homepage/multi-identity-small.mp4	0.0 ms	2.7 MiB
gravatar.com/images/homepage/profile-tina-large.png	0.0 ms	349.0 KiB
gravatar.com/images/homepage/profile-bg-02.png	0.0 ms	167.7 KiB
gravatar.com/images/homepage/multi-identity-small-cover.png	0.0 ms	143.7 KiB
gravatar.com/images/homepage/multi-identity-large-cover.png	0.0 ms	137.5 KiB
gravatar.com/images/homepage/profile-bg-01.png	0.0 ms	91.7 KiB
gravatar.com/images/homepage/profile-privacy-large-cover.png	0.0 ms	87.0 KiB
gravatar.com/images/homepage/profile-privacy-small-cover.png	0.0 ms	79.2 KiB
s.gravatar.com/js/landing-page/landing-page.js?ver=e790138180c789240cdd	604800.0 s	709.5 KiB
gravatar.com/images/homepage/card-ethan.png	0.0 ms	44.1 KiB
gravatar.com/images/homepage/card-sofia.png	0.0 ms	41.8 KiB
gravatar.com/images/homepage/card-jessica.png	0.0 ms	40.9 KiB
gravatar.com/images/homepage/card-joe.png	0.0 ms	40.7 KiB
gravatar.com/images/homepage/card-tina.png	0.0 ms	37.7 KiB
/fonts/L0xTDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_3vrtSM1J-gEPT5...	0.0 ms	22.4 KiB
s.gravatar.com/css/landing-page/landing-page.css?ver=49bfa7c6f9d5f6e34f72	604800.0 s	51.9 KiB
gravatar.com/images/homepage/card-placeholder.png	0.0 ms	4.9 KiB
gravatar.com/icons/privacy-options.svg	0.0 ms	762 B
s.gravatar.com/videos/homepage/profile-privacy-small.mp4	0.0 ms	0 B

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
Tina Wells profile `div.g-wrapper > div.g-columns > div > img.profile-card--large`	gravatar.com/images/homepage/profile-tina-large.png	348.8 KiB	261.6 KiB
body#page > section.g-section > img.profile-background `body#page > section.g-section > img.profile-background`	gravatar.com/images/homepage/profile-bg-02.png	167.5 KiB	154.9 KiB
div.g-columns > div > div.g-video-wrapper > video `div.g-columns > div > div.g-video-wrapper > video`	gravatar.com/images/homepage/multi-identity-large-cover.png	137.3 KiB	107.3 KiB
body#page > section.g-section > img.profile-background `body#page > section.g-section > img.profile-background`	gravatar.com/images/homepage/profile-bg-01.png	91.5 KiB	80.5 KiB
div.g-columns > div > div.g-video-wrapper > video `div.g-columns > div > div.g-video-wrapper > video`	gravatar.com/images/homepage/profile-privacy-large-cover.png	86.8 KiB	65.1 KiB
Ethan Clark `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card`	gravatar.com/images/homepage/card-ethan.png	43.9 KiB	29.9 KiB
Sofia Marinos `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card`	gravatar.com/images/homepage/card-sofia.png	41.5 KiB	28.3 KiB
Jessica Lee `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card`	gravatar.com/images/homepage/card-jessica.png	40.7 KiB	27.8 KiB
Joe Casabona `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card`	gravatar.com/images/homepage/card-joe.png	40.5 KiB	27.6 KiB
Tina Wells `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card`	gravatar.com/images/homepage/card-tina.png	37.5 KiB	25.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

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
s.gravatar.com/js/landing-page/landing-page.js?ver=e790138180c789240cdd	709.5 KiB	527 ms
s.gravatar.com/css/landing-page/landing-page.css?ver=49bfa7c6f9d5f6e34f72	51.9 KiB	338 ms

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 22.1 KiB

URL	Transfer Size	Est Savings
s.gravatar.com/css/landing-page/landing-page.css?ver=49bfa7c6f9d5f6e34f72	51.6 KiB	22.1 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: 40 ms 108.2 KiB

URL	Transfer Size	Est Savings
s.gravatar.com/js/landing-page/landing-page.js?ver=e790138180c789240cdd	709.1 KiB	54.9 KiB
www.googletagmanager.com/gtag/js?id=G-ZK2E2B4FHH	164.5 KiB	53.3 KiB

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
s.gravatar.com/videos/homepage/multi-identity-small.mp4	2.7 MiB
s.gravatar.com/js/landing-page/landing-page.js?ver=e790138180c789240cdd	709.5 KiB
gravatar.com/images/homepage/profile-tina-large.png	349.0 KiB
gravatar.com/images/homepage/profile-bg-02.png	167.7 KiB
www.googletagmanager.com/gtag/js?id=G-ZK2E2B4FHH	164.8 KiB
gravatar.com/images/homepage/multi-identity-small-cover.png	143.7 KiB
gravatar.com/images/homepage/multi-identity-large-cover.png	137.5 KiB
s.gravatar.com/videos/homepage/profile-privacy-small.mp4	96.3 KiB
gravatar.com/images/homepage/profile-bg-01.png	91.7 KiB
gravatar.com/images/homepage/profile-privacy-large-cover.png	87.0 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
Tina Wells profile `div.g-wrapper > div.g-columns > div > img.profile-card--large`	gravatar.com/images/homepage/profile-tina-large.png
div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card-placeholder `div.g-wrapper > div.g-columns > div.g-hero-cards > img.g-hero-cards__card-placeholder`	gravatar.com/images/homepage/card-placeholder.png
Privacy options icon `ul > li#ccpa-donotsell > a > img`	gravatar.com/icons/privacy-options.svg
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`
div.g-wrapper > div.g-columns > div.g-avatar-wall > img `div.g-wrapper > div.g-columns > div.g-avatar-wall > img`

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

●Time to Interactive 2.4 s

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 2 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 170 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 50 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
example.js example.php 1 2 3 4 5 6 7 8 9 10 11 12 13 14 const sha256 = require(… `div.g-wrapper > div.g-columns > div.g-scroll-x > div.g-editor`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GRAVATAR IS USED BY `body#page > section.g-section > div.g-wrapper > p`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PROFILES-AS-A-SERVICE `div.g-columns > div > div.g-content > h4.g-color-accent`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.g-js `html.g-js`

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

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

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

●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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s 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

○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

○Buttons have an accessible name

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

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

○Elements with visible text labels have matching accessible names.

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

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

100

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
s.gravatar.com/js/landing-page/landing-page.js?ver=e790138180c789240cdd

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`