Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 44

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 74

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

2.1 sec in total

First Response

297 ms

Resources Loaded

1.7 sec

Page Rendered

107 ms

m.unser-stadtplan.de screenshot

About Website

Welcome to m.unser-stadtplan.de homepage info - get ready to check M Unser Stadtplan best content for Germany right away, or after learning these important things about m.unser-stadtplan.de

Visit m.unser-stadtplan.de

Key Findings

We analyzed M.unser-stadtplan.de page load time and found that the first response time was 297 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

m.unser-stadtplan.de performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.336

33/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

m.unser-stadtplan.de

297 ms

m.unser-stadtplan.de

429 ms

frontpage

498 ms

style_common.css

97 ms

style_desktop.css

193 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original M.unser-stadtplan.de, 50% (8 requests) were made to Unser-stadtplan.de and 19% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (498 ms) relates to the external source Unser-stadtplan.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.4 kB (64%)

Content Size

152.7 kB

After Optimization

54.3 kB

In fact, the total size of M.unser-stadtplan.de main page is 152.7 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. 15% of websites need less resources to load. Javascripts take 106.9 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.6 kB

  • Original 2.8 kB
  • After minification 2.4 kB
  • After compression 1.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 341 B, which is 12% 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 1.6 kB or 58% of the original size.

Image Optimization

-1%

Potential reduce by 130 B

  • Original 20.2 kB
  • After minification 20.1 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. M Unser Stadtplan images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 78.2 kB

  • Original 106.9 kB
  • After minification 63.3 kB
  • After compression 28.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 78.2 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 18.5 kB

  • Original 22.8 kB
  • After minification 15.9 kB
  • After compression 4.3 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. M.unser-stadtplan.de needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

10

After Optimization

7

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Unser Stadtplan. 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.

Accessibility Review

m.unser-stadtplan.de accessibility score

44

Accessibility Issues

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

m.unser-stadtplan.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

SEO Factors

m.unser-stadtplan.de SEO score

74

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.unser-stadtplan.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that M.unser-stadtplan.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 M Unser Stadtplan. 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: