Tools & Wizards About Us
potsdamer-stadtplan.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

potsdamer-stadtplan.com

Stadtplan Potsdam - Potsdam Hauptbahnhof Potsdam, Potsdam

Page Load Speed

3.5 sec in total

First Response

323 ms

Resources Loaded

3.1 sec

Page Rendered

94 ms

potsdamer-stadtplan.com screenshot

About Website

Visit potsdamer-stadtplan.com now to see the best up-to-date Potsdam Er Stadtplan content for Germany and also check out these interesting facts you probably never knew about potsdamer-stadtplan.com

Stadtplan Potsdam. Schöne detaillierte Potsdam Karte. Finden Sie Hotels, Restaurants, Museen. Mit GPS-Unterstützung und Ausdruck als PDF.

Visit potsdamer-stadtplan.com

Key Findings

We analyzed Potsdamer-stadtplan.com page load time and found that the first response time was 323 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

potsdamer-stadtplan.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

www.potsdamer-stadtplan.com

323 ms

dp1.css

268 ms

dp139.js

284 ms

show_ads.js

68 ms

adsbygoogle.js

164 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Potsdamer-stadtplan.com, 23% (11 requests) were made to Pharus.eu and 21% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (713 ms) relates to the external source Pharus.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 357.1 kB (38%)

Content Size

948.0 kB

After Optimization

590.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Potsdamer-stadtplan.com main page is 948.0 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. 50% of websites need less resources to load. Javascripts take 854.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 37.8 kB

  • Original 49.5 kB
  • After minification 48.5 kB
  • After compression 11.7 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 37.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 38.1 kB
  • After minification 38.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. Potsdam Er Stadtplan images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 319.2 kB

  • Original 854.3 kB
  • After minification 854.3 kB
  • After compression 535.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 319.2 kB or 37% of the original size.

CSS Optimization

-1%

Potential reduce by 58 B

  • Original 6.1 kB
  • After minification 6.1 kB
  • After compression 6.1 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. Potsdamer-stadtplan.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (54%)

Requests Now

39

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.potsdamer-stadtplan.com

www.potsdamer-stadtplan.com

323 ms

dp1.css

dp1.css

268 ms

dp139.js

dp139.js

284 ms

show_ads.js

show_ads.js

68 ms

adsbygoogle.js

adsbygoogle.js

164 ms

dp1.css

dp1.css

468 ms

dp139.js

dp139.js

713 ms

t.gif

t.gif

117 ms

www.ranking-hits.de

www.ranking-hits.de

286 ms

berlin.png

berlin.png

346 ms

adsbygoogle.js

adsbygoogle.js

143 ms

show_ads_impl.js

show_ads_impl.js

250 ms

bg.gif

bg.gif

118 ms

bm.png

bm.png

113 ms

ba.png

ba.png

219 ms

bw.png

bw.png

221 ms

nd.png

nd.png

340 ms

bp.png

bp.png

341 ms

handopen.cur

handopen.cur

161 ms

www.ranking-hits.de

www.ranking-hits.de

449 ms

zrt_lookup.html

zrt_lookup.html

29 ms

ads

ads

460 ms

ads

ads

381 ms

ads

ads

694 ms

ads

ads

232 ms

ax2.gif

ax2.gif

118 ms

12d95d4c7f28e5d768e0b461a4598061.js

12d95d4c7f28e5d768e0b461a4598061.js

27 ms

load_preloaded_resource.js

load_preloaded_resource.js

54 ms

5cad5a605d634f684c7cf1ecfca85228.js

5cad5a605d634f684c7cf1ecfca85228.js

38 ms

abg_lite.js

abg_lite.js

55 ms

window_focus.js

window_focus.js

61 ms

qs_click_protection.js

qs_click_protection.js

70 ms

ufs_web_display.js

ufs_web_display.js

19 ms

c653839755d9d9a3a773c62a0253f53f.js

c653839755d9d9a3a773c62a0253f53f.js

53 ms

icon.png

icon.png

192 ms

s

s

176 ms

14763004658117789537

14763004658117789537

258 ms

css

css

135 ms

activeview

activeview

224 ms

activeview

activeview

200 ms

css

css

89 ms

d4Vwwu8iHiCDxZ1xzxUGRbEaLZqCebWmAfX3l2eV90k.js

d4Vwwu8iHiCDxZ1xzxUGRbEaLZqCebWmAfX3l2eV90k.js

16 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

190 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

191 ms

activeview

activeview

91 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

74 ms

sodar

sodar

73 ms

Accessibility Review

potsdamer-stadtplan.com accessibility score

80

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

potsdamer-stadtplan.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

potsdamer-stadtplan.com SEO score

75

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

High

Page is blocked from indexing

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 Potsdamer-stadtplan.com 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 Potsdamer-stadtplan.com 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

potsdamer-stadtplan.com

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