Lighthouse Mobile

· 0 checks — Mobile 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.

100

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
git-scm.com/images/progit2.png	14400.0 s	115.0 KiB
git-scm.com/images/branching-illustration@2x.png	14400.0 s	18.1 KiB
/application.min.37b496802d9a245ad5c3fc19799a1f38f8230ed9...	14400.0 s	14.1 KiB
/js/application.min.501227e6642ae966f2b54bebd344b2c06c1eb...	14400.0 s	5.4 KiB
git-scm.com/js/modernizr.js	14400.0 s	4.1 KiB
git-scm.com/images/logo@2x.png	14400.0 s	4.0 KiB
git-scm.com/js/session.min.js	14400.0 s	3.4 KiB
git-scm.com//images/logos/downloads/Git-Icon-1788C.png	14400.0 s	2.8 KiB
git-scm.com/images/icons/fa-gears.svg	14400.0 s	1.4 KiB
git-scm.com//images/bg/body.jpg	14400.0 s	1.2 KiB
git-scm.com/images/icons/fa-comments.svg	14400.0 s	966 B
git-scm.com/images/icons/fa-screwdriver-wrench.svg	14400.0 s	940 B
git-scm.com/js/jquery.defaultvalue.js	14400.0 s	665 B
git-scm.com/images/icons/fa-book-open.svg	14400.0 s	654 B
git-scm.com/images/icons/fa-lightbulb.svg	14400.0 s	635 B
git-scm.com//images/bg/isometric-grid.png	14400.0 s	630 B
git-scm.com/images/dark-mode.svg	14400.0 s	577 B
git-scm.com/images/icons/fa-down-long.svg	14400.0 s	550 B
git-scm.com//images/icons/search.png	14400.0 s	538 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: div#masthead > div.inner > div.illustration-wrapper > img.illustration

path: 1,HTML,1,BODY,1,DIV,0,DIV,1,DIV,0,IMG

selector: div#masthead > div.inner > div.illustration-wrapper > img.illustration

snippet: <img class="illustration" src="/images/branching-illustration@2x.png" width="389" height="251">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
git-scm.com/js/modernizr.js	4.1 KiB
/application.min.37b496802d9a245ad5c3fc19799a1f38f8230ed9...	14.1 KiB	333 ms

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#front-content > section#front-navigation > div#front-book > img `div#front-content > section#front-navigation > div#front-book > img`	git-scm.com/images/progit2.png	114.6 KiB	112.6 KiB
div#masthead > div.inner > div.illustration-wrapper > img.illustration `div#masthead > div.inner > div.illustration-wrapper > img.illustration`	git-scm.com/images/branching-illustration@2x.png	17.8 KiB	8.0 KiB

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: 170 ms 12.1 KiB

URL	Transfer Size	Est Savings
/application.min.37b496802d9a245ad5c3fc19799a1f38f8230ed9...	13.9 KiB	12.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: 0.0 ms 58.4 KiB

URL	Transfer Size	Est Savings
code.jquery.com/ui/1.14.1/jquery-ui.min.js	65.4 KiB	58.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
body#home > div.inner > header > img#dark-mode-button `body#home > div.inner > header > img#dark-mode-button`	git-scm.com/images/dark-mode.svg

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

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.2 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 275 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

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

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#home > div.inner > header > img#dark-mode-button `body#home > div.inner > header > img#dark-mode-button`
div#masthead > div.inner > div.illustration-wrapper > img.illustration `div#masthead > div.inner > div.illustration-wrapper > img.illustration`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a.install-link > img `ul > li > a.install-link > img`
ul > li > a > img `ul > li > a > img`
div#front-content > section#front-navigation > div#front-book > img `div#front-content > section#front-navigation > div#front-book > img`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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.js `html.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-hidden="true"]` is not present on the document `<body>`

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○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

○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

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

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

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
git-scm.com//images/bg/body.jpg	Automatically upgraded to HTTPS
git-scm.com//images/icons/search.png	Automatically upgraded to HTTPS
git-scm.com//images/bg/isometric-grid.png	Automatically upgraded to HTTPS
git-scm.com//images/logos/downloads/Git-Icon-1788C.png	Automatically upgraded to HTTPS

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

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#home > div.inner > header > img#dark-mode-button `body#home > div.inner > header > img#dark-mode-button`
div#masthead > div.inner > div.illustration-wrapper > img.illustration `div#masthead > div.inner > div.illustration-wrapper > img.illustration`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a > img `ul > li > a > img`
ul > li > a.install-link > img `ul > li > a.install-link > img`
ul > li > a > img `ul > li > a > img`
div#front-content > section#front-navigation > div#front-book > img `div#front-content > section#front-navigation > div#front-book > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`