Tools & Wizards About Us
passat.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

passat.jp

Passat | ワゴン | フォルクスワーゲン公式

Page Load Speed

9.2 sec in total

First Response

546 ms

Resources Loaded

7.7 sec

Page Rendered

952 ms

passat.jp screenshot

About Website

Welcome to passat.jp homepage info - get ready to check Passat best content right away, or after learning these important things about passat.jp

フォルクスワーゲン「Passat」のご案内。ギャラリー、360度ビュー、ハイライト、カラーなどクルマの詳細をご覧いただけます。

Visit passat.jp

Key Findings

We analyzed Passat.jp page load time and found that the first response time was 546 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

passat.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

passat.jp

546 ms

passat.volkswagen.co.jp

693 ms

style.css

468 ms

top.css

367 ms

eluminate.js

13 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Passat.jp, 75% (114 requests) were made to Passat.volkswagen.co.jp and 5% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Passat.volkswagen.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 757.0 kB (8%)

Content Size

10.0 MB

After Optimization

9.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Passat.jp main page is 10.0 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 9.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 31.9 kB

  • Original 37.6 kB
  • After minification 31.0 kB
  • After compression 5.7 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 6.6 kB, which is 17% 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 31.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 312.0 kB

  • Original 9.4 MB
  • After minification 9.1 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. Passat images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 391.7 kB

  • Original 596.5 kB
  • After minification 589.2 kB
  • After compression 204.8 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 391.7 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 21.4 kB

  • Original 25.7 kB
  • After minification 21.3 kB
  • After compression 4.2 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. Passat.jp needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

142

After Optimization

112

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

passat.jp

passat.jp

546 ms

passat.volkswagen.co.jp

passat.volkswagen.co.jp

693 ms

style.css

style.css

468 ms

top.css

top.css

367 ms

eluminate.js

eluminate.js

13 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

834 ms

jquery.cookie.min.js

jquery.cookie.min.js

314 ms

scrollMe.js

scrollMe.js

470 ms

index.js

index.js

590 ms

vwjp.js

vwjp.js

156 ms

head.js

head.js

56 ms

90395534.js

90395534.js

16 ms

cookie-id.js

cookie-id.js

89 ms

tag.js

tag.js

33 ms

munchkin.js

munchkin.js

32 ms

loding.gif

loding.gif

160 ms

logo.png

logo.png

184 ms

nav_01.png

nav_01.png

157 ms

nav_02.png

nav_02.png

223 ms

ttl_dropmenu01.png

ttl_dropmenu01.png

313 ms

img_dropmenu01_01.png

img_dropmenu01_01.png

633 ms

img_dropmenu01_02.png

img_dropmenu01_02.png

918 ms

img_dropmenu01_03.png

img_dropmenu01_03.png

738 ms

nav_03.png

nav_03.png

379 ms

ttl_dropmenu02.png

ttl_dropmenu02.png

506 ms

img_dropmenu02_01.png

img_dropmenu02_01.png

1161 ms

nav_04.png

nav_04.png

628 ms

ttl_dropmenu03.png

ttl_dropmenu03.png

625 ms

img_dropmenu03_01.png

img_dropmenu03_01.png

1249 ms

img_dropmenu03_02.png

img_dropmenu03_02.png

845 ms

nav_05.png

nav_05.png

787 ms

ttl_dropmenu04.png

ttl_dropmenu04.png

921 ms

img_dropmenu04_01.png

img_dropmenu04_01.png

1103 ms

img_dropmenu04_02.png

img_dropmenu04_02.png

1239 ms

nav_06.png

nav_06.png

1100 ms

ttl_dropmenu05.png

ttl_dropmenu05.png

1104 ms

img_dropmenu05_01.png

img_dropmenu05_01.png

1283 ms

img_dropmenu05_05.png

img_dropmenu05_05.png

1416 ms

img_dropmenu05_03.png

img_dropmenu05_03.png

1286 ms

img_dropmenu05_04.png

img_dropmenu05_04.png

1477 ms

nav_07.png

nav_07.png

1437 ms

icn_car.png

icn_car.png

1403 ms

img_dropmenu06_01.png

img_dropmenu06_01.png

1465 ms

img_dropmenu06_02.png

img_dropmenu06_02.png

1469 ms

icn_new.png

icn_new.png

1559 ms

icn_news.png

icn_news.png

1571 ms

icn_facebook.png

icn_facebook.png

1632 ms

icn_twitter.png

icn_twitter.png

1647 ms

munchkin.js

munchkin.js

11 ms

tag

tag

12 ms

cm

cm

44 ms

visitWebPage

visitWebPage

14 ms

tag

tag

6 ms

img_menu01.png

img_menu01.png

1775 ms

btn_menu01.png

btn_menu01.png

1483 ms

img_menu02.png

img_menu02.png

1880 ms

btn_menu02.png

btn_menu02.png

1568 ms

img_menu03.png

img_menu03.png

1852 ms

btn_menu03.png

btn_menu03.png

1571 ms

img_menu04.png

img_menu04.png

1706 ms

btn_menu04.png

btn_menu04.png

1513 ms

vwjp.js

vwjp.js

267 ms

conversion_async.js

conversion_async.js

67 ms

ttl_menu01.png

ttl_menu01.png

1446 ms

img_menu05.png

img_menu05.png

1517 ms

48 ms

42 ms

45 ms

45 ms

38 ms

44 ms

52 ms

52 ms

45 ms

46 ms

43 ms

43 ms

43 ms

41 ms

43 ms

44 ms

btn_menu05.png

btn_menu05.png

1423 ms

img_menu09.png

img_menu09.png

1633 ms

btn_menu06.png

btn_menu06.png

1572 ms

smartsignals_client.min.js

smartsignals_client.min.js

545 ms

img_menu07.png

img_menu07.png

1471 ms

btn_menu07.png

btn_menu07.png

1440 ms

img_menu08.png

img_menu08.png

1499 ms

btn_menu08.png

btn_menu08.png

1289 ms

btn_top_prev.png

btn_top_prev.png

1463 ms

btn_top_next.png

btn_top_next.png

1262 ms

icn_close02.png

icn_close02.png

1287 ms

bnr_06.png

bnr_06.png

1516 ms

text_01.png

text_01.png

1256 ms

btn_passat.png

btn_passat.png

1260 ms

btn_passatvariant.png

btn_passatvariant.png

1272 ms

polyfill_01.js

polyfill_01.js

447 ms

bg_01.png

bg_01.png

2241 ms

bg_01.png

bg_01.png

2752 ms

text_01.png

text_01.png

1169 ms

btn_more.png

btn_more.png

1238 ms

text_01.png

text_01.png

1239 ms

img_01.png

img_01.png

1419 ms

btn_01.png

btn_01.png

1347 ms

img_02.png

img_02.png

1646 ms

btn_02.png

btn_02.png

1275 ms

img_03.png

img_03.png

1441 ms

bg_01.png

bg_01.png

2775 ms

text_01.png

text_01.png

1406 ms

text_01.png

text_01.png

1564 ms

img_01.png

img_01.png

1761 ms

xdmUidProvider.html

xdmUidProvider.html

4 ms

xdmUidProvider.min.js

xdmUidProvider.min.js

7 ms

btn_01.png

btn_01.png

1490 ms

track

track

216 ms

img_03.png

img_03.png

1575 ms

bg_01.png

bg_01.png

2483 ms

text_01.png

text_01.png

1661 ms

xdmProvider.html

xdmProvider.html

5 ms

btn_more_w.png

btn_more_w.png

1652 ms

xdmProvider.min.js

xdmProvider.min.js

7 ms

text_01.png

text_01.png

1686 ms

img_01.png

img_01.png

1968 ms

btn_01.png

btn_01.png

1787 ms

img_02.png

img_02.png

2025 ms

btn_02.png

btn_02.png

1782 ms

img_03.png

img_03.png

1932 ms

bg_01.png

bg_01.png

3772 ms

text_01.png

text_01.png

1997 ms

text_01.png

text_01.png

1999 ms

img_01.png

img_01.png

2107 ms

btn_01.png

btn_01.png

2046 ms

img_02.png

img_02.png

2058 ms

btn_02.png

btn_02.png

2141 ms

img_03.png

img_03.png

2175 ms

bg_01.png

bg_01.png

2542 ms

text_01.png

text_01.png

2105 ms

img_01.png

img_01.png

2032 ms

img_07.png

img_07.png

2067 ms

img_03.png

img_03.png

2119 ms

img_04.png

img_04.png

2086 ms

btn_footerNavi01.png

btn_footerNavi01.png

1990 ms

btn_footerNavi02.png

btn_footerNavi02.png

2009 ms

btn_footerNavi03.png

btn_footerNavi03.png

2033 ms

btn_footerNavi04.png

btn_footerNavi04.png

1941 ms

btn_footer01.png

btn_footer01.png

1948 ms

btn_footer02.png

btn_footer02.png

1876 ms

btn_footer03.png

btn_footer03.png

1862 ms

btn_footer04.png

btn_footer04.png

1861 ms

btn_footer05.png

btn_footer05.png

1763 ms

icn_blank.png

icn_blank.png

1645 ms

copyright.png

copyright.png

1676 ms

Accessibility Review

passat.jp accessibility score

73

Accessibility Issues

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.

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

Links do not have a discernible name

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

passat.jp best practices score

67

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

Browser errors were logged to the console

SEO Factors

passat.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 Passat.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 Passat.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

passat.jp

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