Tools & Wizards About Us
chronik-berlin.de screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

chronik-berlin.de

Chronik Berlin's

Page Load Speed

2.8 sec in total

First Response

350 ms

Resources Loaded

2.1 sec

Page Rendered

270 ms

chronik-berlin.de screenshot

About Website

Welcome to chronik-berlin.de homepage info - get ready to check Chronik Berlin best content for Germany right away, or after learning these important things about chronik-berlin.de

Geschichte Berlin's von 1230 bis zur heutigen Zeit, mit vielen Historischen Bildern und Zeittafeln. Die Geschichte des deutschen Reichstags. Heinrich Zille und seine Bilder und Zeichnungen.

Visit chronik-berlin.de

Key Findings

We analyzed Chronik-berlin.de page load time and found that the first response time was 350 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

chronik-berlin.de performance score

0

Network Requests Diagram

chronik-berlin.de

350 ms

bd.js

120 ms

index_lk.htm

124 ms

startside.htm

240 ms

realcount.pl

127 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 91% of them (69 requests) were addressed to the original Chronik-berlin.de, 8% (6 requests) were made to Daswetter.org and 1% (1 request) were made to Www2.stats4free.de. The less responsive or slowest element that took the longest time to load (898 ms) belongs to the original domain Chronik-berlin.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.9 kB (18%)

Content Size

72.2 kB

After Optimization

59.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chronik-berlin.de main page is 72.2 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. 20% of websites need less resources to load. Images take 62.4 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 1.3 kB

  • Original 2.2 kB
  • After minification 2.1 kB
  • After compression 817 B

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 1.3 kB or 62% of the original size.

Image Optimization

-11%

Potential reduce by 6.6 kB

  • Original 62.4 kB
  • After minification 55.8 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. Obviously, Chronik Berlin needs image optimization as it can save up to 6.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 4.7 kB

  • Original 7.2 kB
  • After minification 6.7 kB
  • After compression 2.5 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 4.7 kB or 65% of the original size.

CSS Optimization

-63%

Potential reduce by 286 B

  • Original 454 B
  • After minification 324 B
  • After compression 168 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. Chronik-berlin.de needs all CSS files to be minified and compressed as it can save up to 286 B or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (19%)

Requests Now

74

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chronik Berlin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

chronik-berlin.de

chronik-berlin.de

350 ms

bd.js

bd.js

120 ms

index_lk.htm

index_lk.htm

124 ms

startside.htm

startside.htm

240 ms

realcount.pl

realcount.pl

127 ms

menu_.js

menu_.js

236 ms

bg_grau_fein.jpg

bg_grau_fein.jpg

256 ms

bn_gesch-bln.jpg

bn_gesch-bln.jpg

255 ms

menu__top.gif

menu__top.gif

256 ms

menu__bottom.gif

menu__bottom.gif

258 ms

styles.css

styles.css

140 ms

popup.js

popup.js

237 ms

realcount.pl

realcount.pl

255 ms

log.pl

log.pl

465 ms

menu__b1.gif

menu__b1.gif

142 ms

menu__b1_over.gif

menu__b1_over.gif

143 ms

menu__b2.gif

menu__b2.gif

144 ms

menu__b2_over.gif

menu__b2_over.gif

144 ms

menu__b3.gif

menu__b3.gif

230 ms

menu__b3_over.gif

menu__b3_over.gif

244 ms

menu__b4.gif

menu__b4.gif

242 ms

menu__b4_over.gif

menu__b4_over.gif

253 ms

menu__b5.gif

menu__b5.gif

254 ms

menu__b5_over.gif

menu__b5_over.gif

255 ms

menu__b6.gif

menu__b6.gif

358 ms

menu__b6_over.gif

menu__b6_over.gif

359 ms

menu__b7.gif

menu__b7.gif

360 ms

menu__b7_over.gif

menu__b7_over.gif

370 ms

menu__b8.gif

menu__b8.gif

392 ms

menu__b8_over.gif

menu__b8_over.gif

394 ms

menu__b9.gif

menu__b9.gif

476 ms

menu__b9_over.gif

menu__b9_over.gif

476 ms

menu__b10.gif

menu__b10.gif

488 ms

menu__b10_over.gif

menu__b10_over.gif

488 ms

menu__b11.gif

menu__b11.gif

510 ms

menu__b11_over.gif

menu__b11_over.gif

525 ms

menu__b12.gif

menu__b12.gif

593 ms

menu__b12_over.gif

menu__b12_over.gif

592 ms

menu__b13.gif

menu__b13.gif

605 ms

menu__b13_over.gif

menu__b13_over.gif

606 ms

menu__b14.gif

menu__b14.gif

626 ms

menu__b14_over.gif

menu__b14_over.gif

672 ms

menu__b15.gif

menu__b15.gif

707 ms

menu__b15_over.gif

menu__b15_over.gif

706 ms

menu__b16.gif

menu__b16.gif

720 ms

menu__b16_over.gif

menu__b16_over.gif

719 ms

button.php

button.php

266 ms

head_gadget.gif

head_gadget.gif

304 ms

hw_Berlin_12203.php

hw_Berlin_12203.php

321 ms

bn_01.htm

bn_01.htm

272 ms

geschichte_bln.gif

geschichte_bln.gif

770 ms

pferdebahn.gif

pferdebahn.gif

679 ms

foot_gadget.gif

foot_gadget.gif

297 ms

opti.gif

opti.gif

698 ms

sidemap.gif

sidemap.gif

696 ms

ms_ie.gif

ms_ie.gif

730 ms

bn_chroniken-asien400.gif

bn_chroniken-asien400.gif

714 ms

fundgrube.gif

fundgrube.gif

792 ms

weiter.gif

weiter.gif

815 ms

IM_merkel.jpg

IM_merkel.jpg

736 ms

gaestebuch.gif

gaestebuch.gif

731 ms

rahmen_ob.gif

rahmen_ob.gif

745 ms

wunschname.gif

wunschname.gif

773 ms

suchen.gif

suchen.gif

800 ms

werb-bln120.gif

werb-bln120.gif

821 ms

servicetelefon.gif

servicetelefon.gif

723 ms

rahmen_un.gif

rahmen_un.gif

732 ms

gluecklich-werden.jpg

gluecklich-werden.jpg

863 ms

bu_news.gif

bu_news.gif

774 ms

bln-tafel.jpg

bln-tafel.jpg

898 ms

bn_wittenau.gif

bn_wittenau.gif

237 ms

favoriten2.gif

favoriten2.gif

799 ms

schauer.png

schauer.png

101 ms

gplus.png

gplus.png

100 ms

fbshare.png

fbshare.png

99 ms

blank.gif

blank.gif

120 ms

Accessibility Review

chronik-berlin.de accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

chronik-berlin.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

chronik-berlin.de SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chronik-berlin.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 Chronik-berlin.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

chronik-berlin.de

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