Tools & Wizards About Us
lorch.de screenshot

Report Summary

  • 37

    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

  • 83

    SEO

    Google-friendlier than
    46% of websites

lorch.de

Production and sales of safety valves for industrial applications

Page Load Speed

6 sec in total

First Response

394 ms

Resources Loaded

3.6 sec

Page Rendered

2 sec

lorch.de screenshot

About Website

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

LORCH safety valves, your competent partner with experience, know-how and vision for your industrial applications

Visit lorch.de

Key Findings

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

Performance Metrics

lorch.de performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

lorch.de

394 ms

www.lorch.de

618 ms

index.php

101 ms

735 ms

loader.js

24 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (43%)

Content Size

6.5 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 44.6 kB

  • Original 53.1 kB
  • After minification 38.0 kB
  • After compression 8.5 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 15.1 kB, which is 29% 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 44.6 kB or 84% of the original size.

Image Optimization

-43%

Potential reduce by 2.5 MB

  • Original 5.8 MB
  • After minification 3.3 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, Lorch needs image optimization as it can save up to 2.5 MB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 108.9 kB

  • Original 398.9 kB
  • After minification 398.9 kB
  • After compression 290.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 108.9 kB or 27% of the original size.

CSS Optimization

-82%

Potential reduce by 143.3 kB

  • Original 174.3 kB
  • After minification 150.7 kB
  • After compression 31.1 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. Lorch.de needs all CSS files to be minified and compressed as it can save up to 143.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (55%)

Requests Now

71

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lorch.de

lorch.de

394 ms

www.lorch.de

www.lorch.de

618 ms

index.php

index.php

101 ms

735 ms

loader.js

loader.js

24 ms

uc-block.bundle.js

uc-block.bundle.js

31 ms

sop.reset.css

sop.reset.css

101 ms

sop.normalize.css

sop.normalize.css

202 ms

sop.utils.css

sop.utils.css

297 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

493 ms

variables.css

variables.css

298 ms

typography.css

typography.css

298 ms

grid.css

grid.css

299 ms

colored.css

colored.css

300 ms

media.css

media.css

396 ms

button.css

button.css

399 ms

backToTop.css

backToTop.css

398 ms

section.css

section.css

400 ms

content.css

content.css

399 ms

list.css

list.css

496 ms

article.css

article.css

500 ms

navigation.css

navigation.css

501 ms

header.css

header.css

502 ms

footer.css

footer.css

502 ms

breadcrumb.css

breadcrumb.css

592 ms

form.css

form.css

596 ms

dropdown.css

dropdown.css

599 ms

swiper-bundle.min.css

swiper-bundle.min.css

602 ms

swiper.css

swiper.css

602 ms

js

js

78 ms

backToTop.js

backToTop.js

600 ms

search.js

search.js

692 ms

navigation.js

navigation.js

693 ms

dropdown.js

dropdown.js

698 ms

swiper-bundle.min.js

swiper-bundle.min.js

895 ms

slider.js

slider.js

702 ms

bundle.js

bundle.js

11 ms

logo-herose.svg

logo-herose.svg

671 ms

icon-search.svg

icon-search.svg

762 ms

flag-en.svg

flag-en.svg

763 ms

HER_Header_1_1980x1080_230628.jpeg

HER_Header_1_1980x1080_230628.jpeg

963 ms

HER_Header_4_1980x1080_230628.jpeg

HER_Header_4_1980x1080_230628.jpeg

867 ms

HER_Header_2_1980x1080_230628.jpeg

HER_Header_2_1980x1080_230628.jpeg

966 ms

HER_Header_3_1980x1080_230628.jpeg

HER_Header_3_1980x1080_230628.jpeg

1156 ms

icon-arrow-long.svg

icon-arrow-long.svg

798 ms

Ventilskizze_1.png

Ventilskizze_1.png

895 ms

Ventilskizze_2.png

Ventilskizze_2.png

704 ms

Ventilskizze_3.png

Ventilskizze_3.png

803 ms

Ventilskizze_4.png

Ventilskizze_4.png

897 ms

Luftgase_header_1920x1080.jpg

Luftgase_header_1920x1080.jpg

899 ms

LNG_header_1920x1080.jpg

LNG_header_1920x1080.jpg

901 ms

Wasserstoff_header_1920x1080.jpg

Wasserstoff_header_1920x1080.jpg

1192 ms

Dampf_header_1920x1080.jpg

Dampf_header_1920x1080.jpg

904 ms

Druckluft_header_1920x1080.jpg

Druckluft_header_1920x1080.jpg

990 ms

FKS_header_1920x1080.jpg

FKS_header_1920x1080.jpg

996 ms

AmmoniaShip.jpg

AmmoniaShip.jpg

997 ms

VC02-24.png

VC02-24.png

905 ms

NeueVC.png

NeueVC.png

1005 ms

05C02.jpg

05C02.jpg

989 ms

Behaelter_ASU.png

Behaelter_ASU.png

999 ms

sicherheitsventile.png

sicherheitsventile.png

997 ms

wechselarmaturen.png

wechselarmaturen.png

998 ms

durchgangsventile.png

durchgangsventile.png

1094 ms

regelarmatur_4182x1.png

regelarmatur_4182x1.png

1003 ms

schmutzfaenger_08414.png

schmutzfaenger_08414.png

1098 ms

06C01_.png

06C01_.png

1003 ms

11C01_.png

11C01_.png

1001 ms

lftracker_v1_DzLR5a5zKX08BoQ2.js

lftracker_v1_DzLR5a5zKX08BoQ2.js

426 ms

logo-social-youtube.svg

logo-social-youtube.svg

1025 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

0 ms

logo-social-instagram.svg

logo-social-instagram.svg

1006 ms

logo-social-linkedin.svg

logo-social-linkedin.svg

1009 ms

logo-herose-compact.svg

logo-herose-compact.svg

1005 ms

icon-dropdown-active.svg

icon-dropdown-active.svg

1083 ms

icon-dropdown-inactive.svg

icon-dropdown-inactive.svg

1084 ms

tr.lfeeder.com

tr.lfeeder.com

56 ms

Accessibility Review

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

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

lorch.de SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

lorch.de

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