Tools & Wizards About Us
ghg-hamburg.de screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ghg-hamburg.de

GHG Hamburg | Gebäudereinigung Hamburg, Hausmeister Service

Page Load Speed

1.7 sec in total

First Response

472 ms

Resources Loaded

1.1 sec

Page Rendered

154 ms

ghg-hamburg.de screenshot

About Website

Welcome to ghg-hamburg.de homepage info - get ready to check GHG Hamburg best content right away, or after learning these important things about ghg-hamburg.de

Gesellschaft für Haus- und Grundstückspflege mbH in Hamburg, Schleswig Holstein und ganz Norddeutschland. Komplettservice rund ums Haus, Garten und Grundstück, Büro

Visit ghg-hamburg.de

Key Findings

We analyzed Ghg-hamburg.de page load time and found that the first response time was 472 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

ghg-hamburg.de performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

ghg-hamburg.de

472 ms

style.css

193 ms

site.css

200 ms

clearpixel.gif

213 ms

export.html

686 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Ghg-hamburg.de, 6% (1 request) were made to Rss-experte.de and 6% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (686 ms) relates to the external source Rss-experte.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.0 kB (16%)

Content Size

131.0 kB

After Optimization

110.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ghg-hamburg.de main page is 131.0 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. 15% of websites need less resources to load. Images take 84.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.6 kB

  • Original 24.4 kB
  • After minification 24.2 kB
  • After compression 4.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 19.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 609 B

  • Original 84.7 kB
  • After minification 84.1 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. GHG Hamburg images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 746 B

  • Original 1.0 kB
  • After minification 706 B
  • After compression 254 B

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. Ghg-hamburg.de needs all CSS files to be minified and compressed as it can save up to 746 B or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GHG Hamburg. According to our analytics all requests are already optimized.

Network Requests Diagram

ghg-hamburg.de

ghg-hamburg.de

472 ms

style.css

style.css

193 ms

site.css

site.css

200 ms

clearpixel.gif

clearpixel.gif

213 ms

export.html

export.html

686 ms

ghg-111x46.jpg

ghg-111x46.jpg

210 ms

liniegrau800x1.gif

liniegrau800x1.gif

210 ms

DGUV-Pfuefungen.jpg

DGUV-Pfuefungen.jpg

312 ms

a_ghg_video.gif

a_ghg_video.gif

287 ms

link-dunkelgruen.gif

link-dunkelgruen.gif

307 ms

ghg-backg001.jpg

ghg-backg001.jpg

118 ms

buttonback002gr.gif

buttonback002gr.gif

118 ms

ghg-backg002.jpg

ghg-backg002.jpg

118 ms

ghg-bild176-004.jpg

ghg-bild176-004.jpg

279 ms

ghg-bild176-002.jpg

ghg-bild176-002.jpg

214 ms

ghg-bild176-006b.jpg

ghg-bild176-006b.jpg

320 ms

analytics.js

analytics.js

7 ms

Accessibility Review

ghg-hamburg.de accessibility score

93

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

Links do not have a discernible name

Best Practices

ghg-hamburg.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ghg-hamburg.de SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ghg-hamburg.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ghg-hamburg.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ghg-hamburg.de

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