1.6 sec in total
316 ms
1.1 sec
132 ms
Click here to check amazing Berlin Geschichte content. Otherwise, check out these important facts you probably never knew about berlingeschichte.de
Berlin-Lexikon: Stadtentwicklung, Personen, Schauplätze, Zeitgeschehen, Literaturkritik, historische Fakten, Erkundungen - von den Anfängen bis zur Gegenwart
Visit berlingeschichte.deWe analyzed Berlingeschichte.de page load time and found that the first response time was 316 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
berlingeschichte.de performance score
name
value
score
weighting
Value1.8 s
88/100
10%
Value2.4 s
92/100
25%
Value2.3 s
99/100
10%
Value0 ms
100/100
30%
Value0.467
19/100
15%
Value1.8 s
100/100
10%
316 ms
387 ms
95 ms
187 ms
279 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 Berlingeschichte.de and no external sources were called. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Berlingeschichte.de.
Page size can be reduced by 10.6 kB (69%)
15.2 kB
4.7 kB
In fact, the total size of Berlingeschichte.de main page is 15.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 14.9 kB which makes up the majority of the site volume.
Potential reduce by 10.5 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 10.5 kB or 70% of the original size.
Potential reduce by 33 B
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. Berlingeschichte.de needs all CSS files to be minified and compressed as it can save up to 33 B or 12% of the original size.
We found no issues to fix!
9
9
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berlin Geschichte. According to our analytics all requests are already optimized.
berlingeschichte.de
316 ms
berlingeschichte.de
387 ms
Inhalt.css
95 ms
petschaft.gif
187 ms
pxl.gif
279 ms
a-z1300.gif
278 ms
a-z1700.gif
279 ms
inhalt.css
191 ms
nebel_komb.gif
95 ms
a-z1800.gif
95 ms
a-z1900.gif
131 ms
a-z1920.gif
96 ms
berlingeschichte.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
berlingeschichte.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
berlingeschichte.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berlingeschichte.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 Berlingeschichte.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.
berlingeschichte.de
Open Graph description is not detected on the main page of Berlin Geschichte. 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: