Tools & Wizards About Us
herose.de screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

herose.de

HEROSE GmbH

Page Load Speed

6.3 sec in total

First Response

327 ms

Resources Loaded

3.8 sec

Page Rendered

2.2 sec

herose.de screenshot

About Website

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

Visit herose.de

Key Findings

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

Performance Metrics

herose.de performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

herose.de

327 ms

292 ms

loader.js

20 ms

uc-block.bundle.js

26 ms

sop.reset.css

155 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Herose.de, 83% (65 requests) were made to Herose.com and 4% (3 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Herose.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.1 MB (56%)

Content Size

7.3 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Herose.de main page is 7.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. 65% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 69.5 kB

  • Original 86.9 kB
  • After minification 71.0 kB
  • After compression 17.4 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. This page needs HTML code to be minified as it can gain 16.0 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.5 kB or 80% of the original size.

Image Optimization

-57%

Potential reduce by 3.8 MB

  • Original 6.6 MB
  • After minification 2.8 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. Obviously, HEROSE needs image optimization as it can save up to 3.8 MB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 107.8 kB

  • Original 438.6 kB
  • After minification 438.6 kB
  • After compression 330.8 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 107.8 kB or 25% of the original size.

CSS Optimization

-82%

Potential reduce by 132.9 kB

  • Original 161.4 kB
  • After minification 139.7 kB
  • After compression 28.5 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. Herose.de needs all CSS files to be minified and compressed as it can save up to 132.9 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEROSE. 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 from 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

herose.de

herose.de

327 ms

292 ms

loader.js

loader.js

20 ms

uc-block.bundle.js

uc-block.bundle.js

26 ms

sop.reset.css

sop.reset.css

155 ms

sop.normalize.css

sop.normalize.css

200 ms

sop.utils.css

sop.utils.css

296 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

489 ms

variables.css

variables.css

298 ms

typography.css

typography.css

299 ms

grid.css

grid.css

298 ms

colored.css

colored.css

300 ms

media.css

media.css

395 ms

button.css

button.css

397 ms

backToTop.css

backToTop.css

399 ms

section.css

section.css

400 ms

content.css

content.css

398 ms

navigation.css

navigation.css

493 ms

header.css

header.css

497 ms

footer.css

footer.css

496 ms

breadcrumb.css

breadcrumb.css

497 ms

form.css

form.css

498 ms

dropdown.css

dropdown.css

586 ms

swiper-bundle.min.css

swiper-bundle.min.css

597 ms

swiper.css

swiper.css

598 ms

js

js

150 ms

backToTop.js

backToTop.js

617 ms

search.js

search.js

618 ms

navigation.js

navigation.js

618 ms

dropdown.js

dropdown.js

688 ms

swiper-bundle.min.js

swiper-bundle.min.js

934 ms

slider.js

slider.js

691 ms

bundle_legacy.js

bundle_legacy.js

18 ms

logo-herose.svg

logo-herose.svg

670 ms

icon-search.svg

icon-search.svg

671 ms

flag-de.svg

flag-de.svg

673 ms

ASU_Slider.jpg

ASU_Slider.jpg

1825 ms

HER_Header_1_1980x1080_230628.jpeg

HER_Header_1_1980x1080_230628.jpeg

1821 ms

HER_Header_4_1980x1080_230628.jpeg

HER_Header_4_1980x1080_230628.jpeg

1820 ms

HER_Header_2_1980x1080_230628.jpeg

HER_Header_2_1980x1080_230628.jpeg

1852 ms

HER_Header_3_1980x1080_230628.jpeg

HER_Header_3_1980x1080_230628.jpeg

1934 ms

icon-arrow-long.svg

icon-arrow-long.svg

1822 ms

Ventilskizze_1.png

Ventilskizze_1.png

1815 ms

Ventilskizze_2.png

Ventilskizze_2.png

1771 ms

languages.json

languages.json

110 ms

Ventilskizze_3.png

Ventilskizze_3.png

1774 ms

Ventilskizze_4.png

Ventilskizze_4.png

1672 ms

Luftgase_header_1920x1080.jpg

Luftgase_header_1920x1080.jpg

1864 ms

LNG_header_1920x1080.jpg

LNG_header_1920x1080.jpg

1962 ms

Wasserstoff_header_1920x1080.jpg

Wasserstoff_header_1920x1080.jpg

2062 ms

Dampf_header_1920x1080.jpg

Dampf_header_1920x1080.jpg

1772 ms

Druckluft_header_1920x1080.jpg

Druckluft_header_1920x1080.jpg

1866 ms

FKS_header_1920x1080.jpg

FKS_header_1920x1080.jpg

2066 ms

NeueVC.png

NeueVC.png

1961 ms

05C02.jpg

05C02.jpg

1865 ms

de.json

de.json

114 ms

Behaelter_ASU.png

Behaelter_ASU.png

1873 ms

FullX_dez23.png

FullX_dez23.png

1969 ms

BioLNG.png

BioLNG.png

2064 ms

sicherheitsventile.png

sicherheitsventile.png

1965 ms

wechselarmaturen.png

wechselarmaturen.png

2061 ms

durchgangsventile.png

durchgangsventile.png

2066 ms

regelarmatur_4182x1.png

regelarmatur_4182x1.png

1976 ms

1px.png

1px.png

26 ms

lftracker_v1_DzLR5a5zKX08BoQ2.js

lftracker_v1_DzLR5a5zKX08BoQ2.js

50 ms

schmutzfaenger_08414.png

schmutzfaenger_08414.png

2046 ms

06C01_.png

06C01_.png

1948 ms

11C01_.png

11C01_.png

2042 ms

logo-social-youtube.svg

logo-social-youtube.svg

2039 ms

logo-social-instagram.svg

logo-social-instagram.svg

2007 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

0 ms

logo-social-linkedin.svg

logo-social-linkedin.svg

1975 ms

logo-herose-compact.svg

logo-herose-compact.svg

1973 ms

icon-dropdown-active.svg

icon-dropdown-active.svg

2061 ms

icon-dropdown-inactive.svg

icon-dropdown-inactive.svg

2061 ms

translations-de.json

translations-de.json

7 ms

tr.lfeeder.com

tr.lfeeder.com

1012 ms

uct

uct

967 ms

Accessibility Review

herose.de accessibility score

88

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

herose.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

herose.de SEO score

92

Search Engine Optimization Advices

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 Herose.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 Herose.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

herose.de

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