3.4 sec in total
709 ms
2.4 sec
231 ms
Click here to check amazing Templin content for Germany. Otherwise, check out these important facts you probably never knew about templin.de
Willkommen Willkommen Welcome Witam Templin In diesem Bereich finden Sie allgemeine Informationen zur Stadt, deren Ortsteile, Veranstaltungen und mehr. Mehr erfahren Erleben Erfahren Sie hier alles üb...
Visit templin.deWe analyzed Templin.de page load time and found that the first response time was 709 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
templin.de performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value3.5 s
63/100
25%
Value3.8 s
83/100
10%
Value0 ms
100/100
30%
Value0.004
100/100
15%
Value1.7 s
100/100
10%
709 ms
287 ms
289 ms
289 ms
292 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Templin.de, 79% (33 requests) were made to Layout.verwaltungsportal.de and 10% (4 requests) were made to Vorschau.verwaltungsportal.de. The less responsive or slowest element that took the longest time to load (887 ms) relates to the external source Analyse.templin.de.
Page size can be reduced by 172.8 kB (52%)
335.0 kB
162.3 kB
In fact, the total size of Templin.de main page is 335.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. 25% of websites need less resources to load. Images take 139.1 kB which makes up the majority of the site volume.
Potential reduce by 66.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 66.6 kB or 86% of the original size.
Potential reduce by 13.7 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. Templin images are well optimized though.
Potential reduce by 33.3 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 33.3 kB or 65% of the original size.
Potential reduce by 59.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. Templin.de needs all CSS files to be minified and compressed as it can save up to 59.1 kB or 88% of the original size.
Number of requests can be reduced by 25 (61%)
41
16
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Templin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.templin.de
709 ms
global.css
287 ms
layout.css
289 ms
style_std.css
289 ms
jquery.fancybox-1.3.4.css
292 ms
jquery-2.1.3.min.js
388 ms
jquery.style-switcher.js
292 ms
portuna_js_helper-1.2.js
379 ms
bookmark.js
379 ms
unterkunft-finden3.png
551 ms
1447698962.jpg
358 ms
1198783708.jpg
352 ms
2321396624.jpg
354 ms
1908113107.jpg
354 ms
28695986b7a517b8a230f57d6839bf9b_twitter.jpg
553 ms
f_icon.png
359 ms
bg_body.jpg
97 ms
bg_main.jpg
96 ms
bg_footer.jpg
100 ms
banner_gruen.jpg
382 ms
blank.gif
98 ms
secondlevel1.jpg
96 ms
thirdlevel1.jpg
188 ms
secondlevel2.jpg
189 ms
thirdlevel2.jpg
188 ms
secondlevel3.jpg
192 ms
secondlevel4.jpg
192 ms
thirdlevel4.jpg
281 ms
secondlevel5.jpg
281 ms
thirdlevel5.jpg
281 ms
foerderprogramm.jpg
292 ms
uckermark.jpg
293 ms
a.jpg
374 ms
aa.jpg
374 ms
aaa.jpg
374 ms
bg_search.jpg
371 ms
bg_boxtop.jpg
371 ms
bg_boxbody.jpg
451 ms
bg_boxbottom.jpg
450 ms
bg_content_info.jpg
450 ms
bg_content_bottom.jpg
457 ms
piwik.js
887 ms
templin.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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
templin.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
templin.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 doesn't use legible font sizes
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Templin.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 Templin.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.
templin.de
Open Graph description is not detected on the main page of Templin. 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: