Report Summary

  • 28

    Performance

    Renders faster than
    49% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

historiker.de

Res Media GmbH & Co. KG - Internetagentur Augsburg

Page Load Speed

3.5 sec in total

First Response

876 ms

Resources Loaded

2.2 sec

Page Rendered

466 ms

historiker.de screenshot

About Website

Click here to check amazing Historiker content. Otherwise, check out these important facts you probably never knew about historiker.de

Kundenorientiert, zuverlässig und kostenbewusst. Das sind die Stärken der Internetagentur Res Media in Augsburg. Der Wordpress und Symfony Spezialist.

Visit historiker.de

Key Findings

We analyzed Historiker.de page load time and found that the first response time was 876 ms and then it took 2.6 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

historiker.de performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value4,620 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.res-media.de

876 ms

js

100 ms

jquery.min.js

197 ms

3bef155fbebbe6c5763ca1e861ea8c2b.js

972 ms

Logo-JPG-03.jpg

665 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Historiker.de, 17% (2 requests) were made to Googletagmanager.com and 17% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (972 ms) relates to the external source Res-media.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.3 kB (82%)

Content Size

549.6 kB

After Optimization

99.3 kB

In fact, the total size of Historiker.de main page is 549.6 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. 35% of websites need less resources to load. HTML takes 517.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 450.2 kB

  • Original 517.0 kB
  • After minification 514.9 kB
  • After compression 66.7 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 450.2 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 12.6 kB
  • After minification 12.6 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. Historiker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 63 B

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 20.0 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.

Requests Breakdown

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

Requests Now

10

After Optimization

6

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Historiker. 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.

Accessibility Review

historiker.de accessibility score

95

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

Links do not have a discernible name

Best Practices

historiker.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

historiker.de SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historiker.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 Historiker.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.

Social Sharing Optimization

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