Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

nationaltheater-weimar.de

Deutsches Nationaltheater und Staatskapelle Weimar DNT

Page Load Speed

5.1 sec in total

First Response

432 ms

Resources Loaded

4 sec

Page Rendered

682 ms

nationaltheater-weimar.de screenshot

About Website

Welcome to nationaltheater-weimar.de homepage info - get ready to check Nationaltheater Weimar best content for Germany right away, or after learning these important things about nationaltheater-weimar.de

Deutsches Nationaltheater & Staatskapelle Weimar GmbH - Staatstheater Thüringen. Das DNT: Schauspiel, Musiktheater, Sinfoniekonzert, Orchester.

Visit nationaltheater-weimar.de

Key Findings

We analyzed Nationaltheater-weimar.de page load time and found that the first response time was 432 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

nationaltheater-weimar.de performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value1.139

1/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

nationaltheater-weimar.de

432 ms

www.nationaltheater-weimar.de

1262 ms

uc.js

30 ms

screen.css

223 ms

modernizr.js

311 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Nationaltheater-weimar.de, 2% (1 request) were made to Consent.cookiebot.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Nationaltheater-weimar.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.8 kB (13%)

Content Size

4.2 MB

After Optimization

3.7 MB

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

HTML Optimization

-91%

Potential reduce by 99.0 kB

  • Original 109.3 kB
  • After minification 91.3 kB
  • After compression 10.3 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 18.0 kB, which is 16% 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 99.0 kB or 91% of the original size.

Image Optimization

-9%

Potential reduce by 342.3 kB

  • Original 3.9 MB
  • After minification 3.5 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. Nationaltheater Weimar images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 88.3 kB

  • Original 221.2 kB
  • After minification 221.2 kB
  • After compression 132.8 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 88.3 kB or 40% of the original size.

CSS Optimization

-1%

Potential reduce by 230 B

  • Original 43.8 kB
  • After minification 43.8 kB
  • After compression 43.6 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. Nationaltheater-weimar.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (8%)

Requests Now

49

After Optimization

45

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

Accessibility Review

nationaltheater-weimar.de accessibility score

80

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

nationaltheater-weimar.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nationaltheater-weimar.de SEO score

91

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

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 Nationaltheater-weimar.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 Nationaltheater-weimar.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 Nationaltheater Weimar. 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: