Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dtver.de

Deutscher Theater-Verlag : Theater, Amateurtheater, Schultheater, professionelle Bühne

Page Load Speed

3.8 sec in total

First Response

384 ms

Resources Loaded

3.2 sec

Page Rendered

200 ms

About Website

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

Deutscher Theaterverlag. Bei uns erhalten Sie Theaterstücke und Fachliteratur für Amateurtheater, Schultheater und professionelle Bühnen.

Visit dtver.de

Key Findings

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

Performance Metrics

dtver.de performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

dtver.de

384 ms

www.dtver.de

741 ms

screen.css

298 ms

slick.css

300 ms

slick-theme.css

300 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 75% of them (41 requests) were addressed to the original Dtver.de, 7% (4 requests) were made to Cdnjs.cloudflare.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Dtver.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.1 kB (2%)

Content Size

17.4 MB

After Optimization

17.0 MB

In fact, the total size of Dtver.de main page is 17.4 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. 65% of websites need less resources to load. Images take 17.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 45.7 kB

  • Original 53.9 kB
  • After minification 43.0 kB
  • After compression 8.2 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 10.9 kB, which is 20% 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 45.7 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 306.9 kB

  • Original 17.2 MB
  • After minification 16.9 MB

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. Dtver images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 30.9 kB

  • Original 88.6 kB
  • After minification 88.6 kB
  • After compression 57.7 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 30.9 kB or 35% of the original size.

CSS Optimization

-15%

Potential reduce by 3.7 kB

  • Original 24.9 kB
  • After minification 24.9 kB
  • After compression 21.2 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. Dtver.de needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (30%)

Requests Now

47

After Optimization

33

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

Accessibility Review

dtver.de accessibility score

77

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dtver.de SEO score

92

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