Skip to content
https://torproject.org

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

72

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.

RequestCache TTLTransfer Size
www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c3600.0 s85.4 KiB
www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f3600.0 s68.6 KiB
www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c9786400.0 s98.5 KiB
www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d386400.0 s97.6 KiB
www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c9786400.0 s92.1 KiB
www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d386400.0 s88.7 KiB
www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd86400.0 s70.0 KiB
www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb86400.0 s65.8 KiB
www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c86400.0 s63.1 KiB
www.torproject.org/static/css/bootstrap.css?h=0d5c9bf63600.0 s29.7 KiB
www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd86400.0 s49.1 KiB
www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=3c73ff1c3600.0 s22.7 KiB
www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c86400.0 s41.4 KiB
www.torproject.org/static/js/popper.min.js?h=a43367193600.0 s19.5 KiB
www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb86400.0 s29.2 KiB
www.torproject.org/static/js/scrollspy.min.js?h=026741323600.0 s7.1 KiB
www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc86400.0 s10.6 KiB
www.torproject.org/static/js/modernizr.js?h=9a7f06093600.0 s4.6 KiB
www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.png86400.0 s4.1 KiB
www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.png86400.0 s4.0 KiB
www.torproject.org/static/js/fallback.js?h=8a716acd3600.0 s1.8 KiB
www.torproject.org/static/images/circle-pattern.svg?h=9a4040e486400.0 s2.5 KiB
www.torproject.org/static/js/download.js?h=4ce9d0953600.0 s1.2 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

URLResource SizeEst Savings
Browse Freely div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d396.8 KiB56.2 KiB
Resist Fingerprinting div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c9797.7 KiB53.6 KiB
Multi-layered Encryption div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd69.2 KiB41.6 KiB
Defend Against Surveillance div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c62.3 KiB36.7 KiB
Block Trackers div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb64.9 KiB29.6 KiB
The Tor Project nav.navbar > div.d-flex > a.navbar-brand > img
www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc9.8 KiB7.9 KiB

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-4-IMG
nodeLabel: Block Trackers
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.card > div.row > div.col-md-5 > img
snippet: <img src="static/images/home/svg/block-trackers.svg?h=70991bcb" class="" alt="Block Trackers">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.torproject.org/http/1.1
www.torproject.org/static/css/bootstrap.css?h=0d5c9bf6http/1.1
www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=3c73ff1chttp/1.1
www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bchttp/1.1
www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcbhttp/1.1
www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829chttp/1.1
www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97http/1.1
www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3ddhttp/1.1
www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3http/1.1
www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018chttp/1.1
www.torproject.org/static/js/popper.min.js?h=a4336719http/1.1
www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82fhttp/1.1
www.torproject.org/static/js/scrollspy.min.js?h=02674132http/1.1
www.torproject.org/static/js/modernizr.js?h=9a7f0609http/1.1
www.torproject.org/static/js/download.js?h=4ce9d095http/1.1
www.torproject.org/static/js/fallback.js?h=8a716acdhttp/1.1
www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.pnghttp/1.1
www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.pnghttp/1.1
www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttfhttp/1.1
www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttfhttp/1.1
www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttfhttp/1.1
www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcbhttp/1.1
www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829chttp/1.1
www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97http/1.1
www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3ddhttp/1.1
www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3http/1.1
www.torproject.org/static/images/circle-pattern.svg?h=9a4040e4http/1.1
www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2http/1.1
www.torproject.org/static/images/favicon/favicon.pnghttp/1.1
www.torproject.org/static/images/favicon/favicon.icohttp/1.1

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms
URLTime Spent
torproject.org/750 ms
www.torproject.org/0.0 ms

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

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: 330 ms 48.8 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: 810 ms 109.2 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
Block Trackers div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
Defend Against Surveillance div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
Resist Fingerprinting div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
Multi-layered Encryption div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
Browse Freely div.card > div.row > div.col-md-5 > img
www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
The Tor Project nav.navbar > div.d-flex > a.navbar-brand > img
www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,507 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.9 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 0 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 130 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
83

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle navigation nav.navbar > div.d-flex > label.position-absolute > a.btn

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle navigation nav.navbar > div.d-flex > label.position-absolute > a.btn

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.

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
Defend yourself against tracking and surveillance. Circumvent censorship. div.row > div.col-12 > div.row > h3.mx-auto
ABOUT US div.row > main.mx-auto > div.container > h6
Our mission: div.row > div.col-12 > div.col-sm-6 > h5.font-weight-bold

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Meet our team main.mx-auto > div.container > p > 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-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
●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
●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 have a discernible name
●Touch targets have sufficient size and spacing.
●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-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 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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
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
●Use a strong HSTS policy
●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
○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`

Send Feedback