Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

matthies.eu

Alles für Auto - Motorrad - Werkstatt. Einfach mehr drin

Page Load Speed

4.1 sec in total

First Response

551 ms

Resources Loaded

3.1 sec

Page Rendered

452 ms

About Website

Visit matthies.eu now to see the best up-to-date Matthies content and also check out these interesting facts you probably never knew about matthies.eu

Matthies - Großhandel für Autoteile, Motorradteile, Zubehör und Werkstattausrüstung. Der zuverlässige Partner für die Kfz-Reparaturbranche. Einfach mehr drin. ✅

Visit matthies.eu

Key Findings

We analyzed Matthies.eu page load time and found that the first response time was 551 ms and then it took 3.5 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

matthies.eu performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value1.178

1/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

matthies.eu

551 ms

www.matthies.de

429 ms

aktuelle-nachrichten.html

221 ms

aktuelle-nachrichten.html

370 ms

merged-69f93d036c2589c598fdb987c78db8c4-2202dcbc57fa64111185965b8286752f.css.gzip

541 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Matthies.eu, 96% (54 requests) were made to Matthies.de and 2% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (683 ms) relates to the external source Matthies.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.9 kB (15%)

Content Size

732.0 kB

After Optimization

623.1 kB

In fact, the total size of Matthies.eu main page is 732.0 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. 40% of websites need less resources to load. Images take 402.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 105.3 kB

  • Original 124.2 kB
  • After minification 119.1 kB
  • After compression 18.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 105.3 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 872 B

  • Original 402.8 kB
  • After minification 401.9 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. Matthies images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 151.6 kB
  • After minification 151.6 kB
  • After compression 149.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.0 kB

  • Original 53.5 kB
  • After minification 53.5 kB
  • After compression 52.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. Matthies.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

50

After Optimization

45

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

Accessibility Review

matthies.eu accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

matthies.eu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

matthies.eu SEO score

84

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Matthies.eu can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Matthies.eu 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

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