Tools & Wizards About Us
metallblitz.de screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

metallblitz.de

Metall Blitz GmbH in Halle (Saale) - Metallfachhandel

Page Load Speed

3.4 sec in total

First Response

659 ms

Resources Loaded

2.5 sec

Page Rendered

229 ms

metallblitz.de screenshot

About Website

Visit metallblitz.de now to see the best up-to-date Metall Blitz content and also check out these interesting facts you probably never knew about metallblitz.de

Bei der Metall Blitz GmbH in Halle (Saale) ist Ihr Metallfachhandel. Wir bieten Ihnen Dachrinnen, NE-Metalle und Bandware inklusive fachgerechtem Service.

Visit metallblitz.de

Key Findings

We analyzed Metallblitz.de page load time and found that the first response time was 659 ms and then it took 2.7 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

metallblitz.de performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

metallblitz.de

659 ms

styles.css

299 ms

mailmask.js

201 ms

jquery.min.js

9 ms

cufon-yui.js

407 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 91% of them (30 requests) were addressed to the original Metallblitz.de, 6% (2 requests) were made to Tracker.euroweb.net and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Tracker.euroweb.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.0 kB (11%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 7.4 kB

  • Original 10.0 kB
  • After minification 7.7 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.3 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 7.4 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 13.6 kB

  • Original 1.1 MB
  • After minification 1.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. Metall Blitz images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 98.3 kB

  • Original 145.5 kB
  • After minification 140.6 kB
  • After compression 47.2 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 98.3 kB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 17.7 kB

  • Original 22.4 kB
  • After minification 15.8 kB
  • After compression 4.8 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. Metallblitz.de needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (38%)

Requests Now

32

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metallblitz.de

metallblitz.de

659 ms

styles.css

styles.css

299 ms

mailmask.js

mailmask.js

201 ms

jquery.min.js

jquery.min.js

9 ms

cufon-yui.js

cufon-yui.js

407 ms

font.js

font.js

415 ms

nivo-slider.css

nivo-slider.css

204 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

410 ms

ew-cms.css

ew-cms.css

400 ms

shadowbox.css

shadowbox.css

308 ms

yui-utilities.js

yui-utilities.js

701 ms

shadowbox.js

shadowbox.js

810 ms

tracker.js

tracker.js

1308 ms

contentKachel.jpg

contentKachel.jpg

111 ms

background.jpg

background.jpg

671 ms

bg-head.jpg

bg-head.jpg

628 ms

branding.png

branding.png

220 ms

bg-navigation.jpg

bg-navigation.jpg

207 ms

bg-navigation2.jpg

bg-navigation2.jpg

329 ms

loading.gif

loading.gif

217 ms

01.jpg

01.jpg

541 ms

02.jpg

02.jpg

748 ms

03.jpg

03.jpg

758 ms

04.jpg

04.jpg

845 ms

05.jpg

05.jpg

755 ms

06.jpg

06.jpg

931 ms

bg-seperator.jpg

bg-seperator.jpg

771 ms

li-content.png

li-content.png

847 ms

buttonMehr.jpg

buttonMehr.jpg

857 ms

bg-footerKachel.jpg

bg-footerKachel.jpg

858 ms

bg-footer.jpg

bg-footer.jpg

970 ms

counter.js

counter.js

473 ms

print.css

print.css

102 ms

Accessibility Review

metallblitz.de accessibility score

94

Accessibility Issues

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

metallblitz.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

metallblitz.de SEO score

71

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metallblitz.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 Metallblitz.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

metallblitz.de

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