3.7 sec in total
762 ms
2.8 sec
157 ms
Welcome to potsdam-wiki.de homepage info - get ready to check Potsdam Wiki best content for Germany right away, or after learning these important things about potsdam-wiki.de
Visit potsdam-wiki.deWe analyzed Potsdam-wiki.de page load time and found that the first response time was 762 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
potsdam-wiki.de performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value1.8 s
99/100
25%
Value3.2 s
92/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
762 ms
257 ms
361 ms
531 ms
361 ms
Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Potsdam-wiki.de and no external sources were called. The less responsive or slowest element that took the longest time to load (762 ms) belongs to the original domain Potsdam-wiki.de.
Page size can be reduced by 15.3 kB (24%)
64.3 kB
49.0 kB
In fact, the total size of Potsdam-wiki.de main page is 64.3 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. Only 10% of websites need less resources to load. Images take 47.4 kB which makes up the majority of the site volume.
Potential reduce by 11.3 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 11.3 kB or 67% of the original size.
Potential reduce by 4.0 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 Wiki images are well optimized though.
Number of requests can be reduced by 4 (36%)
11
7
The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potsdam Wiki. 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 as a result speed up the page load time.
PotsdamWiki:Hauptseite
762 ms
load.php
257 ms
load.php
361 ms
load.php
531 ms
load.php
361 ms
load.php
520 ms
load.php
149 ms
Sanssouci_bei_der_Potsdamer_Schl%C3%B6ssernacht_.jpg
196 ms
logo.png
96 ms
gnu-fdl.png
98 ms
poweredby_mediawiki_88x31.png
98 ms
load.php
415 ms
potsdam-wiki.de accessibility score
potsdam-wiki.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
potsdam-wiki.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potsdam-wiki.de 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 Potsdam-wiki.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.
potsdam-wiki.de
Open Graph description is not detected on the main page of Potsdam Wiki. 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: