Tools & Wizards About Us
staedtetag.de screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

staedtetag.de

Deutscher Städtetag – die Stimme der Städte: Deutscher Städtetag

Page Load Speed

4.1 sec in total

First Response

322 ms

Resources Loaded

3.2 sec

Page Rendered

539 ms

staedtetag.de screenshot

About Website

Click here to check amazing Staedtetag content for Germany. Otherwise, check out these important facts you probably never knew about staedtetag.de

Der Deutsche Städtetag ist die Stimme der Städte und der kommunale Spitzenverband der kreisfreien sowie der meisten kreisangehörigen deutschen Städte.

Visit staedtetag.de

Key Findings

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

Performance Metrics

staedtetag.de performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

staedtetag.de

322 ms

staedtetag.de

396 ms

www.staedtetag.de

1413 ms

merged-ddaf9764ddcfd947651822079044646c-daa5fa1c161645d4e11ae46b3347f552.css

296 ms

merged-3096572245793fe88bffba89af23a3f2-f9d7e66784b9039cabfb1d58b7d04122.js

398 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that all of those requests were addressed to Staedtetag.de and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Staedtetag.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.3 kB (50%)

Content Size

569.4 kB

After Optimization

285.0 kB

  • HTML
  • Images

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

HTML Optimization

-89%

Potential reduce by 284.3 kB

  • Original 318.9 kB
  • After minification 203.3 kB
  • After compression 34.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 115.6 kB, which is 36% 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 284.3 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 250.5 kB
  • After minification 250.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. Staedtetag images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

staedtetag.de

staedtetag.de

322 ms

staedtetag.de

staedtetag.de

396 ms

www.staedtetag.de

www.staedtetag.de

1413 ms

merged-ddaf9764ddcfd947651822079044646c-daa5fa1c161645d4e11ae46b3347f552.css

merged-ddaf9764ddcfd947651822079044646c-daa5fa1c161645d4e11ae46b3347f552.css

296 ms

merged-3096572245793fe88bffba89af23a3f2-f9d7e66784b9039cabfb1d58b7d04122.js

merged-3096572245793fe88bffba89af23a3f2-f9d7e66784b9039cabfb1d58b7d04122.js

398 ms

earlyLoaded-10e02c602f71fa2a88b81a19359fdf6c.js

earlyLoaded-10e02c602f71fa2a88b81a19359fdf6c.js

397 ms

merged-9e49536e77fcfcbe07138abc04885d19-8d79b4e43efb3501a29e80bdeec170bb.js

merged-9e49536e77fcfcbe07138abc04885d19-8d79b4e43efb3501a29e80bdeec170bb.js

414 ms

merged-117d1fb81eb4a4c16312402309cda6c4-39b524911b111dac80f14667d949473b.js

merged-117d1fb81eb4a4c16312402309cda6c4-39b524911b111dac80f14667d949473b.js

723 ms

svg-sprite-22dfe4f1.svg

svg-sprite-22dfe4f1.svg

120 ms

csm_sindelfingen-panorama-buehne_9741d0f5cc.jpg

csm_sindelfingen-panorama-buehne_9741d0f5cc.jpg

719 ms

titillium-web-v8-latin-regular.woff

titillium-web-v8-latin-regular.woff

109 ms

titillium-web-v8-latin-300.woff

titillium-web-v8-latin-300.woff

111 ms

titillium-web-v8-latin-200.woff

titillium-web-v8-latin-200.woff

111 ms

titillium-web-v8-latin-600.woff

titillium-web-v8-latin-600.woff

308 ms

titillium-web-v8-latin-700.woff

titillium-web-v8-latin-700.woff

193 ms

titillium-web-v8-latin-900.woff

titillium-web-v8-latin-900.woff

226 ms

rubik-v9-latin-regular.woff

rubik-v9-latin-regular.woff

226 ms

rubik-v9-latin-500.woff

rubik-v9-latin-500.woff

497 ms

rubik-v9-latin-300.woff

rubik-v9-latin-300.woff

498 ms

rubik-v9-latin-700.woff

rubik-v9-latin-700.woff

497 ms

rubik-v9-latin-900.woff

rubik-v9-latin-900.woff

581 ms

Accessibility Review

staedtetag.de accessibility score

78

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

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

staedtetag.de best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

staedtetag.de SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

staedtetag.de

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