Tools & Wizards About Us
syanago.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

syanago.com

【車なごコレクション】公式サイト

Page Load Speed

7 sec in total

First Response

572 ms

Resources Loaded

6 sec

Page Rendered

466 ms

syanago.com screenshot

About Website

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

車なご（しゃなご）とは、実在する自動車メーカーのクルマを擬人化し、イラスト・マンガ・ゲームなど様々な形態でクルマ文化の魅力をお伝えするコンテンツです。車なご図鑑絶賛更新中！

Visit syanago.com

Key Findings

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

Performance Metrics

syanago.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

syanago.com

572 ms

reset.css

444 ms

common_2017new.css

441 ms

top_2017new.css

647 ms

special_2017new.css

455 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Syanago.com, 69% (82 requests) were made to Fsv-static.autoc-one.jp and 17% (20 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Fsv-static.autoc-one.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.0 kB (6%)

Content Size

5.7 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Syanago.com main page is 5.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 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.5 kB

  • Original 50.1 kB
  • After minification 43.5 kB
  • After compression 10.6 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 13% 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 39.5 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 60.8 kB

  • Original 5.1 MB
  • After minification 5.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. Syanago images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 198.4 kB

  • Original 491.9 kB
  • After minification 491.7 kB
  • After compression 293.5 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 198.4 kB or 40% of the original size.

CSS Optimization

-76%

Potential reduce by 15.2 kB

  • Original 20.1 kB
  • After minification 16.0 kB
  • After compression 4.9 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. Syanago.com needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (31%)

Requests Now

116

After Optimization

80

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

syanago.com

syanago.com

572 ms

reset.css

reset.css

444 ms

common_2017new.css

common_2017new.css

441 ms

top_2017new.css

top_2017new.css

647 ms

special_2017new.css

special_2017new.css

455 ms

rollover.js

rollover.js

442 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

937 ms

jquery.js

jquery.js

950 ms

html5shiv.js

html5shiv.js

610 ms

selectivizr.js

selectivizr.js

608 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

628 ms

syanago_index.js

syanago_index.js

777 ms

jquery.zlayer.min.js

jquery.zlayer.min.js

776 ms

gtm.js

gtm.js

16 ms

bdh.js

bdh.js

444 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

6 ms

gtm.js

gtm.js

78 ms

gpt.js

gpt.js

90 ms

analytics.js

analytics.js

89 ms

bg_2017new.png

bg_2017new.png

298 ms

img_logo-top.png

img_logo-top.png

346 ms

img_titleNews_2017new.png

img_titleNews_2017new.png

345 ms

img_titleSpecial.png

img_titleSpecial.png

345 ms

z_42.png

z_42.png

516 ms

z__41.png

z__41.png

981 ms

z_40.png

z_40.png

392 ms

z_39.png

z_39.png

673 ms

z_38.png

z_38.png

507 ms

z_37.png

z_37.png

1314 ms

z_36.png

z_36.png

564 ms

z_35.png

z_35.png

691 ms

z_34.png

z_34.png

700 ms

z_33.png

z_33.png

743 ms

z_32.png

z_32.png

835 ms

z_31.png

z_31.png

846 ms

z_30.png

z_30.png

869 ms

z_29.png

z_29.png

910 ms

z_28.png

z_28.png

1003 ms

z_27.png

z_27.png

1015 ms

z_26.png

z_26.png

1213 ms

z_25.png

z_25.png

1079 ms

z_24.png

z_24.png

2167 ms

z_23.png

z_23.png

1169 ms

z_22.png

z_22.png

1183 ms

z_21.png

z_21.png

1248 ms

z_20.png

z_20.png

1499 ms

z_19.png

z_19.png

1352 ms

z_18.png

z_18.png

1386 ms

z_17.png

z_17.png

1416 ms

z_16.png

z_16.png

3638 ms

z_15.png

z_15.png

1521 ms

z_14.png

z_14.png

1559 ms

z_13.png

z_13.png

1584 ms

z_12.png

z_12.png

1664 ms

pubads_impl.js

pubads_impl.js

143 ms

ppub_config

ppub_config

225 ms

z_11.png

z_11.png

1624 ms

collect

collect

184 ms

sdk.js

sdk.js

181 ms

widgets.js

widgets.js

70 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

114 ms

z_10.png

z_10.png

1444 ms

js

js

67 ms

sdk.js

sdk.js

24 ms

settings

settings

101 ms

z_09.png

z_09.png

1415 ms

z_08.png

z_08.png

1496 ms

60 ms

z_07.png

z_07.png

1501 ms

z_06.png

z_06.png

1524 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

7 ms

embeds

embeds

43 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

21 ms

Syanago_Staff

Syanago_Staff

73 ms

z_05.png

z_05.png

1421 ms

z_04.png

z_04.png

1493 ms

z_03.png

z_03.png

1470 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

3 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

23 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

25 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

25 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

61 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

65 ms

_buildManifest.js

_buildManifest.js

59 ms

_ssgManifest.js

_ssgManifest.js

77 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

14 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

15 ms

z_02.png

z_02.png

1418 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

6 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

13 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

11 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

30 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

12 ms

z_01.png

z_01.png

1406 ms

q4.jpg

q4.jpg

1475 ms

q3.jpg

q3.jpg

1461 ms

q2.jpg

q2.jpg

1431 ms

q1.jpg

q1.jpg

1420 ms

bnr_joyalphard.jpg

bnr_joyalphard.jpg

2443 ms

bnr_joynboxs.jpg

bnr_joynboxs.jpg

1431 ms

bnr_wiki.png

bnr_wiki.png

1393 ms

bnr_DENGEKI.png

bnr_DENGEKI.png

1437 ms

img_goToTop.png

img_goToTop.png

1420 ms

bg_check.png

bg_check.png

1428 ms

h1bg_2017new.png

h1bg_2017new.png

1370 ms

bg_header-top_2nd_2017new.png

bg_header-top_2nd_2017new.png

3230 ms

infoLink.png

infoLink.png

1403 ms

bg_nav.png

bg_nav.png

1427 ms

img_navi_2017new.png

img_navi_2017new.png

1396 ms

bg_top_twitter.png

bg_top_twitter.png

1437 ms

bg_top_frameRightTop.png

bg_top_frameRightTop.png

1456 ms

bg_top_frameRightBottom.png

bg_top_frameRightBottom.png

1461 ms

bg_top_frameRight.png

bg_top_frameRight.png

1466 ms

bg_frameTop.png

bg_frameTop.png

1489 ms

bg_frameBottom.png

bg_frameBottom.png

1484 ms

bg_frame.png

bg_frame.png

1552 ms

special_title01.png

special_title01.png

1514 ms

special_title02.png

special_title02.png

1525 ms

Accessibility Review

syanago.com accessibility score

60

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

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

syanago.com SEO score

81

Search Engine Optimization Advices

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Syanago.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Syanago.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

syanago.com

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