Tools & Wizards About Us
stadtplan.net screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

stadtplan.net

Stadtplan: Kartografie und Stadtpläne auf stadtplan.net

Page Load Speed

2.7 sec in total

First Response

210 ms

Resources Loaded

2.3 sec

Page Rendered

246 ms

stadtplan.net screenshot

About Website

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

stadtplan.net bietet Ihnen präzise Stadtpläne und Kartografie mit aktuellen Informationen und benutzerfreundlichen Funktionen für die schnelle Orientierung vor Ort.

Visit stadtplan.net

Key Findings

We analyzed Stadtplan.net page load time and found that the first response time was 210 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

stadtplan.net performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value4.7 s

70/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

stadtplan.net

210 ms

stadtplan.net

388 ms

www.stadtplan.net

406 ms

general_structure.css

192 ms

jquery-ui-1.10.4.css

282 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 87% of them (20 requests) were addressed to the original Stadtplan.net, 9% (2 requests) were made to Apis.google.com and 4% (1 request) were made to Consent.cookiefirst.com. The less responsive or slowest element that took the longest time to load (648 ms) belongs to the original domain Stadtplan.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.3 kB (3%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stadtplan.net main page is 1.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. 30% of websites need less resources to load. Images take 922.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 8.2 kB

  • Original 11.0 kB
  • After minification 8.7 kB
  • After compression 2.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 2.3 kB, which is 21% 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 8.2 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 373 B

  • Original 922.0 kB
  • After minification 921.6 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. Stadtplan images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.0 kB

  • Original 233.2 kB
  • After minification 232.6 kB
  • After compression 228.2 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

-63%

Potential reduce by 24.7 kB

  • Original 39.3 kB
  • After minification 18.1 kB
  • After compression 14.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. Stadtplan.net needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (70%)

Requests Now

20

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stadtplan.net

stadtplan.net

210 ms

stadtplan.net

stadtplan.net

388 ms

www.stadtplan.net

www.stadtplan.net

406 ms

general_structure.css

general_structure.css

192 ms

jquery-ui-1.10.4.css

jquery-ui-1.10.4.css

282 ms

general_dynamic.php

general_dynamic.php

288 ms

empty.css

empty.css

281 ms

tablet.css

tablet.css

283 ms

mobile.css

mobile.css

284 ms

noimage.css

noimage.css

286 ms

lang.js.php

lang.js.php

382 ms

stadtplan.js

stadtplan.js

379 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

477 ms

jquery-ui.min.js

jquery-ui.min.js

580 ms

plusone.js

plusone.js

23 ms

jquery.cookie.js

jquery.cookie.js

376 ms

jquery.main.js

jquery.main.js

382 ms

banner.js

banner.js

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

logo.png

logo.png

95 ms

SN-Startbild-01-Himmel-NG.jpg

SN-Startbild-01-Himmel-NG.jpg

648 ms

icon-home-background.png

icon-home-background.png

94 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

95 ms

Accessibility Review

stadtplan.net accessibility score

79

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

stadtplan.net 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

SEO Factors

stadtplan.net 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 Stadtplan.net 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 Stadtplan.net 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

stadtplan.net

Open Graph description is not detected on the main page of 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: