Tools & Wizards About Us
mumdat.de screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

mumdat.de

markmann + müller I Beratung und Software für den Mittelstand

Page Load Speed

3.6 sec in total

First Response

198 ms

Resources Loaded

2.8 sec

Page Rendered

611 ms

mumdat.de screenshot

About Website

Welcome to mumdat.de homepage info - get ready to check Mumdat best content right away, or after learning these important things about mumdat.de

Finden Sie standardnahe Software-Lösungen für Ihre Branche. ✓ Stahl ✓ NE-Metall ✓ Oberflächen ✓ metallverarbeitende Branche

Visit mumdat.de

Key Findings

We analyzed Mumdat.de page load time and found that the first response time was 198 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

mumdat.de performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

mumdat.de

198 ms

www.mumdat.de

693 ms

uc.js

29 ms

bootstrap.min.css

104 ms

all.min.css

205 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 87% of them (59 requests) were addressed to the original Mumdat.de, 4% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Matomo.wirsinddesigner.de. The less responsive or slowest element that took the longest time to load (797 ms) belongs to the original domain Mumdat.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.8 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 36.0 kB

  • Original 49.3 kB
  • After minification 48.6 kB
  • After compression 13.3 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 36.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 12.5 kB

  • Original 1.0 MB
  • After minification 1.0 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. Mumdat images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 94.6 kB

  • Original 460.5 kB
  • After minification 460.5 kB
  • After compression 365.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 94.6 kB or 21% of the original size.

CSS Optimization

-1%

Potential reduce by 723 B

  • Original 117.0 kB
  • After minification 117.0 kB
  • After compression 116.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. Mumdat.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (64%)

Requests Now

56

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mumdat.de

mumdat.de

198 ms

www.mumdat.de

www.mumdat.de

693 ms

uc.js

uc.js

29 ms

bootstrap.min.css

bootstrap.min.css

104 ms

all.min.css

all.min.css

205 ms

animate.min.css

animate.min.css

277 ms

simple-line-icons.min.css

simple-line-icons.min.css

281 ms

owl.carousel.min.css

owl.carousel.min.css

282 ms

owl.theme.default.min.css

owl.theme.default.min.css

282 ms

magnific-popup.min.css

magnific-popup.min.css

292 ms

swiper.min.css

swiper.min.css

303 ms

mumdat.min.css

mumdat.min.css

558 ms

style.css

style.css

382 ms

js

js

69 ms

jquery.min.js

jquery.min.js

481 ms

jquery.appear.min.js

jquery.appear.min.js

383 ms

jquery.easing.min.js

jquery.easing.min.js

394 ms

jquery.cookie.min.js

jquery.cookie.min.js

400 ms

popper.min.js

popper.min.js

476 ms

bootstrap.min.js

bootstrap.min.js

708 ms

common.min.js

common.min.js

496 ms

jquery.validate.min.js

jquery.validate.min.js

500 ms

jquery.easypiechart.min.js

jquery.easypiechart.min.js

708 ms

jquery.gmap.min.js

jquery.gmap.min.js

709 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

710 ms

jquery.isotope.min.js

jquery.isotope.min.js

708 ms

owl.carousel.min.js

owl.carousel.min.js

710 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

712 ms

jquery.vide.min.js

jquery.vide.min.js

711 ms

vivus.min.js

vivus.min.js

712 ms

swiper.min.js

swiper.min.js

757 ms

theme.js

theme.js

756 ms

custom.js

custom.js

757 ms

theme.init.js

theme.init.js

797 ms

mtiFontTrackingCode.js

mtiFontTrackingCode.js

195 ms

gtm.js

gtm.js

107 ms

matomo.js

matomo.js

713 ms

logo_2.svg

logo_2.svg

180 ms

icon-suchen.svg

icon-suchen.svg

205 ms

header_20221125-057633b9.jpg

header_20221125-057633b9.jpg

462 ms

stahl-1-3225ab0b.jpg

stahl-1-3225ab0b.jpg

463 ms

nemetall-1-eeb1eca0.jpg

nemetall-1-eeb1eca0.jpg

464 ms

oberflaeche-1-c8cfcd08.jpg

oberflaeche-1-c8cfcd08.jpg

382 ms

metall-2-16749cd2.jpg

metall-2-16749cd2.jpg

528 ms

branche-stahl-2-17f6be2b.jpg

branche-stahl-2-17f6be2b.jpg

462 ms

branche-nemetall-09950468.jpg

branche-nemetall-09950468.jpg

532 ms

branche-oberflaeche-c3eb462b.jpg

branche-oberflaeche-c3eb462b.jpg

490 ms

branche-metall-2-deb2cf6b.jpg

branche-metall-2-deb2cf6b.jpg

499 ms

projektschablone-teaser-1a7fcede.jpg

projektschablone-teaser-1a7fcede.jpg

509 ms

bg-footer.jpg

bg-footer.jpg

524 ms

MicrosoftPartner_cropped-11b6cf11.png

MicrosoftPartner_cropped-11b6cf11.png

590 ms

icon-linkedin.svg

icon-linkedin.svg

603 ms

7f34d676-21e3-4ac7-998d-04f8428dff18.woff

7f34d676-21e3-4ac7-998d-04f8428dff18.woff

493 ms

e478d528-f58a-473a-bf84-d8b21b7f7107.woff

e478d528-f58a-473a-bf84-d8b21b7f7107.woff

513 ms

ab45fe39-2036-4dba-b878-a74d8140e8e7.woff

ab45fe39-2036-4dba-b878-a74d8140e8e7.woff

547 ms

c061ab4d-74ab-4c1c-9399-152de03f973d.woff

c061ab4d-74ab-4c1c-9399-152de03f973d.woff

546 ms

d154b4cc-8431-4ad7-b2bf-f46a84f1fbe7.woff

d154b4cc-8431-4ad7-b2bf-f46a84f1fbe7.woff

600 ms

7785de4d-b6ce-4272-a2b3-439b3066b1df.woff

7785de4d-b6ce-4272-a2b3-439b3066b1df.woff

601 ms

e9889c96-b678-47f3-99e2-e50426ce470b.woff

e9889c96-b678-47f3-99e2-e50426ce470b.woff

599 ms

19e7d03b-3090-4530-8910-2424f7451642.woff

19e7d03b-3090-4530-8910-2424f7451642.woff

619 ms

analytics.js

analytics.js

31 ms

fa-solid-900.woff

fa-solid-900.woff

644 ms

fa-regular-400.woff

fa-regular-400.woff

592 ms

icon-plus.svg

icon-plus.svg

614 ms

collect

collect

13 ms

js

js

134 ms

matomo.php

matomo.php

557 ms

salesviewer.org

salesviewer.org

252 ms

Accessibility Review

mumdat.de accessibility score

91

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

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

mumdat.de SEO score

93

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

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

    DE

  • Encoding

    UTF-8

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

mumdat.de

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