Tools & Wizards About Us
metallograf.de screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

metallograf.de

Metallografie und Werkstoffprüfung bei Stahl - für Metallograf und Werkstoffprüfer

Page Load Speed

2.2 sec in total

First Response

322 ms

Resources Loaded

1.8 sec

Page Rendered

107 ms

metallograf.de screenshot

About Website

Visit metallograf.de now to see the best up-to-date Metallograf content for Germany and also check out these interesting facts you probably never knew about metallograf.de

Informationsseite fr Metallografen auf dem Stahlsektor und jeden den das Thema Metallografie interessiert

Visit metallograf.de

Key Findings

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

Performance Metrics

metallograf.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

metallograf.de

322 ms

framesetnachladen1deu.js

98 ms

menueoben.htm

102 ms

hauptmenue.htm

207 ms

menueunten.php

1225 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Metallograf.de, 5% (2 requests) were made to Lober-net.de. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Lober-net.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.0 kB (46%)

Content Size

15.2 kB

After Optimization

8.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Metallograf.de main page is 15.2 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 9.7 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 1.2 kB

  • Original 2.0 kB
  • After minification 1.8 kB
  • After compression 725 B

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 1.2 kB or 63% of the original size.

Image Optimization

-33%

Potential reduce by 3.2 kB

  • Original 9.7 kB
  • After minification 6.5 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. Obviously, Metallograf needs image optimization as it can save up to 3.2 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 2.6 kB

  • Original 3.6 kB
  • After minification 2.9 kB
  • After compression 932 B

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 2.6 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (8%)

Requests Now

39

After Optimization

36

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

metallograf.de

metallograf.de

322 ms

framesetnachladen1deu.js

framesetnachladen1deu.js

98 ms

menueoben.htm

menueoben.htm

102 ms

hauptmenue.htm

hauptmenue.htm

207 ms

menueunten.php

menueunten.php

1225 ms

banneroben.htm

banneroben.htm

208 ms

gruss.htm

gruss.htm

210 ms

bannerunten.htm

bannerunten.htm

210 ms

bgoecke.jpg

bgoecke.jpg

116 ms

de.gif

de.gif

193 ms

en-us.gif

en-us.gif

207 ms

hauptauswahl-n1.gif

hauptauswahl-n1.gif

106 ms

hauptauswahl-a1.gif

hauptauswahl-a1.gif

115 ms

hauptauswahl-n2.gif

hauptauswahl-n2.gif

119 ms

hauptauswahl-a2.gif

hauptauswahl-a2.gif

120 ms

hauptauswahl-n3.gif

hauptauswahl-n3.gif

190 ms

hauptauswahl-a3.gif

hauptauswahl-a3.gif

206 ms

hauptauswahl-n4.gif

hauptauswahl-n4.gif

210 ms

hauptauswahl-a4.gif

hauptauswahl-a4.gif

214 ms

hauptauswahl-n5.gif

hauptauswahl-n5.gif

220 ms

hauptauswahl-a5.gif

hauptauswahl-a5.gif

222 ms

hauptauswahl-n6.gif

hauptauswahl-n6.gif

286 ms

hauptauswahl-a6.gif

hauptauswahl-a6.gif

305 ms

hauptauswahl-n7.gif

hauptauswahl-n7.gif

310 ms

hauptauswahl-a7.gif

hauptauswahl-a7.gif

317 ms

hauptauswahl-n8.gif

hauptauswahl-n8.gif

321 ms

hauptauswahl-a8.gif

hauptauswahl-a8.gif

324 ms

hauptauswahl-n11.gif

hauptauswahl-n11.gif

380 ms

hauptauswahl-a11.gif

hauptauswahl-a11.gif

404 ms

bginhalt.jpg

bginhalt.jpg

410 ms

bgobanner.jpg

bgobanner.jpg

412 ms

banner-dew.gif

banner-dew.gif

619 ms

framesetnachladen2deu.js

framesetnachladen2deu.js

420 ms

ticker.js

ticker.js

472 ms

de-en-umschalten.js

de-en-umschalten.js

496 ms

bghaupt.jpg

bghaupt.jpg

98 ms

bgubanner.jpg

bgubanner.jpg

102 ms

suchen-k.gif

suchen-k.gif

104 ms

de-en.gif

de-en.gif

105 ms

bguecke.jpg

bguecke.jpg

104 ms

Accessibility Review

metallograf.de accessibility score

33

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

<frame> or <iframe> elements do not have a title

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

Best Practices

metallograf.de 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

SEO Factors

metallograf.de SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metallograf.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 Metallograf.de main page’s claimed encoding is . 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

metallograf.de

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