Tools & Wizards About Us
sennheiser.nl screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

sennheiser.nl

Sennheiser — Headphones, Microphones, Wireless Systems

Page Load Speed

4.5 sec in total

First Response

189 ms

Resources Loaded

2 sec

Page Rendered

2.3 sec

sennheiser.nl screenshot

About Website

Click here to check amazing Sennheiser content. Otherwise, check out these important facts you probably never knew about sennheiser.nl

For over 75 years, our products come with a built-in mission: to stay true to the sound and soul the music was given by its artist.

Visit sennheiser.nl

Key Findings

We analyzed Sennheiser.nl page load time and found that the first response time was 189 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

sennheiser.nl performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

sennheiser.nl

189 ms

nl-nl.sennheiser.com

155 ms

en-nl

569 ms

28e621575dc61cb6.css

40 ms

9e70cd3eba432ed2.css

47 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Sennheiser.nl, 92% (58 requests) were made to Sennheiser.com and 5% (3 requests) were made to Cdn.uc.assets.prezly.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Sennheiser.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 551.0 kB (3%)

Content Size

21.3 MB

After Optimization

20.7 MB

  • HTML
  • Images

In fact, the total size of Sennheiser.nl main page is 21.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 21.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 174.6 kB

  • Original 206.4 kB
  • After minification 206.3 kB
  • After compression 31.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 174.6 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 376.4 kB

  • Original 21.1 MB
  • After minification 20.7 MB

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. Sennheiser images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 42 (70%)

Requests Now

60

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sennheiser.nl

sennheiser.nl

189 ms

nl-nl.sennheiser.com

nl-nl.sennheiser.com

155 ms

en-nl

en-nl

569 ms

28e621575dc61cb6.css

28e621575dc61cb6.css

40 ms

9e70cd3eba432ed2.css

9e70cd3eba432ed2.css

47 ms

2af9e66f3f057b77.css

2af9e66f3f057b77.css

53 ms

aa7e46d6c4fa8528.css

aa7e46d6c4fa8528.css

45 ms

a21771cf50b33ade.css

a21771cf50b33ade.css

44 ms

f7e4c7e39b54d486.css

f7e4c7e39b54d486.css

65 ms

e6b675358e5a965a.css

e6b675358e5a965a.css

74 ms

473b927a2ad7f99a.css

473b927a2ad7f99a.css

67 ms

4531b10bad003c43.css

4531b10bad003c43.css

76 ms

1dd3208c-ba45997566588d82.js

1dd3208c-ba45997566588d82.js

81 ms

286-c8bc2f8483ce07e3.js

286-c8bc2f8483ce07e3.js

97 ms

main-app-719c2e562480b46e.js

main-app-719c2e562480b46e.js

95 ms

7410-9ce567bdb927b1f0.js

7410-9ce567bdb927b1f0.js

100 ms

9126-cf21908238cb464f.js

9126-cf21908238cb464f.js

105 ms

8574-ade908ecfd8a36cd.js

8574-ade908ecfd8a36cd.js

99 ms

9590-086f63bd00d48d64.js

9590-086f63bd00d48d64.js

111 ms

layout-b639827cbc26c028.js

layout-b639827cbc26c028.js

115 ms

c3110d36-84717dc3a851c1cf.js

c3110d36-84717dc3a851c1cf.js

125 ms

3549-912ac7af0cdd321f.js

3549-912ac7af0cdd321f.js

120 ms

6546-da738fc1ac22ca2f.js

6546-da738fc1ac22ca2f.js

123 ms

9915-49b67b5e5069abac.js

9915-49b67b5e5069abac.js

141 ms

page-b4b4b688fd3cafdb.js

page-b4b4b688fd3cafdb.js

129 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

138 ms

webpack-19aa34e858c878ce.js

webpack-19aa34e858c878ce.js

185 ms

error-d3e3250d68c9f79e.js

error-d3e3250d68c9f79e.js

109 ms

not-found-1414ba8379232ef1.js

not-found-1414ba8379232ef1.js

110 ms

142 ms

2f92e70df84d5608.css

2f92e70df84d5608.css

27 ms

b1121086a7b48802.css

b1121086a7b48802.css

26 ms

af3834002de952a4.css

af3834002de952a4.css

39 ms

8409cf9c2eda17b0.css

8409cf9c2eda17b0.css

23 ms

16b5784bdb73e90e.css

16b5784bdb73e90e.css

19 ms

ea5e6b2328870a2a.css

ea5e6b2328870a2a.css

26 ms

ed52312dcd167064.css

ed52312dcd167064.css

42 ms

1a1691fac4d598f0.css

1a1691fac4d598f0.css

47 ms

2c88032bb65b41c9.css

2c88032bb65b41c9.css

46 ms

0cd6323250f6ec48.css

0cd6323250f6ec48.css

45 ms

03f8a6b898f94ceb.css

03f8a6b898f94ceb.css

43 ms

34ecda7949b53152.css

34ecda7949b53152.css

69 ms

c804903956e5d11a.css

c804903956e5d11a.css

59 ms

79454a94c32b41f1.css

79454a94c32b41f1.css

60 ms

64d5fd945cfae38b.css

64d5fd945cfae38b.css

63 ms

66883b68a187dd2c.css

66883b68a187dd2c.css

75 ms

cca38ff0eb7c6229.css

cca38ff0eb7c6229.css

67 ms

68c4184611548bb2.css

68c4184611548bb2.css

77 ms

151 ms

172 ms

SennheiserFullWidth

SennheiserFullWidth

199 ms

SennheiserFullWidth

SennheiserFullWidth

358 ms

SennheiserFullWidth

SennheiserFullWidth

206 ms

SennheiserFullWidth

SennheiserFullWidth

321 ms

SennheiserFullWidth

SennheiserFullWidth

229 ms

SennheiserFullWidth

SennheiserFullWidth

365 ms

SennheiserFullWidth

SennheiserFullWidth

419 ms

SennheiserFullWidth

SennheiserFullWidth

580 ms

SennheiserFullWidth

SennheiserFullWidth

588 ms

SennheiserFullWidth

SennheiserFullWidth

508 ms

SennheiserFullWidth

SennheiserFullWidth

1010 ms

SennheiserFullWidth

SennheiserFullWidth

569 ms

SennheiserFullWidth

SennheiserFullWidth

720 ms

Accessibility Review

sennheiser.nl accessibility score

71

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

Document doesn't have a <title> element

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

sennheiser.nl 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

SEO Factors

sennheiser.nl SEO score

58

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sennheiser.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sennheiser.nl 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

sennheiser.nl

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