Tools & Wizards About Us
mercedes-benz.co.jp screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mercedes-benz.co.jp

メルセデス・ベンツ日本 オフィシャルサイト

Page Load Speed

1.3 sec in total

First Response

195 ms

Resources Loaded

1.1 sec

Page Rendered

58 ms

mercedes-benz.co.jp screenshot

About Website

Welcome to mercedes-benz.co.jp homepage info - get ready to check Mercedes Benz best content for Japan right away, or after learning these important things about mercedes-benz.co.jp

メルセデス・ベンツ公式サイト。カタログや詳細情報、正規販売店や試乗車の検索、イベントやキャンペーンなど、メルセデスのさまざまな情報をご紹介しています。

Visit mercedes-benz.co.jp

Key Findings

We analyzed Mercedes-benz.co.jp page load time and found that the first response time was 195 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

mercedes-benz.co.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.115

85/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

www.mercedes-benz.co.jp

195 ms

owc.min.css

146 ms

vue.min.js

174 ms

globals.css

187 ms

globals.css

195 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Mercedes-benz.co.jp, 86% (37 requests) were made to Assets.oneweb.mercedes-benz.com and 2% (1 request) were made to Userlike-cdn-widgets.s3-eu-west-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (476 ms) relates to the external source Assets.oneweb.mercedes-benz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (70%)

Content Size

2.1 MB

After Optimization

648.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Mercedes-benz.co.jp main page is 2.1 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. 55% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 123.0 kB

  • Original 160.6 kB
  • After minification 153.9 kB
  • After compression 37.5 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 123.0 kB or 77% of the original size.

JavaScript Optimization

-68%

Potential reduce by 1.2 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 558.7 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 1.2 MB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 198.4 kB

  • Original 250.4 kB
  • After minification 249.8 kB
  • After compression 52.0 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. Mercedes-benz.co.jp needs all CSS files to be minified and compressed as it can save up to 198.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (95%)

Requests Now

42

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

www.mercedes-benz.co.jp

www.mercedes-benz.co.jp

195 ms

owc.min.css

owc.min.css

146 ms

vue.min.js

vue.min.js

174 ms

globals.css

globals.css

187 ms

globals.css

globals.css

195 ms

style.css

style.css

185 ms

style.css

style.css

171 ms

style.css

style.css

171 ms

style.css

style.css

191 ms

style.css

style.css

215 ms

cookie-banner.esm.js

cookie-banner.esm.js

190 ms

cookie-banner.js

cookie-banner.js

191 ms

publish.0.20240429164859.min.js

publish.0.20240429164859.min.js

30 ms

publish.0.20240429164859.min.css

publish.0.20240429164859.min.css

265 ms

publish.0.20240429164859.min.css

publish.0.20240429164859.min.css

155 ms

index.js

index.js

210 ms

owc.min.js

owc.min.js

210 ms

index.js

index.js

231 ms

workbench.esm.js

workbench.esm.js

215 ms

workbench.js

workbench.js

236 ms

globals.css

globals.css

216 ms

c11y.esm.js

c11y.esm.js

238 ms

c11y.js

c11y.js

220 ms

workbench.esm.js

workbench.esm.js

302 ms

index.js

index.js

261 ms

index.js

index.js

237 ms

index.js

index.js

246 ms

ciam.js

ciam.js

276 ms

wkomodule.js

wkomodule.js

270 ms

bootstrap.js

bootstrap.js

476 ms

bootstrap.js

bootstrap.js

264 ms

bootstrap.js

bootstrap.js

272 ms

index.wc.js

index.wc.js

284 ms

index.js

index.js

290 ms

vmos-flyout-1.16.3.min.js

vmos-flyout-1.16.3.min.js

290 ms

index.wc.js

index.wc.js

288 ms

bootstrap-esm.js

bootstrap-esm.js

301 ms

footnote-reference-component.esm.js

footnote-reference-component.esm.js

310 ms

footnote-component.esm.js

footnote-component.esm.js

339 ms

74c536d878554ddb9994111732ead2acc273cc8a0bac4f9394664bfdb37e1af3.js

74c536d878554ddb9994111732ead2acc273cc8a0bac4f9394664bfdb37e1af3.js

310 ms

index.js

index.js

337 ms

globals.css

globals.css

114 ms

gtm.js

gtm.js

144 ms

Accessibility Review

mercedes-benz.co.jp accessibility score

100

Accessibility Issues

Best Practices

mercedes-benz.co.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mercedes-benz.co.jp SEO score

92

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mercedes-benz.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Mercedes-benz.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.

Social Sharing Optimization

mercedes-benz.co.jp

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