2.6 sec in total
380 ms
2 sec
197 ms
Visit torproject.us now to see the best up-to-date Torproject content and also check out these interesting facts you probably never knew about torproject.us
Visit torproject.usWe analyzed Torproject.us page load time and found that the first response time was 380 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
torproject.us performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value7.4 s
4/100
25%
Value2.8 s
96/100
10%
Value40 ms
100/100
30%
Value0.257
48/100
15%
Value7.6 s
46/100
10%
380 ms
627 ms
120 ms
234 ms
352 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Torproject.us, 97% (30 requests) were made to Torproject.org. The less responsive or slowest element that took the longest time to load (627 ms) relates to the external source Torproject.org.
Page size can be reduced by 43.7 kB (27%)
160.7 kB
117.0 kB
In fact, the total size of Torproject.us main page is 160.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 115.1 kB which makes up the majority of the site volume.
Potential reduce by 11.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 3.8 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.4 kB or 79% of the original size.
Potential reduce by 7.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Torproject images are well optimized though.
Potential reduce by 25.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Torproject.us needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 80% of the original size.
Number of requests can be reduced by 8 (28%)
29
21
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Torproject. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
torproject.us
380 ms
www.torproject.org
627 ms
master.css
120 ms
icon-TorBrowser.jpg
234 ms
icon-Orbot.jpg
352 ms
tails_logo.png
370 ms
icon-Arm.jpg
372 ms
icon-TorStatus.jpg
376 ms
icon-Obfsproxy.jpg
375 ms
icon-stem.jpg
397 ms
icon-OONI.png
468 ms
family.jpg
490 ms
consumers.jpg
493 ms
activists.jpg
495 ms
media.jpg
496 ms
military.jpg
528 ms
onion.jpg
584 ms
InternetDefenseLeague-footer-badge.png
611 ms
reset.css
501 ms
layout.css
506 ms
typography.css
504 ms
tor-logo.jpg
119 ms
bg-nav-hover.jpg
134 ms
cta-buttons.jpg
124 ms
bg-banner.jpg
129 ms
banner-gradient.jpg
128 ms
white-bullet.png
126 ms
button-download.png
350 ms
button-download-arrow.png
246 ms
table-head.jpg
245 ms
table-arrow.jpg
246 ms
torproject.us accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
torproject.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
torproject.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torproject.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Torproject.us main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
torproject.us
Open Graph description is not detected on the main page of Torproject. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: