Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

maximus.de

Herrenmode in Übergrößen & großen Größen | Pfundskerl

Page Load Speed

3.5 sec in total

First Response

257 ms

Resources Loaded

2.8 sec

Page Rendered

427 ms

maximus.de screenshot

About Website

Click here to check amazing Maximus content for Germany. Otherwise, check out these important facts you probably never knew about maximus.de

Entdecke die starken Outfits beim Spezialisten für Übergrößen-Kleidung in perfekter Passform von XXL bis 14XL: Bestell im Pfundskerl Onlineshop Männermode in großen Größen!

Visit maximus.de

Key Findings

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

Performance Metrics

maximus.de performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

12/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

maximus.de

257 ms

maximus.de

363 ms

www.pfundskerl-xxl.de

209 ms

gtm.js

742 ms

style.min.css

17 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Maximus.de, 90% (113 requests) were made to Pfundskerl-xxl.de and 3% (4 requests) were made to Connect.ekomi.de. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Pfundskerl-xxl.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 410.0 kB (28%)

Content Size

1.4 MB

After Optimization

1.0 MB

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

HTML Optimization

-92%

Potential reduce by 279.0 kB

  • Original 303.4 kB
  • After minification 151.0 kB
  • After compression 24.4 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 152.4 kB, which is 50% 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 279.0 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 10.7 kB

  • Original 667.3 kB
  • After minification 656.6 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. Maximus images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 119.9 kB

  • Original 359.8 kB
  • After minification 359.6 kB
  • After compression 239.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 119.9 kB or 33% of the original size.

CSS Optimization

-0%

Potential reduce by 391 B

  • Original 117.7 kB
  • After minification 117.7 kB
  • After compression 117.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. Maximus.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (26%)

Requests Now

117

After Optimization

87

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

Accessibility Review

maximus.de accessibility score

72

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

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.

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

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

maximus.de SEO score

86

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

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

Open Graph data is detected on the main page of Maximus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: