Tools & Wizards About Us
netzschmie.de screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

netzschmie.de

netzschmie.de | Georg Loewy | n e t z s c h m i e . de | fine web products and services

Page Load Speed

1.6 sec in total

First Response

109 ms

Resources Loaded

1.3 sec

Page Rendered

93 ms

netzschmie.de screenshot

About Website

Welcome to netzschmie.de homepage info - get ready to check N E T Z S C H M I best content right away, or after learning these important things about netzschmie.de

Involved in web design and coding since 1996, we have been through a lot of changes in design trends as well as development in technology and the way the web is perceived.

Visit netzschmie.de

Key Findings

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

Performance Metrics

netzschmie.de performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

109 ms

loewy-de-styles.css

95 ms

SpryValidationTextField.js

264 ms

SpryValidationTextarea.js

186 ms

SpryTooltip.js

185 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 67% of them (33 requests) were addressed to the original Netzschmie.de, 29% (14 requests) were made to Use.typekit.net and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (644 ms) belongs to the original domain Netzschmie.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.4 kB (5%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 20.9 kB

  • Original 25.8 kB
  • After minification 25.7 kB
  • After compression 4.9 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 20.9 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 37.3 kB

  • Original 1.3 MB
  • After minification 1.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. N E T Z S C H M I images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 13.0 kB

  • Original 62.6 kB
  • After minification 62.6 kB
  • After compression 49.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 13.0 kB or 21% of the original size.

CSS Optimization

-48%

Potential reduce by 2.2 kB

  • Original 4.6 kB
  • After minification 4.1 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. Netzschmie.de needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (27%)

Requests Now

33

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of N E T Z S C H M I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

109 ms

loewy-de-styles.css

loewy-de-styles.css

95 ms

SpryValidationTextField.js

SpryValidationTextField.js

264 ms

SpryValidationTextarea.js

SpryValidationTextarea.js

186 ms

SpryTooltip.js

SpryTooltip.js

185 ms

jquery.min.js

jquery.min.js

278 ms

fadeslideshow.js

fadeslideshow.js

185 ms

slideshow.js

slideshow.js

185 ms

osf1ohh.js

osf1ohh.js

25 ms

SpryValidationTextField.css

SpryValidationTextField.css

276 ms

SpryValidationTextarea.css

SpryValidationTextarea.css

276 ms

SpryTooltip.css

SpryTooltip.css

291 ms

challenge

challenge

23 ms

pic-01.jpg

pic-01.jpg

102 ms

pic-02.jpg

pic-02.jpg

186 ms

pic-03.jpg

pic-03.jpg

280 ms

pic-04.jpg

pic-04.jpg

279 ms

pic-05.jpg

pic-05.jpg

189 ms

pic-06.jpg

pic-06.jpg

184 ms

pic-07.jpg

pic-07.jpg

282 ms

pic-08.jpg

pic-08.jpg

368 ms

pic-09.jpg

pic-09.jpg

274 ms

pic-10.jpg

pic-10.jpg

281 ms

pic-11.jpg

pic-11.jpg

450 ms

pic-12.jpg

pic-12.jpg

462 ms

pic-13.jpg

pic-13.jpg

461 ms

pic-14.jpg

pic-14.jpg

373 ms

antonius-blue.png

antonius-blue.png

644 ms

transparent-40-20x20.png

transparent-40-20x20.png

458 ms

georg-loewy-3d-271x161-blue.png

georg-loewy-3d-271x161-blue.png

463 ms

loewy-qr-code-291x231-blue.png

loewy-qr-code-291x231-blue.png

621 ms

loewy-google-logo-75x65.png

loewy-google-logo-75x65.png

551 ms

loewy-facebook-logo-75x65.png

loewy-facebook-logo-75x65.png

549 ms

loewy-linkedin-logo-179x45.png

loewy-linkedin-logo-179x45.png

550 ms

d

d

96 ms

d

d

115 ms

d

d

77 ms

loading.gif

loading.gif

464 ms

d

d

21 ms

d

d

36 ms

d

d

35 ms

d

d

78 ms

d

d

139 ms

d

d

39 ms

d

d

69 ms

d

d

54 ms

d

d

54 ms

d

d

68 ms

p.gif

p.gif

39 ms

Accessibility Review

netzschmie.de accessibility score

76

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

netzschmie.de best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

netzschmie.de SEO score

92

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Netzschmie.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Netzschmie.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

netzschmie.de

Open Graph description is not detected on the main page of N E T Z S C H M I. 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: