Tools & Wizards About Us
willileaks.de screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

willileaks.de

NEO MAGAZIN ROYALE mit Jan Böhmermann - ZDFmediathek

Page Load Speed

6.6 sec in total

First Response

380 ms

Resources Loaded

5.5 sec

Page Rendered

672 ms

willileaks.de screenshot

About Website

Visit willileaks.de now to see the best up-to-date Willileaks content for Germany and also check out these interesting facts you probably never knew about willileaks.de

Jan Böhmermann begrüßt prominente Gäste und beschäftigt sich satirisch, intelligent und humorvoll mit dem Zeitgeschehen im NEO MAGAZIN ROYALE

Visit willileaks.de

Key Findings

We analyzed Willileaks.de page load time and found that the first response time was 380 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

willileaks.de performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value3,910 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

willileaks.de

380 ms

www.neomagazin.de

240 ms

2855 ms

otSDKStub.js

443 ms

abGroupLibrary.js

239 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Willileaks.de, 71% (17 requests) were made to Zdf.de and 13% (3 requests) were made to Cmp.zdf.de. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Zdf.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 669.0 kB (70%)

Content Size

956.8 kB

After Optimization

287.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Willileaks.de main page is 956.8 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. 65% of websites need less resources to load. HTML takes 784.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 666.9 kB

  • Original 784.5 kB
  • After minification 676.8 kB
  • After compression 117.6 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 107.7 kB, which is 14% 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 666.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 23.7 kB
  • After minification 23.7 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. Willileaks images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 2.1 kB

  • Original 38.2 kB
  • After minification 38.2 kB
  • After compression 36.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 110.4 kB
  • After minification 110.4 kB
  • After compression 110.4 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. Willileaks.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Willileaks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

willileaks.de

willileaks.de

380 ms

www.neomagazin.de

www.neomagazin.de

240 ms

2855 ms

otSDKStub.js

otSDKStub.js

443 ms

abGroupLibrary.js

abGroupLibrary.js

239 ms

styles.css

styles.css

478 ms

d2ba7782-831d-4b39-846e-58f275678494.json

d2ba7782-831d-4b39-846e-58f275678494.json

448 ms

_app-polyfills.pkg.js

_app-polyfills.pkg.js

472 ms

_crucial-behavior.pkg.js

_crucial-behavior.pkg.js

469 ms

_app-behavior.pkg.js

_app-behavior.pkg.js

937 ms

iam.js

iam.js

928 ms

smarttag.js

smarttag.js

926 ms

det.png

det.png

174 ms

otBannerSdk.js

otBannerSdk.js

949 ms

ZDFType-Light.ttf

ZDFType-Light.ttf

154 ms

ZDFType-ExtraLight.ttf

ZDFType-ExtraLight.ttf

458 ms

ZDFType-Thin.ttf

ZDFType-Thin.ttf

454 ms

ZDFType-Regular.ttf

ZDFType-Regular.ttf

454 ms

ZDFType-Medium.ttf

ZDFType-Medium.ttf

454 ms

ZDFType-Bold.ttf

ZDFType-Bold.ttf

689 ms

ZDFType-SemiBold.ttf

ZDFType-SemiBold.ttf

855 ms

ZDFType-Heavy.ttf

ZDFType-Heavy.ttf

618 ms

ZDFType-Black.ttf

ZDFType-Black.ttf

687 ms

zdf-iconfont.woff

zdf-iconfont.woff

614 ms

Accessibility Review

willileaks.de accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Best Practices

willileaks.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

willileaks.de SEO score

99

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Willileaks.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Willileaks.de 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

willileaks.de

Open Graph data is detected on the main page of Willileaks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: