Tools & Wizards About Us
netzhaus.ag screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

netzhaus.ag

netzhaus aktiengesellschaft - Ihr persönliches IT-Systemhaus aus Potsdam.

Page Load Speed

5.2 sec in total

First Response

306 ms

Resources Loaded

4.3 sec

Page Rendered

609 ms

netzhaus.ag screenshot

About Website

Click here to check amazing Netzh Aus content. Otherwise, check out these important facts you probably never knew about netzhaus.ag

Als herstellerunabhängiges IT-Systemhaus aus Potsdam entwickeln, implementieren und betreiben wir IT-Lösungen auf Basis Ihrer individuellen Anforderungen.

Visit netzhaus.ag

Key Findings

We analyzed Netzhaus.ag page load time and found that the first response time was 306 ms and then it took 4.9 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

netzhaus.ag performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

netzhaus.ag

306 ms

www.netzhaus.ag

306 ms

www.netzhaus.ag

1051 ms

wp-emoji-release.min.js

233 ms

style.css

939 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 87% of them (41 requests) were addressed to the original Netzhaus.ag, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Netzhaus.ag.

Page Optimization Overview & Recommendations

Page size can be reduced by 893.4 kB (28%)

Content Size

3.2 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Netzhaus.ag main page is 3.2 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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 48.8 kB

  • Original 61.3 kB
  • After minification 56.5 kB
  • After compression 12.6 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 48.8 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 129.2 kB

  • Original 2.2 MB
  • After minification 2.1 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. Netzh Aus images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 265.8 kB

  • Original 378.9 kB
  • After minification 336.5 kB
  • After compression 113.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 265.8 kB or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 449.6 kB

  • Original 509.7 kB
  • After minification 457.1 kB
  • After compression 60.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. Netzhaus.ag needs all CSS files to be minified and compressed as it can save up to 449.6 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (47%)

Requests Now

43

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

netzhaus.ag

netzhaus.ag

306 ms

www.netzhaus.ag

www.netzhaus.ag

306 ms

www.netzhaus.ag

www.netzhaus.ag

1051 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

233 ms

style.css

style.css

939 ms

css

css

62 ms

style.css

style.css

312 ms

shortcodes.css

shortcodes.css

419 ms

shortcodes_responsive.css

shortcodes_responsive.css

320 ms

magnific_popup.css

magnific_popup.css

324 ms

jetpack.css

jetpack.css

494 ms

jquery.js

jquery.js

720 ms

jquery-migrate.min.js

jquery-migrate.min.js

426 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

429 ms

devicepx-jetpack.js

devicepx-jetpack.js

40 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

522 ms

custom.js

custom.js

635 ms

jquery.fitvids.js

jquery.fitvids.js

536 ms

waypoints.min.js

waypoints.min.js

595 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

625 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

1011 ms

wp-embed.min.js

wp-embed.min.js

699 ms

salvattore.min.js

salvattore.min.js

730 ms

e-201611.js

e-201611.js

37 ms

analytics.js

analytics.js

68 ms

nhwplogowhite.png

nhwplogowhite.png

858 ms

slider_mf.jpg

slider_mf.jpg

546 ms

slider_sh.jpg

slider_sh.jpg

661 ms

slider_jg-1.jpg

slider_jg-1.jpg

541 ms

slider_team.jpg

slider_team.jpg

1613 ms

image1.jpg

image1.jpg

762 ms

bg_references.jpg

bg_references.jpg

687 ms

smartadminguy-400x284.jpg

smartadminguy-400x284.jpg

661 ms

AWB_wz_teaser-400x284.jpg

AWB_wz_teaser-400x284.jpg

769 ms

AWB_ricam_beitrag-400x284.jpg

AWB_ricam_beitrag-400x284.jpg

766 ms

msplogo.jpg

msplogo.jpg

791 ms

lcaplogo.jpg

lcaplogo.jpg

1185 ms

dpdlogo.jpg

dpdlogo.jpg

871 ms

inllogo.jpg

inllogo.jpg

873 ms

deniclogo.jpg

deniclogo.jpg

896 ms

ripencclogo.jpg

ripencclogo.jpg

1168 ms

bcixlogo.jpg

bcixlogo.jpg

975 ms

csmiglogo1.jpg

csmiglogo1.jpg

979 ms

slider_mf_mobil.jpg

slider_mf_mobil.jpg

1504 ms

ETmodules_v2_4.ttf

ETmodules_v2_4.ttf

1087 ms

collect

collect

14 ms

g.gif

g.gif

21 ms

Accessibility Review

netzhaus.ag accessibility score

83

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

netzhaus.ag 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

netzhaus.ag SEO score

97

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

High

Tap targets are not sized appropriately

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 Netzhaus.ag 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 Netzhaus.ag 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

netzhaus.ag

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