7.1 sec in total
518 ms
5.1 sec
1.6 sec
Visit brabus.co.jp now to see the best up-to-date BRABUS content and also check out these interesting facts you probably never knew about brabus.co.jp
ドイツのベンツ用チューニングカーメーカーブラバスのパーツ日本総輸入元会社、株式会社エクゼ
Visit brabus.co.jpWe analyzed Brabus.co.jp page load time and found that the first response time was 518 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
brabus.co.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.7 s
32/100
25%
Value8.2 s
20/100
10%
Value60 ms
100/100
30%
Value3.196
0/100
15%
Value4.7 s
80/100
10%
518 ms
21 ms
170 ms
494 ms
506 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 91% of them (43 requests) were addressed to the original Brabus.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Brabus.co.jp.
Page size can be reduced by 219.6 kB (4%)
5.9 MB
5.7 MB
In fact, the total size of Brabus.co.jp main page is 5.9 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. 40% of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.
Potential reduce by 10.1 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 1.9 kB, which is 14% 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 10.1 kB or 74% of the original size.
Potential reduce by 103.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. BRABUS images are well optimized though.
Potential reduce by 69.3 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 69.3 kB or 48% of the original size.
Potential reduce by 36.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. Brabus.co.jp needs all CSS files to be minified and compressed as it can save up to 36.4 kB or 77% of the original size.
Number of requests can be reduced by 18 (39%)
46
28
The browser has sent 46 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 8 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
brabus.co.jp
518 ms
jquery.min.js
21 ms
viewport.js
170 ms
iscroll.js
494 ms
bootstrap.min.js
506 ms
drawer.min.js
339 ms
jquery.flexslider.js
513 ms
style-flexslider.css
349 ms
bike.css
349 ms
js
54 ms
exe.css
171 ms
styles_pc.css
172 ms
navi.css
175 ms
table.css
170 ms
ie.css
172 ms
exe-brabus-logo.svg
170 ms
main.jpg
1918 ms
main.jpg
1182 ms
main.jpg
1016 ms
main-i.jpg
822 ms
main-i.jpg
1568 ms
main-i.jpg
1016 ms
main.jpg
990 ms
main-i.jpg
1158 ms
exe-logo_sp.svg
1184 ms
brabus-logo_sp.svg
1185 ms
exe-logo.svg
1322 ms
brabus-logo.svg
1348 ms
mv_filter.svg
1352 ms
subimg_0101.jpg
1356 ms
subimg_0102.jpg
1488 ms
new_item_003.jpg
1853 ms
new_item_001.jpg
1522 ms
new_item_002.jpg
1526 ms
main.jpg
1654 ms
c_w205.jpg
1862 ms
cls_c257.jpg
1701 ms
a_w177.jpg
2958 ms
logo_mandai.svg
1818 ms
ga.js
7 ms
__utm.gif
13 ms
exe_sp.css
170 ms
styles_sp.css
170 ms
navi_sp.css
170 ms
drawer.min.css
171 ms
exe.css
171 ms
controls.png
171 ms
brabus.co.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
brabus.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
brabus.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brabus.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Brabus.co.jp 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.
brabus.co.jp
Open Graph description is not detected on the main page of BRABUS. 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: