Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hanser.de

Startseite | Carl Hanser Verlag

Page Load Speed

3 sec in total

First Response

322 ms

Resources Loaded

2.4 sec

Page Rendered

269 ms

About Website

Visit hanser.de now to see the best up-to-date Hanser content for Germany and also check out these interesting facts you probably never knew about hanser.de

Der Carl Hanser Verlag GmbH & Co. KG wurde 1928 von Carl Hanser in München gegründet. Informieren Sie sich über den Verlag, seine Geschichte und seine Bücher und Zeitschriften...

Visit hanser.de

Key Findings

We analyzed Hanser.de page load time and found that the first response time was 322 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

hanser.de performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

hanser.de

322 ms

hanser.de

857 ms

OtAutoBlock.js

32 ms

otSDKStub.js

41 ms

f90157e1-38c5-47b7-872e-1960d1d20fc0.json

21 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 54% of them (22 requests) were addressed to the original Hanser.de, 32% (13 requests) were made to A.storyblok.com and 7% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hanser.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 674.6 kB (69%)

Content Size

975.4 kB

After Optimization

300.8 kB

In fact, the total size of Hanser.de main page is 975.4 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. Javascripts take 770.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 165.1 kB

  • Original 205.3 kB
  • After minification 205.3 kB
  • After compression 40.1 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 165.1 kB or 80% of the original size.

JavaScript Optimization

-66%

Potential reduce by 509.4 kB

  • Original 770.1 kB
  • After minification 770.1 kB
  • After compression 260.7 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 509.4 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (28%)

Requests Now

32

After Optimization

23

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

Accessibility Review

hanser.de accessibility score

88

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

hanser.de best practices score

92

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

Page has valid source maps

SEO Factors

hanser.de SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Hanser.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 Hanser.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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: