Access wikileak.com.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

wikileak.com

119 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Wikileak.com and no external sources were called. The less responsive or slowest element that took the longest time to load (119 ms) belongs to the original domain Wikileak.com.

Content Size

107.0 kB

After Optimization

83.3 kB

In fact, the total size of Wikileak.com main page is 107.0 kB. 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. Javascripts take 75.1 kB which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 399 B

Original 885 B
After minification 796 B
After compression 486 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 399 B or 45% of the original size.

Image Optimization

-31%

Potential reduce by 9.6 kB

Original 31.1 kB
After minification 21.5 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. Obviously, Wikileak needs image optimization as it can save up to 9.6 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 13.7 kB

Original 75.1 kB
After minification 70.2 kB
After compression 61.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 13.7 kB or 18% 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

High

<frame> or <iframe> elements do not have a title

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

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

robots.txt is not valid

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wikileak.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), while the claimed language is English. Our system also found out that Wikileak.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 Wikileak. 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: