Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ndr2.de

NDR 2 Homepage | NDR.de - NDR 2

Page Load Speed

3 sec in total

First Response

342 ms

Resources Loaded

2.1 sec

Page Rendered

524 ms

ndr2.de screenshot

About Website

Click here to check amazing NDR 2 content. Otherwise, check out these important facts you probably never knew about ndr2.de

Hier informieren wir über das Programm, Events, Aktionen und neue Musik in der Playlist von NDR 2.

Visit ndr2.de

Key Findings

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

Performance Metrics

ndr2.de performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

ndr2.de

342 ms

406 ms

ndrmerged.css

38 ms

ndrde_base.js

164 ms

scripts.js

33 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ndr2.de, 72% (39 requests) were made to Ndr.de and 15% (8 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (822 ms) relates to the external source De.sitestat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 690.1 kB (45%)

Content Size

1.5 MB

After Optimization

835.1 kB

In fact, the total size of Ndr2.de main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 657.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 76.4 kB

  • Original 93.9 kB
  • After minification 91.8 kB
  • After compression 17.5 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. 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 76.4 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 13.1 kB

  • Original 657.3 kB
  • After minification 644.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. NDR 2 images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 337.8 kB

  • Original 457.9 kB
  • After minification 395.5 kB
  • After compression 120.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 337.8 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 262.9 kB

  • Original 316.2 kB
  • After minification 261.5 kB
  • After compression 53.3 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. Ndr2.de needs all CSS files to be minified and compressed as it can save up to 262.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (19%)

Requests Now

48

After Optimization

39

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NDR 2. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ndr2.de accessibility score

98

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.

Best Practices

ndr2.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

ndr2.de SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Ndr2.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 Ndr2.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

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