Tools & Wizards About Us
goin.jp screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

goin.jp

GOIN

Page Load Speed

7.5 sec in total

First Response

333 ms

Resources Loaded

6.9 sec

Page Rendered

347 ms

goin.jp screenshot

About Website

Welcome to goin.jp homepage info - get ready to check GOIN best content for Japan right away, or after learning these important things about goin.jp

GOINは自動車やドライブ旅行、カーライフスタイルに関する情報が集まるキュレーションメディアです。新車・中古車の購入に役立つ情報から、ドライブ旅行の情報や車用品・カスタムパーツ・イベント・レースの紹介など車情報盛りだくさん。

Visit goin.jp

Key Findings

We analyzed Goin.jp page load time and found that the first response time was 333 ms and then it took 7.2 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

goin.jp performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

goin.jp

333 ms

goin.jp

1161 ms

application-83223f7a3566dc53cc8af20b0a2239dfd0d1dbbc02355506cdeca99b616c73ac.css

323 ms

bower-core-d11f324a786b1fb30ec53c59be5b1b55f05c18e76cc6e1236b7fe54b1ad401f6.js

905 ms

application-da651035f5c8687803628227c0ca36e8e011ae0d9a5c82c40b5af5dea2524244.js

485 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 10% of them (8 requests) were addressed to the original Goin.jp, 41% (33 requests) were made to Goin.cdn-dena.com and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Goin.cdn-dena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.8 kB (13%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Goin.jp main page is 3.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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 107.5 kB

  • Original 139.1 kB
  • After minification 133.6 kB
  • After compression 31.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 107.5 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 40.9 kB

  • Original 2.5 MB
  • After minification 2.5 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. GOIN images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 154.0 kB

  • Original 259.7 kB
  • After minification 259.7 kB
  • After compression 105.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 154.0 kB or 59% of the original size.

CSS Optimization

-80%

Potential reduce by 83.4 kB

  • Original 103.6 kB
  • After minification 101.5 kB
  • After compression 20.3 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. Goin.jp needs all CSS files to be minified and compressed as it can save up to 83.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (37%)

Requests Now

78

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

goin.jp

goin.jp

333 ms

goin.jp

goin.jp

1161 ms

application-83223f7a3566dc53cc8af20b0a2239dfd0d1dbbc02355506cdeca99b616c73ac.css

application-83223f7a3566dc53cc8af20b0a2239dfd0d1dbbc02355506cdeca99b616c73ac.css

323 ms

bower-core-d11f324a786b1fb30ec53c59be5b1b55f05c18e76cc6e1236b7fe54b1ad401f6.js

bower-core-d11f324a786b1fb30ec53c59be5b1b55f05c18e76cc6e1236b7fe54b1ad401f6.js

905 ms

application-da651035f5c8687803628227c0ca36e8e011ae0d9a5c82c40b5af5dea2524244.js

application-da651035f5c8687803628227c0ca36e8e011ae0d9a5c82c40b5af5dea2524244.js

485 ms

bookmark_button.js

bookmark_button.js

743 ms

pinit.js

pinit.js

18 ms

analytics.js

analytics.js

211 ms

widgets.js

widgets.js

298 ms

big

big

1487 ms

533492097-chidorigafuchi-tokyo-japan-gettyimages.jpg

533492097-chidorigafuchi-tokyo-japan-gettyimages.jpg

379 ms

button-only@2x.png

button-only@2x.png

219 ms

big

big

1306 ms

big

big

1330 ms

big

big

1681 ms

big

big

1690 ms

big

big

1642 ms

big

big

1929 ms

big

big

1741 ms

big

big

2114 ms

big

big

2119 ms

big

big

2370 ms

big

big

2666 ms

big

big

2360 ms

big

big

2430 ms

big

big

2398 ms

big

big

2416 ms

big

big

2882 ms

big

big

2792 ms

thumb

thumb

2725 ms

thumb

thumb

2443 ms

thumb

thumb

2747 ms

thumb

thumb

2713 ms

thumb

thumb

2934 ms

thumb

thumb

2979 ms

thumb

thumb

3004 ms

thumb

thumb

3187 ms

thumb

thumb

3059 ms

thumb

thumb

2910 ms

thumb

thumb

3195 ms

thumb

thumb

3214 ms

thumb

thumb

3930 ms

thumb

thumb

4126 ms

thumb

thumb

4102 ms

gtm.js

gtm.js

249 ms

sdk.js

sdk.js

429 ms

pc-logo-f805ee09b0879960fe54455a1edea2908951ed8c23ad088f057493b024b11fe4.svg

pc-logo-f805ee09b0879960fe54455a1edea2908951ed8c23ad088f057493b024b11fe4.svg

192 ms

pc-sprite-47bb15656226806c8d01dce3326e75c82ce850fc726766826f19ce7957babee1.png

pc-sprite-47bb15656226806c8d01dce3326e75c82ce850fc726766826f19ce7957babee1.png

489 ms

curve-71de9f4860908d61afe1876b8508db76e96b2d41e3c507044185cf1997b07ff6.png

curve-71de9f4860908d61afe1876b8508db76e96b2d41e3c507044185cf1997b07ff6.png

303 ms

plusone.js

plusone.js

109 ms

863 ms

pinit_main.js

pinit_main.js

146 ms

linkid.js

linkid.js

17 ms

collect

collect

13 ms

collect

collect

87 ms

fbds.js

fbds.js

166 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

57 ms

fastbutton

fastbutton

119 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

58 ms

postmessageRelay

postmessageRelay

79 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

16 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

75 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

80 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

64 ms

rpc:shindig_random.js

rpc:shindig_random.js

58 ms

111 ms

107 ms

xd_arbiter.php

xd_arbiter.php

272 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

jot

jot

100 ms

reset.css

reset.css

162 ms

entry-button.css

entry-button.css

323 ms

bbtn-l_v3.png

bbtn-l_v3.png

162 ms

nr-885.min.js

nr-885.min.js

115 ms

34 ms

like.php

like.php

87 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

315 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

345 ms

11e6ee8438

11e6ee8438

117 ms

Accessibility Review

goin.jp accessibility score

72

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

goin.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

goin.jp SEO score

92

Search Engine Optimization Advices

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 Goin.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 Goin.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

goin.jp

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