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.

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.

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
static.djangoproject.com/js/mod/switch-dark-mode.139625c684db.js	1.2 KiB
static.djangoproject.com/css/output.c538cb572318.css	26.3 KiB	902 ms

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
static.djangoproject.com/font/Roboto-Light.4b97d1da126a.woff2	10 ms
static.djangoproject.com/font/Roboto-Regular.62d315e68f04.woff2	5.0 ms
static.djangoproject.com/font/Roboto-Bold.b7e6688d781f.woff2	5.0 ms
static.djangoproject.com/font/fontawesome-webfont.d95d6f5d5ab7.woff?v=4.2.0	5.0 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: 0.0 ms 22.1 KiB

URL	Transfer Size	Est Savings
static.djangoproject.com/css/output.c538cb572318.css	25.9 KiB	22.1 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
Support Django! `div > div.fundraising-sidebar > div.small-heart > img`	static.djangoproject.com/img/fundraising-heart.cd6bb84ffd33.svg

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

●Time to Interactive 3.1 s

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 316 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 30 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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
Get started with Django `section.copy-banner > div.container > p > a.cta`
Learn more about Django `div.container > main#main-content > div.section > a.cta`
BACK TO TOP `body#homepage > div.container > main#main-content > a.backtotop`
Download latest release: 6.0.3 `body#homepage > div.container > div > a.cta`
latest release: 6.0.3 `div.container > div > a.cta > em`
DJANGO DOCUMENTATION `body#homepage > div.container > div > a.link-readmore`
Automatic Doorz donated to the Django Software Foundation to support Django dev… `div.small-cta > ul.list-links-small > li > a`
DSF member of the month - Theresa Seyram Agbenyegah `ul.list-news > li > h4 > a`
Posted by Sarah Abderemane on March 8, 2026 `div > ul.list-news > li > span.meta`
Sarah Abderemane `ul.list-news > li > span.meta > strong`
Django security releases issued: 6.0.3, 5.2.12, and 4.2.29 `ul.list-news > li > h4 > a`
Posted by Natalia Bidart on March 3, 2026 `div > ul.list-news > li > span.meta`
Natalia Bidart `ul.list-news > li > span.meta > strong`
MORE NEWS `body#homepage > div.container > div > a.link-readmore`
Installation guide `div > ul.list-links-small > li > a`
Write your first Django app `div > ul.list-links-small > li > a`
GETTING STARTED WITH DJANGO `body#homepage > div.container > div > a.link-readmore`
Object-relational mapper `div > ul.list-links-small > li > a`
Automatic admin interface `div > ul.list-links-small > li > a`
Robust template system `div > ul.list-links-small > li > a`
Quick internationalization `div > ul.list-links-small > li > a`
EXPLORE MORE FEATURES `body#homepage > div.container > div > a.link-readmore`
Ticket system `div > dl.list-links-small > dt > a`
Report bugs and make feature requests `div.container > div > dl.list-links-small > dd`
Development dashboard `div > dl.list-links-small > dt > a`
see what's currently being worked on `div.container > div > dl.list-links-small > dd`
INSIDE THE DJANGO COMMUNITY `body#homepage > div.container > div > a.link-readmore`
Django Discord Server `div > dl.list-links-small > dt > a`
Join the Django Discord Community `div.container > div > dl.list-links-small > dd`
Official Django Forum `div > dl.list-links-small > dt > a`
Join the community on the Django Forum. `div.container > div > dl.list-links-small > dd`
About the Foundation `div > dl.list-links-small > dt > a`
Our non-profit supports the project `div.container > div > dl.list-links-small > dd`
Support Django `div > dl.list-links-small > dt > a`
Your contribution makes Django stronger `div.container > div > dl.list-links-small > dd`
Contact the Django Software Foundation `div > dl.list-links-small > dt > a`
MORE ABOUT THE DSF `body#homepage > div.container > div > a.link-readmore`
Learn More `div.container > div.column-container > div.col-learn-more > h3`
About Django `div.col-learn-more > ul > li > a`
Getting Started with Django `div.col-learn-more > ul > li > a`
Team Organization `div.col-learn-more > ul > li > a`
Django Software Foundation `div.col-learn-more > ul > li > a`
Code of Conduct `div.col-learn-more > ul > li > a`
Diversity Statement `div.col-learn-more > ul > li > a`
Get Involved `div.container > div.column-container > div.col-get-involved > h3`
Join a Group `div.col-get-involved > ul > li > a`
Contribute to Django `div.col-get-involved > ul > li > a`
Submit a Bug `div.col-get-involved > ul > li > a`
Report a Security Issue `div.col-get-involved > ul > li > a`
Individual membership `div.col-get-involved > ul > li > a`
Get Help `div.container > div.column-container > div.col-get-help > h3`
Getting Help FAQ `div.col-get-help > ul > li > a`
Django Discord `div.col-get-help > ul > li > a`
Official Django Forum `div.col-get-help > ul > li > a`
Follow Us `div.container > div.column-container > div.col-follow-us > h3`
GitHub `div.col-follow-us > ul > li > a`
Fediverse (Mastodon) `div.col-follow-us > ul > li > a`
Bluesky `div.col-follow-us > ul > li > a`
LinkedIn `div.col-follow-us > ul > li > a`
News RSS `div.col-follow-us > ul > li > a`
Support Us `div.container > div.column-container > div.col-support-us > h3`
Sponsor Django `div.col-support-us > ul > li > a`
Corporate membership `div.col-support-us > ul > li > a`
Official merchandise store `div.col-support-us > ul > li > a`
Benevity Workplace Giving Program `div.col-support-us > ul > li > a`
Hosting by `div.container > ul.thanks > li > span`
In-kind donors `div.container > ul.thanks > li > a.in-kind-donors`
Design by `div.container > ul.thanks > li.design > span`
© 2005-2026 Django Software Foundation and individual contributors. Django is a… `footer > div.footer > div.container > p.copyright`
Django Software Foundation `div.footer > div.container > p.copyright > a`
registered trademark `div.footer > div.container > p.copyright > a`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

100

Best Practices

●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

●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

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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.

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`