Access brabus.com. BRABUS

34

Performance

Renders faster than
54% of other websites
51

Accessibility

Visual factors better than
that of 21% of websites
83

Best Practices

More advanced features
available than in
55% of websites
86

SEO

Google-friendlier than
60% of websites

First Response

304 ms

Resources Loaded

1.3 sec

Page Rendered

4.5 sec

About Website

Visit brabus.com now to see the best up-to-date BRABUS content for Germany and also check out these interesting facts you probably never knew about brabus.com

BRABUS - moderner, maßgeschneiderter Luxus aus Bottrop

Visit brabus.com

Key Findings

We analyzed Brabus.com page load time and found that the first response time was 304 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value40.7 s

0/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value40.9 s

0/100

10%

brabus.com

304 ms

www.brabus.com

129 ms

project.min.css

21 ms

jquery.min.js

45 ms

CookieHandling.js

14 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 98% of them (94 requests) were addressed to the original Brabus.com, 2% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (554 ms) belongs to the original domain Brabus.com.

Content Size

20.7 MB

After Optimization

18.9 MB

In fact, the total size of Brabus.com main page is 20.7 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. Only a small number of websites need less resources to load. Images take 20.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 119.5 kB

Original 145.2 kB
After minification 142.0 kB
After compression 25.8 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 119.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 1.3 MB

Original 20.0 MB
After minification 18.7 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. BRABUS images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 334.2 kB

Original 519.7 kB
After minification 510.8 kB
After compression 185.4 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 334.2 kB or 64% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 49.7 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.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

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

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

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 Brabus.com 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 Brabus.com 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

brabus.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

BRABUS

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)