Tools & Wizards About Us
mfz.de screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

mfz.de

  - START

Page Load Speed

5 sec in total

First Response

642 ms

Resources Loaded

3.9 sec

Page Rendered

421 ms

mfz.de screenshot

About Website

Welcome to mfz.de homepage info - get ready to check Mfz best content for Germany right away, or after learning these important things about mfz.de

Visit mfz.de

Key Findings

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

mfz.de performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.25

50/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

mfz.de

642 ms

beng-proxy.js

626 ms

font-awesome.min.css

730 ms

widget-runtime.css

637 ms

deploy.css

639 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 31% of them (17 requests) were addressed to the original Mfz.de, 36% (20 requests) were made to Strato-editor.com and 33% (18 requests) were made to Fonts.cm4all.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Mfz.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 377.4 kB (22%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 42.0 kB

  • Original 50.9 kB
  • After minification 50.5 kB
  • After compression 8.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 42.0 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.2 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.

JavaScript Optimization

-67%

Potential reduce by 289.8 kB

  • Original 431.7 kB
  • After minification 415.1 kB
  • After compression 141.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 289.8 kB or 67% of the original size.

CSS Optimization

-75%

Potential reduce by 45.5 kB

  • Original 60.8 kB
  • After minification 60.2 kB
  • After compression 15.3 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. Mfz.de needs all CSS files to be minified and compressed as it can save up to 45.5 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (79%)

Requests Now

24

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mfz.de

mfz.de

642 ms

beng-proxy.js

beng-proxy.js

626 ms

font-awesome.min.css

font-awesome.min.css

730 ms

widget-runtime.css

widget-runtime.css

637 ms

deploy.css

deploy.css

639 ms

slideshow-common.css

slideshow-common.css

640 ms

jquery.js

jquery.js

751 ms

prototype.js

prototype.js

825 ms

legacy.js

legacy.js

777 ms

widget-runtime.js

widget-runtime.js

879 ms

slideshow-common.js

slideshow-common.js

776 ms

deploy.js

deploy.js

845 ms

uro-min.js

uro-min.js

858 ms

main.css

main.css

886 ms

responsive.css

responsive.css

885 ms

vars.css

vars.css

443 ms

effects.js

effects.js

865 ms

tinycolor.js

tinycolor.js

888 ms

cm-templates-global-script.js

cm-templates-global-script.js

884 ms

cm_template-focus-point.js

cm_template-focus-point.js

885 ms

show.js

show.js

156 ms

css

css

296 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmZfp3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmZfp3vV5Q.ttf

572 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmrfp3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmrfp3vV5Q.ttf

604 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnnHfp3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnnHfp3vV5Q.ttf

582 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnkZfp3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnkZfp3vV5Q.ttf

599 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmZf53vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnmZf53vV5Q.ttf

594 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnlHeZ3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnlHeZ3vV5Q.ttf

593 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnl-eZ3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnl-eZ3vV5Q.ttf

719 ms

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnkZeZ3vV5Q.ttf

TK3PWkoJARApz5UCd345tuevwwQX0CwsoYkAWgWYevAauivBUnkZeZ3vV5Q.ttf

733 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

414 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

666 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

692 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

670 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

672 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

767 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

772 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

780 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

791 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

825 ms

_pixel.img

_pixel.img

109 ms

mfz%20Logo010a.png

mfz%20Logo010a.png

445 ms

picture-200

picture-200

355 ms

picture-200

picture-200

278 ms

picture-200

picture-200

273 ms

picture-200

picture-200

313 ms

picture-200

picture-200

317 ms

picture-200

picture-200

317 ms

picture-200

picture-200

314 ms

picture-200

picture-200

230 ms

picture-200

picture-200

266 ms

picture-200

picture-200

278 ms

picture-200

picture-200

291 ms

picture-200

picture-200

274 ms

MFZ_Foto01.png

MFZ_Foto01.png

1844 ms

Accessibility Review

mfz.de accessibility score

75

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

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

Form elements do not have associated labels

Best Practices

mfz.de best practices score

83

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

Page has valid source maps

SEO Factors

mfz.de SEO score

85

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

Links do not have descriptive text

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

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

mfz.de

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