4.5 sec in total
702 ms
2.8 sec
1 sec
Click here to check amazing Tramgeschichten content for Germany. Otherwise, check out these important facts you probably never knew about tramgeschichten.de
Write an awesome description for your new site here. You can edit this line in _config.yml. It will appear in your document head meta (for Google search results) and in your feed.xml site description.
Visit tramgeschichten.deWe analyzed Tramgeschichten.de page load time and found that the first response time was 702 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tramgeschichten.de performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value2.5 s
98/100
10%
Value150 ms
94/100
30%
Value0
100/100
15%
Value1.5 s
100/100
10%
702 ms
261 ms
5 ms
539 ms
162 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 48% of them (24 requests) were addressed to the original Tramgeschichten.de, 20% (10 requests) were made to C2.staticflickr.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source C2.staticflickr.com.
Page size can be reduced by 72.2 kB (5%)
1.3 MB
1.3 MB
In fact, the total size of Tramgeschichten.de main page is 1.3 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 43.6 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 43.6 kB or 79% of the original size.
Potential reduce by 9.2 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. Tramgeschichten images are well optimized though.
Potential reduce by 9.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 9.8 kB or 30% of the original size.
Potential reduce by 9.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. Tramgeschichten.de needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 79% of the original size.
Number of requests can be reduced by 18 (37%)
49
31
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tramgeschichten. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
www.tramgeschichten.de
702 ms
style-winter.css
261 ms
show_ads.js
5 ms
15084204180_fb876b5077.jpg
539 ms
main-bg.gif
162 ms
content-bg.gif
158 ms
header-schnee.jpg
402 ms
header-icon-tram.gif
292 ms
nav-button-bg.gif
284 ms
netzplan.png
401 ms
sammlung-avenio.png
454 ms
ubahnnetz.png
422 ms
25389293280_65fdd4fd3a.jpg
760 ms
24672780713_5044c99852.jpg
1008 ms
24832105749_e5fb943fe5.jpg
946 ms
24811265119_ae0226a781.jpg
948 ms
12242972303_2fef36a642.jpg
1146 ms
24403079153_7fee047acb.jpg
1041 ms
24291581590_af03cccba6.jpg
987 ms
24562689236_c3d91d3af2.jpg
1231 ms
24268884550_1febd3b561.jpg
1223 ms
ca-pub-3887254361926659.js
112 ms
zrt_lookup.html
116 ms
show_ads_impl.js
53 ms
date-bg.gif
423 ms
mini-category.gif
416 ms
mini-comments.gif
603 ms
mini-nav-left.gif
578 ms
search-btn-bg.gif
485 ms
mini-monthly-archive.gif
579 ms
mini-blogroll.gif
531 ms
footer-bg.gif
551 ms
mini-footer-post.gif
625 ms
mini-footer-comments.gif
733 ms
footer-right-bg.gif
734 ms
mini-rss.gif
713 ms
mini-loginout.gif
752 ms
ads
227 ms
osd.js
17 ms
ads
195 ms
1215506591548907880
51 ms
abg.js
58 ms
m_js_controller.js
71 ms
googlelogo_color_112x36dp.png
48 ms
s
34 ms
redir.html
635 ms
x_button_blue2.png
35 ms
print.css
172 ms
iframe.html
165 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
tramgeschichten.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
tramgeschichten.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
tramgeschichten.de SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tramgeschichten.de can be misinterpreted by Google and other search engines. Our service has detected that English 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 Tramgeschichten.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.
tramgeschichten.de
Open Graph description is not detected on the main page of Tramgeschichten. 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: