Tools & Wizards About Us
ghc.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

ghc.com

GHC – the chemical gas specialist

Page Load Speed

3.8 sec in total

First Response

818 ms

Resources Loaded

2.7 sec

Page Rendered

202 ms

ghc.com screenshot

About Website

Visit ghc.com now to see the best up-to-date GHC content for United States and also check out these interesting facts you probably never knew about ghc.com

GHC Gerling, Holz & Co. - Hersteller, Handelshaus und Zulieferer - bietet eine breite Palette an Produkten an, die Kältemittel, Spezialgase, chemische Rohstoffe und Anlagenbau umfasst. Wir arbeiten mi...

Visit ghc.com

Key Findings

We analyzed Ghc.com page load time and found that the first response time was 818 ms and then it took 3 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

ghc.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.992

2/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

home.php

818 ms

mdcr.js

191 ms

jquery-min.js

899 ms

style.css

300 ms

ghc_gradient_home.png

101 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Ghc.com and no external sources were called. The less responsive or slowest element that took the longest time to load (899 ms) relates to the external source Ghc.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.5 kB (38%)

Content Size

213.2 kB

After Optimization

131.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ghc.com main page is 213.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 95.4 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 4.4 kB

  • Original 6.9 kB
  • After minification 6.6 kB
  • After compression 2.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. 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 4.4 kB or 64% of the original size.

Image Optimization

-2%

Potential reduce by 2.2 kB

  • Original 95.4 kB
  • After minification 93.2 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. GHC images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 61.2 kB

  • Original 94.8 kB
  • After minification 94.3 kB
  • After compression 33.6 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 61.2 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 13.6 kB

  • Original 16.0 kB
  • After minification 8.5 kB
  • After compression 2.4 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. Ghc.com needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

11

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

home.php

home.php

818 ms

mdcr.js

mdcr.js

191 ms

jquery-min.js

jquery-min.js

899 ms

style.css

style.css

300 ms

ghc_gradient_home.png

ghc_gradient_home.png

101 ms

ghc_home_footer_bg.png

ghc_home_footer_bg.png

105 ms

spacer.gif

spacer.gif

110 ms

ghcgradient_1.png

ghcgradient_1.png

101 ms

GHC_Logo_77.png

GHC_Logo_77.png

321 ms

startbild_980_sat_de.jpg

startbild_980_sat_de.jpg

729 ms

startbild_980_sprache.png

startbild_980_sprache.png

283 ms

print.css

print.css

102 ms

Accessibility Review

ghc.com accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

ghc.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ghc.com SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ghc.com

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