Access torify.com. torify.com

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

91/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

torify.com

123 ms

ww2.torify.com

630 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Torify.com, 50% (1 request) were made to Ww2.torify.com. The less responsive or slowest element that took the longest time to load (630 ms) relates to the external source Ww2.torify.com.

Content Size

51 B

After Optimization

33 B

In fact, the total size of Torify.com main page is 51 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 51 B which makes up the majority of the site volume.

HTML Optimization

-35%

Potential reduce by 18 B

Original 51 B
After minification 39 B
After compression 33 B

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 12 B, which is 24% 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 18 B or 35% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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

High

Document doesn't have a <title> element

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Search Engine Optimization Advices

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

High

Document doesn't have a <title> element

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torify.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Torify.com 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Torify. 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: