Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

spitzenstadt.de

Spitzenstadt.de – Das Online-Magazin für Plauen und das Vogtland

Page Load Speed

6.7 sec in total

First Response

477 ms

Resources Loaded

5.2 sec

Page Rendered

1.1 sec

spitzenstadt.de screenshot

About Website

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

Das Online-Stadtmagazin für Plauen mit aktuellen Nachrichten und Informationen aus der Spitzenstadt im Vogtland.

Visit spitzenstadt.de

Key Findings

We analyzed Spitzenstadt.de page load time and found that the first response time was 477 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

spitzenstadt.de performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,240 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.418

24/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

spitzenstadt.de

477 ms

www.spitzenstadt.de

827 ms

139 ms

analytics.js

39 ms

gen-light

133 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 38% of them (53 requests) were addressed to the original Spitzenstadt.de, 14% (20 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Player.nowonscreen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 599.8 kB (31%)

Content Size

2.0 MB

After Optimization

1.4 MB

In fact, the total size of Spitzenstadt.de main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 74.6 kB

  • Original 91.1 kB
  • After minification 83.1 kB
  • After compression 16.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 74.6 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 108.7 kB

  • Original 1.3 MB
  • After minification 1.1 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. Spitzenstadt images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 218.1 kB

  • Original 380.2 kB
  • After minification 322.7 kB
  • After compression 162.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 218.1 kB or 57% of the original size.

CSS Optimization

-84%

Potential reduce by 198.3 kB

  • Original 235.7 kB
  • After minification 185.3 kB
  • After compression 37.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. Spitzenstadt.de needs all CSS files to be minified and compressed as it can save up to 198.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (60%)

Requests Now

132

After Optimization

53

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

Accessibility Review

spitzenstadt.de accessibility score

74

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

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

spitzenstadt.de best practices score

77

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

spitzenstadt.de SEO score

84

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 Spitzenstadt.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 Spitzenstadt.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 Spitzenstadt. 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: