Tools & Wizards About Us
historycorner.de screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

historycorner.de

Duke Gozers History Corner - Das Retro-Portal für alte Systeme

Page Load Speed

2.8 sec in total

First Response

398 ms

Resources Loaded

2.3 sec

Page Rendered

113 ms

historycorner.de screenshot

About Website

Welcome to historycorner.de homepage info - get ready to check History Corner best content right away, or after learning these important things about historycorner.de

History Corner beschäftigt sich mit der Computergeschichte und stellt die Modelle und die entwickelnden Unternehmen ebenso vor, wie die Köpfe dahinter.

Visit historycorner.de

Key Findings

We analyzed Historycorner.de page load time and found that the first response time was 398 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

historycorner.de performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

historycorner.de

398 ms

www.historycorner.de

324 ms

MarketPlace.css

110 ms

plusone.js

23 ms

widgets.js

38 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 25% of them (8 requests) were addressed to the original Historycorner.de, 19% (6 requests) were made to Apis.google.com and 13% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.3 kB (8%)

Content Size

315.8 kB

After Optimization

290.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Historycorner.de main page is 315.8 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. 45% of websites need less resources to load. Javascripts take 166.6 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 18.8 kB

  • Original 27.6 kB
  • After minification 26.4 kB
  • After compression 8.8 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 18.8 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 5.2 kB

  • Original 118.4 kB
  • After minification 113.3 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. History Corner images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 502 B

  • Original 166.6 kB
  • After minification 166.6 kB
  • After compression 166.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 839 B

  • Original 3.2 kB
  • After minification 3.2 kB
  • After compression 2.3 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. Historycorner.de needs all CSS files to be minified and compressed as it can save up to 839 B or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (40%)

Requests Now

25

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historycorner.de

historycorner.de

398 ms

www.historycorner.de

www.historycorner.de

324 ms

MarketPlace.css

MarketPlace.css

110 ms

plusone.js

plusone.js

23 ms

widgets.js

widgets.js

38 ms

ga.js

ga.js

56 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

45 ms

19.gif

19.gif

711 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

268 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

13 ms

fastbutton

fastbutton

113 ms

header-photo.jpg

header-photo.jpg

423 ms

content-wrap.jpg

content-wrap.jpg

220 ms

button.jpg

button.jpg

226 ms

286px-Pong.png

286px-Pong.png

227 ms

NES_nn.jpg

NES_nn.jpg

226 ms

all.js

all.js

112 ms

postmessageRelay

postmessageRelay

90 ms

__utm.gif

__utm.gif

17 ms

all.js

all.js

11 ms

collect

collect

70 ms

developers.google.com

developers.google.com

1034 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

29 ms

rpc:shindig_random.js

rpc:shindig_random.js

10 ms

ga-audiences

ga-audiences

133 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

settings

settings

69 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

21 ms

embeds

embeds

20 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.de.html

tweet_button.2f70fb173b9000da126c79afe2098f02.de.html

37 ms

www.wetest.de

www.wetest.de

281 ms

www.wetest.de

www.wetest.de

434 ms

Accessibility Review

historycorner.de accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Best Practices

historycorner.de best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

historycorner.de SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historycorner.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 Historycorner.de main page’s claimed encoding is iso-8859-1. 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

historycorner.de

Open Graph data is detected on the main page of History Corner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: