torproject.org

torproject.org is SSL secured

Free website and domain report on torproject.org

Last Updated: 19th August, 2024 Update Now
Overview

Snoop Summary for torproject.org

This is a free and comprehensive report about torproject.org. The domain torproject.org is currently hosted on a server located in Germany with the IP address 95.216.163.36, where EUR is the local currency and the local language is German. Our records indicate that torproject.org is privately registered by The Tor Project, Inc. Torproject.org is expected to earn an estimated $1,663 USD per day from advertising revenue. The sale of torproject.org would possibly be worth $1,214,283 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Torproject.org receives an estimated 265,085 unique visitors every day - an insane amount of traffic! This report was last updated 19th August, 2024.

About torproject.org

Site Preview: torproject.org torproject.org
Title: Tor Project | Anonymity Online
Description: Anonymity Online | Defend yourself against tracking and surveillance. Circumvent censorship.
Keywords and Tags: onion router, popular, the onion router, tor, tor browser, tor browser download, tor browser mac, tor download, tor network, tor onion, tor project, tor web browser, ultrasurf, what is tor, 洋葱 浏览 器
Related Terms: anonymity, anonymity on the internet, anonymity test, censorship, steeperton tor, tor com, tor.kr, watern tor
Fav Icon:
Age: Over 17 years old
Domain Created: 17th October, 2006
Domain Updated: 20th September, 2023
Domain Expires: 17th October, 2027
Review

Snoop Score

4/5 (Excellent!)

Valuation

$1,214,283 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,089
Alexa Reach:
SEMrush Rank (US): 7,680
SEMrush Authority Score: 76
Moz Domain Authority: 85
Moz Page Authority: 67

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 34,104 0
Traffic: 376,579 0
Cost: $171,124 USD $0 USD
Traffic

Visitors

Daily Visitors: 265,085
Monthly Visitors: 8,068,352
Yearly Visitors: 96,756,025
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,663 USD
Monthly Revenue: $50,628 USD
Yearly Revenue: $607,137 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 11,981,616
Referring Domains: 51,258
Referring IPs: 51,860
Torproject.org has 11,981,616 backlinks according to SEMrush. 79% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve torproject.org's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of torproject.org's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://hup.hu/
Target: https://tb-manual.torproject.org/about/

2
Source: https://news.ycombinator.com/
Target: https://blog.torproject.org/covid19-impact-tor/#body

3
Source: https://news.ycombinator.com/
Target: https://blog.torproject.org/covid19-impact-tor

4
Source: https://www.solidot.org/
Target: https://blog.torproject.org/covid19-impact-tor

5
Source: https://www.opennet.ru/opennews/art.shtml?num=52672
Target: https://blog.torproject.org/new-release-tor-browser-908

Top Ranking Keywords (US)

1
Keyword: tor
Ranked Page: https://www.torproject.org/

2
Keyword: tor browser
Ranked Page: https://www.torproject.org/download/

3
Keyword: tor download
Ranked Page: https://www.torproject.org/download/

4
Keyword: tor browser download
Ranked Page: https://www.torproject.org/download/

5
Keyword: tor project
Ranked Page: https://www.torproject.org/

Domain Analysis

Value Length
Domain: torproject.org 14
Domain Name: torproject 10
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.16 seconds
Load Time Comparison: Faster than 64% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 98
Accessibility 96
Best Practices 75
SEO 91
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.torproject.org/
Updated: 8th November, 2022

1.88 seconds
First Contentful Paint (FCP)
74%
16%
10%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for torproject.org. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.047
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://torproject.org/
http/1.1
0
240.71899999399
414
0
301
text/html
https://www.torproject.org/
http/1.1
241.06000002939
1179.186000023
5609
22011
200
text/html
Document
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
http/1.1
1185.455000028
1644.4109999575
33207
210567
200
text/css
Stylesheet
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
http/1.1
1185.5510000605
1794.4830000633
12568
53741
200
text/css
Stylesheet
https://www.torproject.org/static/images/yec-bg-desktop-2x.png?h=ca3ea4d3
http/1.1
1195.0760000618
2229.6039999928
97622
96868
200
image/png
Image
https://www.torproject.org/static/images/yec-foreground-2x_12x.png?h=84c51273
http/1.1
1195.2309999615
1769.8530000634
21556
20799
200
image/png
Image
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
http/1.1
1195.4899999546
1622.4599999841
10789
10042
200
image/png
Image
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
http/1.1
1195.6899999641
1782.8720000107
67258
66496
200
image/png
Image
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
http/1.1
1195.8240000531
1647.7120000636
64570
63810
200
image/png
Image
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
http/1.1
1195.9900000365
2263.401000062
100832
100068
200
image/png
Image
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
http/1.1
1196.1339999689
2069.244000013
71654
70895
200
image/png
Image
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
http/1.1
1196.5290000662
2221.7690000543
99899
99137
200
image/png
Image
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
http/1.1
1192.7750000032
2176.799000008
87419
86659
200
application/javascript
Script
https://www.torproject.org/static/js/popper.min.js?h=a4336719
http/1.1
1193.0990000255
2140.0729999878
19950
19197
200
application/javascript
Script
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
http/1.1
1193.2390000438
2038.6739999522
70217
69453
200
application/javascript
Script
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
http/1.1
1193.6920000007
1953.0570000643
7176
6422
200
application/javascript
Script
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
http/1.1
1193.8849999569
1934.8349999636
4619
3869
200
application/javascript
Script
https://www.torproject.org/static/js/download.js?h=caaadf8f
http/1.1
1194.5429999614
1552.9010000173
1179
431
200
application/javascript
Script
https://www.torproject.org/static/js/fallback.js?h=8ecbf837
http/1.1
1194.7040000232
1771.732000052
2265
1516
200
application/javascript
Script
https://www.torproject.org/static/css/images/x.svg
http/1.1
1805.5820000591
2164.1320000635
975
234
200
image/svg+xml
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.png
http/1.1
1808.1079999683
2221.2399999844
4152
3381
200
image/png
Image
https://www.torproject.org/static/css/images/circle-pattern.png
http/1.1
1808.8109999662
2508.9150000131
556995
556240
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.png
http/1.1
1809.104999993
2381.2910000561
3974
3202
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/facebook.png
http/1.1
1809.8699999973
2161.2800000003
2864
2095
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/mastodon.png
http/1.1
1810.1429999806
2170.3399999533
6413
5643
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/instagram.png
http/1.1
1810.4329999769
2238.4310000343
6244
5472
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/twitter.png
http/1.1
1810.6909999624
2088.4999999544
6414
5645
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/linkedin.png
http/1.1
1810.9800000675
2220.4780000029
3785
3015
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/github.png
http/1.1
1811.1550000031
2247.4099999527
8308
7539
200
image/png
Image
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
http/1.1
1811.7179999826
2163.5369999567
294301
293516
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
http/1.1
1811.8979999563
2265.7240000553
91677
90904
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
http/1.1
1812.1510000201
2345.9509999957
87303
86528
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
http/1.1
1812.367000035
2336.1450000666
87280
86504
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
http/1.1
1812.5200000359
2268.602999975
293463
292680
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
http/1.1
1812.9770000232
2258.2630000543
291698
290916
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-brands-400.woff2
http/1.1
1813.4940000018
2326.5110000502
74723
73936
200
application/font-woff2
Font
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
http/1.1
2226.965000038
2578.3770000562
92008
91245
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
http/1.1
2227.273000055
2929.1880000383
113901
113139
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
http/1.1
2227.4050000124
2791.7920000618
281523
280759
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
http/1.1
2227.5600000285
2700.6490000058
187832
187072
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
http/1.1
2228.7800000049
2839.1899999697
280740
279977
200
image/svg+xml
Image
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
http/1.1
2229.168000049
2575.1460000174
79857
79072
200
application/font-woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1182.86
9.948
1646.338
7.107
1800.184
38.758
2000.664
7.135
2180.324
8.314
2189.181
14.926
2204.277
24.594
2228.907
7.451
2285
6.588
2576.888
5.702
2582.631
6.581
2589.253
6.527
2702.437
20.422
2724.008
6.641
2793.66
30.011
2826.233
8.186
2841.381
24.871
2880.883
6.268
2931.133
11.386
2945.086
5.302
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 94 KiB
Images can slow down the page's load time. Torproject.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/images/yec-bg-desktop-2x.png?h=ca3ea4d3
96868
72651
https://www.torproject.org/static/images/yec-foreground-2x_12x.png?h=84c51273
20799
15582
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
10042
7642
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Torproject.org should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Torproject.org should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
6080
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Torproject.org should consider minifying JS files.
Reduce unused CSS — Potential savings of 42 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Torproject.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
30447
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
12568
12395
Reduce unused JavaScript — Potential savings of 110 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
87419
57996
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
70217
54834
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 123 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
86659
56481
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
69453
50135
https://www.torproject.org/static/js/popper.min.js?h=a4336719
19197
12290
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
6422
4299
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
3869
2337
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Torproject.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://torproject.org/
190
https://www.torproject.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Torproject.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.torproject.org/static/js/popper.min.js?h=a4336719
174
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
169
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 239 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
239
Maximum DOM Depth
13
Maximum Child Elements
16
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Torproject.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
159.36
1.614
0
https://www.torproject.org/
137.242
3.273
1.095
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
125.582
Style & Layout
111.332
Rendering
51.367
Script Evaluation
38.725
Parse HTML & CSS
15.142
Script Parsing & Compilation
5.138
Keep request counts low and transfer sizes small — 42 requests • 3,550 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
42
3635233
Image
23
2090308
Font
8
1300302
Script
7
192825
Stylesheet
2
45775
Document
1
5609
Other
1
414
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.025910579369597
0.010244397145001
0.003824294832928
0.0010511786035645
0.001029353821907
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of torproject.org on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.4 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 160 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Torproject.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
110
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
12568
150
Serve images in next-gen formats — Potential savings of 573 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/css/images/circle-pattern.png
556240
252401.7
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
100068
73391.05
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
99137
71416.3
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
70895
51240.4
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
66496
47560.55
https://www.torproject.org/static/images/yec-bg-desktop-2x.png?h=ca3ea4d3
96868
47230.75
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
63810
43942.5
Avoid enormous network payloads — Total size was 3,550 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.torproject.org/static/css/images/circle-pattern.png
556995
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
294301
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
293463
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
291698
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
281523
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
280740
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
187832
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
113901
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
100832
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
99899

Other

Reduce initial server response time — Root document took 940 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.torproject.org/
939.122
Serve static assets with an efficient cache policy — 40 resources found
Torproject.org can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
3600000
87419
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
3600000
70217
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
3600000
33207
https://www.torproject.org/static/js/popper.min.js?h=a4336719
3600000
19950
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
3600000
12568
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
3600000
7176
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
3600000
4619
https://www.torproject.org/static/js/fallback.js?h=8ecbf837
3600000
2265
https://www.torproject.org/static/js/download.js?h=caaadf8f
3600000
1179
https://www.torproject.org/static/css/images/circle-pattern.png
86400000
556995
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
86400000
281523
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
86400000
280740
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
86400000
187832
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
86400000
113901
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
86400000
100832
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
86400000
99899
https://www.torproject.org/static/images/yec-bg-desktop-2x.png?h=ca3ea4d3
86400000
97622
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
86400000
92008
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
86400000
71654
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
86400000
67258
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
86400000
64570
https://www.torproject.org/static/images/yec-foreground-2x_12x.png?h=84c51273
86400000
21556
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
86400000
10789
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/github.png
86400000
8308
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/twitter.png
86400000
6414
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/mastodon.png
86400000
6413
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/instagram.png
86400000
6244
https://www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.png
86400000
4152
https://www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.png
86400000
3974
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/linkedin.png
86400000
3785
https://www.torproject.org/static/fonts/fontawesome/png/white/brands/facebook.png
86400000
2864
https://www.torproject.org/static/css/images/x.svg
86400000
975
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
2592000000
294301
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
2592000000
293463
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
2592000000
291698
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
2592000000
91677
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
2592000000
87303
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
2592000000
87280
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
2592000000
79857
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-brands-400.woff2
2592000000
74723
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
351.81899997406
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
453.82600009907
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
533.7999999756
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
523.7780000316
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
456.0829999391
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
445.28600003105
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-brands-400.woff2
513.01700004842
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
345.97799996845
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.torproject.org/static/images/yec-bg-desktop-2x.png?h=ca3ea4d3
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
https://www.torproject.org/static/images/yec-foreground-2x_12x.png?h=84c51273
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of torproject.org. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Torproject.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that torproject.org should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.0.0-beta.2
jQuery
3.2.1
Modernizr
3.6.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
https://www.torproject.org/static/js/bootstrap.bundle.min.js.map

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://torproject.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium

Audits

Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Content security policy
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for torproject.org. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of torproject.org on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of torproject.org. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of torproject.org on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 80
Performance 72
Accessibility 90
Best Practices 67
SEO 92
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.torproject.org/
Updated: 8th November, 2022

2.17 seconds
First Contentful Paint (FCP)
67%
20%
13%

0.01 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
72

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for torproject.org. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 3.3 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.016
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://torproject.org/
http/1.1
0
72.156999958679
414
0
301
text/html
https://www.torproject.org/
http/1.1
72.53500004299
720.71200003847
5609
22011
200
text/html
Document
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
http/1.1
729.82599993702
1444.1919999663
33207
210567
200
text/css
Stylesheet
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
http/1.1
729.95299997274
1089.3980000401
12568
53741
200
text/css
Stylesheet
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
http/1.1
737.95700003393
1778.6530000158
228476
227721
200
image/png
Image
https://www.torproject.org/static/images/yec-foreground-2x_13x.png?h=6fd7ec08
http/1.1
738.07900003158
1454.9739999929
38527
37770
200
image/png
Image
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
http/1.1
738.18600003142
1148.8499999978
10789
10042
200
image/png
Image
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
http/1.1
738.36700001266
1156.8940000143
67259
66496
200
image/png
Image
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
http/1.1
738.48299996462
1753.4779999405
64570
63810
200
image/png
Image
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
http/1.1
738.61500003841
1236.4979999838
100832
100068
200
image/png
Image
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
http/1.1
738.80900000222
1548.56200004
71654
70895
200
image/png
Image
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
http/1.1
739.04300003778
1160.3089999408
99899
99137
200
image/png
Image
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
http/1.1
736.37800000142
1618.9899999881
87419
86659
200
application/javascript
Script
https://www.torproject.org/static/js/popper.min.js?h=a4336719
http/1.1
737.03800002113
1110.8189999359
19950
19197
200
application/javascript
Script
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
http/1.1
737.13699996006
1300.2939999569
70216
69453
200
application/javascript
Script
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
http/1.1
737.27599997073
1305.5630000308
7177
6422
200
application/javascript
Script
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
http/1.1
737.36899998039
1140.3249999275
4619
3869
200
application/javascript
Script
https://www.torproject.org/static/js/download.js?h=caaadf8f
http/1.1
737.57400002796
1146.8510000268
1179
431
200
application/javascript
Script
https://www.torproject.org/static/js/fallback.js?h=8ecbf837
http/1.1
737.66500002239
1143.1249999441
2265
1516
200
application/javascript
Script
https://www.torproject.org/static/css/images/x.svg
http/1.1
1460.1620000321
1797.7160000009
974
234
200
image/svg+xml
Image
1461.0899999971
1461.1210000003
0
0
-1
Image
https://www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.png
http/1.1
1462.1999999508
2125.1720000291
4152
3381
200
image/png
Image
https://www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.png
http/1.1
1463.1649999646
1858.6679999717
3974
3202
200
image/png
Image
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
http/1.1
1464.1380000394
1863.2079999661
294301
293516
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
http/1.1
1464.2849999946
2070.9339999594
91676
90904
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
http/1.1
1464.4580000313
2365.2849999489
87303
86528
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
http/1.1
1464.6850000136
2108.4349999437
87279
86504
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
http/1.1
1465.0220000185
2709.7160000121
293464
292680
200
application/font-sfnt
Font
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
http/1.1
1465.5909999274
2035.2750000311
291698
290916
200
application/font-sfnt
Font
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
http/1.1
1652.5559999282
2566.0830000415
92009
91245
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
http/1.1
1652.6519999607
1967.0100000221
113901
113139
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
http/1.1
1652.9650000157
1898.9359999541
281523
280759
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
http/1.1
1653.2149999402
2361.7569999769
187832
187072
200
image/svg+xml
Image
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
http/1.1
1653.3969999291
2213.9390000375
280740
279977
200
image/svg+xml
Image
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
http/1.1
1654.8330000369
1946.1819999851
79857
79072
200
application/font-woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
724.586
10.821
1445.903
9.559
1455.677
45.188
1626.8
12.426
1639.473
15.026
1865.017
5.004
1870.08
7.092
1900.948
38.28
1942.28
9.156
1951.653
6.267
1969.094
11.767
2000.335
6.386
2074.281
5.481
2215.596
20.734
2363.521
24.233
2388.844
5.435
2567.723
7.499
2711.583
5.675
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Torproject.org should consider lazy-loading offscreen and hidden images.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Torproject.org should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Torproject.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://torproject.org/
630
https://www.torproject.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Torproject.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.torproject.org/static/js/popper.min.js?h=a4336719
174
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
169
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 239 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
239
Maximum DOM Depth
13
Maximum Child Elements
16
Avoid chaining critical requests — 14 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Torproject.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
622.096
7.308
0
https://www.torproject.org/
552.384
13.912
4.816
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
70.848
46.6
6.216
Minimizes main-thread work — 1.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
482.692
Other
478.544
Rendering
194.704
Script Evaluation
113.68
Parse HTML & CSS
62.572
Script Parsing & Compilation
18.168
Keep request counts low and transfer sizes small — 34 requests • 3,044 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
34
3117312
Image
16
1647111
Font
7
1225578
Script
7
192825
Stylesheet
2
45775
Document
1
5609
Other
1
414
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0089821687597565
0.0030692837973037
0.0022076776594332
0.0017360009582299
0.00032263331943088
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.torproject.org/
1453
90
Unattributable
1543
77
https://www.torproject.org/static/js/popper.min.js?h=a4336719
5790
60
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
4260
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of torproject.org on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.

Other

Eliminate render-blocking resources — Potential savings of 420 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Torproject.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
330
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
12568
180
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Torproject.org should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
6080
Reduce unused CSS — Potential savings of 42 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Torproject.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
33207
30811
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
12568
12472
Reduce unused JavaScript — Potential savings of 110 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
87419
57996
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
70216
54833
Enable text compression — Potential savings of 123 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
86659
56481
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
69453
50135
https://www.torproject.org/static/js/popper.min.js?h=a4336719
19197
12290
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
6422
4299
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
3869
2337
Avoid enormous network payloads — Total size was 3,044 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
294301
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
293464
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
291698
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
281523
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
280740
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
228476
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
187832
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
113901
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
100832
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
99899
First Contentful Paint (3G) — 3720 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Largest Contentful Paint — 6.9 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 4.0 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 181 KiB
Images can slow down the page's load time. Torproject.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
227721
159368
https://www.torproject.org/static/images/yec-foreground-2x_13x.png?h=6fd7ec08
37770
26411
Serve images in next-gen formats — Potential savings of 408 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
227721
115531.7
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
100068
73391.05
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
99137
71416.3
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
70895
51240.4
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
66496
47560.55
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
63810
43942.5
https://www.torproject.org/static/images/yec-foreground-2x_13x.png?h=6fd7ec08
37770
14468.4
Reduce initial server response time — Root document took 650 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.torproject.org/
649.171
Serve static assets with an efficient cache policy — 32 resources found
Torproject.org can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.torproject.org/static/js/jquery-3.2.1.min.js?h=1055018c
3600000
87419
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
3600000
70216
https://www.torproject.org/static/css/bootstrap.css?h=90e599b0
3600000
33207
https://www.torproject.org/static/js/popper.min.js?h=a4336719
3600000
19950
https://www.torproject.org/static/fonts/fontawesome/css/all.min.css?h=9d272f6a
3600000
12568
https://www.torproject.org/static/js/scrollspy.min.js?h=02674132
3600000
7177
https://www.torproject.org/static/js/modernizr.js?h=9a7f0609
3600000
4619
https://www.torproject.org/static/js/fallback.js?h=8ecbf837
3600000
2265
https://www.torproject.org/static/js/download.js?h=caaadf8f
3600000
1179
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
86400000
281523
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
86400000
280740
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
86400000
228476
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
86400000
187832
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
86400000
113901
https://www.torproject.org/static/images/home/png/fingerprinting@3x.png?h=11fc8c97
86400000
100832
https://www.torproject.org/static/images/home/png/browse-freely@3x.png?h=23b7d7d3
86400000
99899
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
86400000
92009
https://www.torproject.org/static/images/home/png/encryption@3x.png?h=4b28f3dd
86400000
71654
https://www.torproject.org/static/images/home/png/block-trackers@3x.png?h=70991bcb
86400000
67259
https://www.torproject.org/static/images/home/png/surveillance@3x.png?h=688a829c
86400000
64570
https://www.torproject.org/static/images/yec-foreground-2x_13x.png?h=6fd7ec08
86400000
38527
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
86400000
10789
https://www.torproject.org/static/fonts/fontawesome/png/white/solid/arrow-down.png
86400000
4152
https://www.torproject.org/static/fonts/fontawesome/png/primary/solid/arrow-down.png
86400000
3974
https://www.torproject.org/static/css/images/x.svg
86400000
974
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
2592000000
294301
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
2592000000
293464
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
2592000000
291698
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
2592000000
91676
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
2592000000
87303
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
2592000000
87279
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
2592000000
79857
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Regular.ttf
399.06999992672
https://www.torproject.org/static/fonts/Space/SpaceMono-Regular.ttf
606.64899996482
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Medium.ttf
900.82699991763
https://www.torproject.org/static/fonts/Space/SpaceGrotesk-Regular.ttf
643.74999993015
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Light.ttf
1244.6939999936
https://www.torproject.org/static/fonts/SourceSansPro/SourceSansPro-Bold.ttf
569.68400010373
https://www.torproject.org/static/fonts/fontawesome/webfonts/fa-solid-900.woff2
291.34899994824
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.torproject.org/static/images/home/svg/block-trackers.svg?h=70991bcb
https://www.torproject.org/static/images/home/svg/surveillance.svg?h=688a829c
https://www.torproject.org/static/images/home/svg/fingerprinting.svg?h=11fc8c97
https://www.torproject.org/static/images/home/svg/encryption.svg?h=4b28f3dd
https://www.torproject.org/static/images/home/svg/browse-freely.svg?h=23b7d7d3
https://www.torproject.org/static/images/yec-bg-desktop-3x.png?h=fb898b61
https://www.torproject.org/static/images/tor-logo@2x.png?h=16ad42bc
https://www.torproject.org/static/images/yec-foreground-2x_13x.png?h=6fd7ec08
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of torproject.org. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Torproject.org may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
67

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that torproject.org should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.0.0-beta.2
jQuery
3.2.1
Modernizr
3.6.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.torproject.org/static/js/bootstrap.bundle.min.js?h=46d1f82f
https://www.torproject.org/static/js/bootstrap.bundle.min.js.map

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://torproject.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Refused to load the image 'data:image/svg+xml;charset=utf8,%3Csvg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath stroke='%23FFFFFF' stroke-width='2' stroke-linecap='round' stroke-miterlimit='10' d='M4 7h22M4 15h22M4 23h22'/%3E%3C/svg%3E' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Content security policy
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for torproject.org. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of torproject.org on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
Hosting

Server Location

Server IP Address: 95.216.163.36
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
Transferred to the RIPE region on 2018-08-28T00:42:30Z.
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: The Tor Project, Inc
Country: US
City: REDACTED FOR PRIVACY
State: WA
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Public Interest Registry 194.245.148.200
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 94/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.torproject.org
Issued By: R3
Valid From: 12th September, 2023
Valid To: 11th December, 2023
Subject: CN = www.torproject.org
Hash: 5af0fa32
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04DAD8A1D9476E2704878E065B070CC2DA71
Serial Number (Hex): 04DAD8A1D9476E2704878E065B070CC2DA71
Valid From: 12th September, 2024
Valid To: 11th December, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Sep 12 02:01:31.345 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D5:8E:AF:7D:8B:5D:AE:65:B8:4B:61:
F3:52:08:3A:88:57:2C:50:66:AB:A1:BA:10:49:79:BE:
F8:A7:D2:CC:32:02:21:00:AC:FA:4F:BA:2C:CD:79:61:
E5:BE:D0:BA:FD:BD:7F:5D:B9:84:21:52:49:E8:6E:0A:
C2:16:61:01:66:1B:62:1D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Sep 12 02:01:31.396 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:5F:B2:A3:70:42:14:D8:06:1A:DD:66:74:
35:F0:01:15:09:C2:99:B0:FE:00:1C:75:D9:CA:EF:48:
DF:52:CA:16:02:20:52:7C:1E:51:37:C2:00:8A:98:E7:
F2:76:2E:FB:1E:B8:A9:52:52:14:1F:9D:22:5C:E1:E9:
D6:DC:CA:DA:74:B6
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.torproject.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
torproject.org. 116.202.120.166 IN 150
torproject.org. 204.8.99.144 IN 150
torproject.org. 95.216.163.36 IN 150
torproject.org. 116.202.120.165 IN 150
torproject.org. 204.8.99.146 IN 150

NS Records

Host Nameserver Class TTL
torproject.org. ns3.torproject.org. IN 21600
torproject.org. nsp.dnsnode.net. IN 21600
torproject.org. ns4.torproject.org. IN 21600
torproject.org. ns1.torproject.org. IN 21600
torproject.org. ns5.torproject.org. IN 21600

AAAA Records

IP Address Class TTL
2620:7:6002:0:466:39ff:fe7f:1826 IN 150
2a01:4f8:fff0:4f:266:37ff:feae:3bbc IN 150
2a01:4f9:c010:19eb::1 IN 150
2620:7:6002:0:466:39ff:fe32:e3dd IN 150
2a01:4f8:fff0:4f:266:37ff:fe2c:5d19 IN 150

CAA Records

Domain Flags Tag Class TTL
globalsign.com 128 issue IN 3600
letsencrypt.org 128 issue IN 3600
; 128 issuewild IN 3600
mailto:torproject-admin@torproject.org 0 iodef IN 3600

MX Records

Priority Host Server Class TTL
10 torproject.org. eugeni.torproject.org. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
torproject.org. nevii.torproject.org. hostmaster.torproject.org. 3600

TXT Records

Host Value Class TTL
torproject.org. v=spf1 IN 3600
torproject.org. google-site-verification=YeQsuz0lo1q00m6KE1lpJX7hHBzriDpcMHr_f9q2Ag8 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 28th September, 2023
Server: Apache
Cache-Control: max-age=3600
Expires: 28th September, 2023
Content-Type: text/html
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
X-Xss-Protection: 1
Referrer-Policy: no-referrer
Strict-Transport-Security: max-age=15768000; preload
Onion-Location: http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/index.html
Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline';
Last-Modified: 7th September, 2023
ETag: "5351-604cb69075449"
Accept-Ranges: bytes
Content-Length: 21329
Vary: Accept-Encoding
Content-Language: en

Whois Lookup

Created: 17th October, 2006
Changed: 20th September, 2023
Expires: 17th October, 2027
Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com a German GmbH
Status: clientTransferProhibited
Nameservers: ns1.torproject.org
ns3.torproject.org
ns4.torproject.org
ns5.torproject.org
Owner Name: REDACTED FOR PRIVACY
Owner Organization: The Tor Project, Inc
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: WA
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: torproject.org
Registry Domain ID: 087e71f0459146cfb39100d275ecff82-LROR
Registrar WHOIS Server: http://whois.joker.com
Registrar URL: http://www.joker.com
Updated Date: 2023-09-20T17:05:48Z
Creation Date: 2006-10-17T22:02:50Z
Registry Expiry Date: 2027-10-17T22:02:50Z
Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com a German GmbH
Registrar IANA ID: 113
Registrar Abuse Contact Email: abuse@joker.com
Registrar Abuse Contact Phone: +49.21186767447
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: The Tor Project, Inc
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: WA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns4.torproject.org
Name Server: ns5.torproject.org
Name Server: ns1.torproject.org
Name Server: ns3.torproject.org
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-09-28T11:41:15Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
ns1.torproject.org 204.8.99.145
ns3.torproject.org 204.8.99.145
ns4.torproject.org 49.12.57.135
ns5.torproject.org 89.47.185.6
Related

Similar Sites

Domain Valuation Snoop Score
$10 USD 1/5
$36,944 USD 3/5
$323,046 USD 3/5
0/5
$55,190 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address