Report Summary

  • 20

    Performance

    Renders faster than
    37% 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

  • 85

    SEO

    Google-friendlier than
    55% of websites

schwerin.de

Startseite - Landeshauptstadt Schwerin

Page Load Speed

6 sec in total

First Response

396 ms

Resources Loaded

4.9 sec

Page Rendered

669 ms

schwerin.de screenshot

About Website

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

Herzlich willkommen auf dem Stadtportal der Landeshauptstadt Schwerin. Hier finden Sie schnell und übersichtlich Informationen für Touristen, Bürger und Unternehmer.

Visit schwerin.de

Key Findings

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

Performance Metrics

schwerin.de performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

schwerin.de

396 ms

www.schwerin.de

703 ms

loader.js

84 ms

uc-block.bundle.js

50 ms

js

71 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 92% of them (133 requests) were addressed to the original Schwerin.de, 1% (2 requests) were made to App.eu.usercentrics.eu and 1% (2 requests) were made to Cdn.eye-able.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Schwerin.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 521.6 kB (7%)

Content Size

7.5 MB

After Optimization

7.0 MB

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

HTML Optimization

-89%

Potential reduce by 288.3 kB

  • Original 325.0 kB
  • After minification 280.8 kB
  • After compression 36.8 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 44.3 kB, which is 14% 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 288.3 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 209.6 kB

  • Original 6.6 MB
  • After minification 6.4 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. Schwerin images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 19.6 kB

  • Original 540.6 kB
  • After minification 540.6 kB
  • After compression 521.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 4.1 kB

  • Original 64.0 kB
  • After minification 64.0 kB
  • After compression 59.8 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. Schwerin.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (26%)

Requests Now

133

After Optimization

98

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

Accessibility Review

schwerin.de accessibility score

78

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

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

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

schwerin.de SEO score

85

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

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 Schwerin.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 Schwerin.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 Schwerin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: