Tools & Wizards About Us
gogo.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

gogo.jp

GoGo! TOWN - レビュー・口コミの地域情報サイト

Page Load Speed

6 sec in total

First Response

989 ms

Resources Loaded

4.8 sec

Page Rendered

235 ms

gogo.jp screenshot

About Website

Click here to check amazing Go content for Japan. Otherwise, check out these important facts you probably never knew about gogo.jp

GoGo! TOWNはショップ検索ができる地域情報サイト。レビューと口コミで地域のお気に入りショップを見つけよう！

Visit gogo.jp

Key Findings

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

Performance Metrics

gogo.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

gogo.jp

989 ms

base.css

290 ms

common.css

437 ms

style.css

456 ms

tooltipster.css

311 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 89% of them (118 requests) were addressed to the original Gogo.jp, 3% (4 requests) were made to Platform.twitter.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Gogo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 538.2 kB (25%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gogo.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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 85.4 kB

  • Original 104.4 kB
  • After minification 93.1 kB
  • After compression 19.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 11.4 kB, which is 11% 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 85.4 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 72.6 kB

  • Original 1.5 MB
  • After minification 1.4 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. Go images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 253.3 kB

  • Original 386.3 kB
  • After minification 355.9 kB
  • After compression 133.0 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 253.3 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 126.9 kB

  • Original 148.2 kB
  • After minification 116.1 kB
  • After compression 21.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. Gogo.jp needs all CSS files to be minified and compressed as it can save up to 126.9 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

132

After Optimization

94

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gogo.jp

gogo.jp

989 ms

base.css

base.css

290 ms

common.css

common.css

437 ms

style.css

style.css

456 ms

tooltipster.css

tooltipster.css

311 ms

lightbox.css

lightbox.css

314 ms

contact.css

contact.css

349 ms

tooltipster.css

tooltipster.css

433 ms

tooltipster-light.css

tooltipster-light.css

465 ms

tooltipster-noir.css

tooltipster-noir.css

469 ms

tooltipster-punk.css

tooltipster-punk.css

514 ms

tooltipster-shadow.css

tooltipster-shadow.css

576 ms

jquery-ui.css

jquery-ui.css

582 ms

jquery.min.js

jquery.min.js

7 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

607 ms

lightbox-2.6.min.js

lightbox-2.6.min.js

619 ms

jquery.tooltipster.js

jquery.tooltipster.js

778 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

1295 ms

jquery.cookie.js

jquery.cookie.js

720 ms

jquery.blockUI.js

jquery.blockUI.js

727 ms

passwordinput.js

passwordinput.js

760 ms

mapRollover.js

mapRollover.js

774 ms

jquery.layerBoard.js

jquery.layerBoard.js

863 ms

mvp_ok.css

mvp_ok.css

872 ms

mvp.js

mvp.js

912 ms

close.png

close.png

164 ms

loading.gif

loading.gif

163 ms

prev.png

prev.png

162 ms

next.png

next.png

163 ms

analytics.js

analytics.js

136 ms

widgets.js

widgets.js

131 ms

186 ms

sdk.js

sdk.js

34 ms

bg-wrapper.gif

bg-wrapper.gif

172 ms

icon_first.png

icon_first.png

183 ms

logo.png

logo.png

187 ms

arrow-orange.png

arrow-orange.png

181 ms

img_catch.png

img_catch.png

186 ms

btn-search-L.png

btn-search-L.png

318 ms

bg-mainvisual.gif

bg-mainvisual.gif

311 ms

star-s.png

star-s.png

316 ms

icon-review.gif

icon-review.gif

335 ms

img-men.png

img-men.png

338 ms

img-women.png

img-women.png

339 ms

img-human-1.gif

img-human-1.gif

456 ms

img-human-2.gif

img-human-2.gif

460 ms

img-human-3.gif

img-human-3.gif

474 ms

img-human-4.gif

img-human-4.gif

493 ms

img-human-5.gif

img-human-5.gif

496 ms

img-human-6.gif

img-human-6.gif

495 ms

img-human-7.gif

img-human-7.gif

601 ms

img-human-8.gif

img-human-8.gif

604 ms

img-human-9.gif

img-human-9.gif

629 ms

img-dog.gif

img-dog.gif

646 ms

img-cat.gif

img-cat.gif

651 ms

img-bird-left.gif

img-bird-left.gif

650 ms

img-bird-right.gif

img-bird-right.gif

747 ms

top.png

top.png

1036 ms

h2-search-category.png

h2-search-category.png

784 ms

bg-category-search.jpg

bg-category-search.jpg

798 ms

01.png

01.png

804 ms

02.png

02.png

806 ms

03.png

03.png

895 ms

04.png

04.png

941 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

58 ms

linkid.js

linkid.js

11 ms

05.png

05.png

927 ms

06.png

06.png

934 ms

07.png

07.png

937 ms

0101.jpg

0101.jpg

1015 ms

sdk.js

sdk.js

9 ms

collect

collect

50 ms

collect

collect

56 ms

56 ms

settings

settings

100 ms

js

js

65 ms

0102.jpg

0102.jpg

928 ms

0103.jpg

0103.jpg

935 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

0104.jpg

0104.jpg

937 ms

0111.jpg

0111.jpg

939 ms

0113.jpg

0113.jpg

998 ms

embeds

embeds

28 ms

0201.jpg

0201.jpg

1000 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

15 ms

0202.jpg

0202.jpg

946 ms

0203.jpg

0203.jpg

946 ms

0204.jpg

0204.jpg

957 ms

0208.jpg

0208.jpg

944 ms

0209.jpg

0209.jpg

989 ms

0301.jpg

0301.jpg

996 ms

0302.jpg

0302.jpg

957 ms

0303.jpg

0303.jpg

956 ms

0304.jpg

0304.jpg

956 ms

0305.jpg

0305.jpg

941 ms

0306.jpg

0306.jpg

977 ms

0401.jpg

0401.jpg

986 ms

0402.jpg

0402.jpg

968 ms

0403.jpg

0403.jpg

965 ms

0404.jpg

0404.jpg

956 ms

0405.jpg

0405.jpg

943 ms

0501.jpg

0501.jpg

966 ms

0502.jpg

0502.jpg

976 ms

0503.jpg

0503.jpg

978 ms

0601.jpg

0601.jpg

938 ms

0602.jpg

0602.jpg

942 ms

0603.jpg

0603.jpg

940 ms

0604.jpg

0604.jpg

954 ms

0605.jpg

0605.jpg

877 ms

0701.jpg

0701.jpg

935 ms

0704.jpg

0704.jpg

929 ms

0706.jpg

0706.jpg

935 ms

0707.jpg

0707.jpg

938 ms

0708.jpg

0708.jpg

869 ms

0709.jpg

0709.jpg

879 ms

tab-search-map-off.png

tab-search-map-off.png

931 ms

tab-search-line-off.png

tab-search-line-off.png

932 ms

img-area-search-bg.png

img-area-search-bg.png

1089 ms

h2-search-map.png

h2-search-map.png

939 ms

img-area-search.png

img-area-search.png

870 ms

h2-search-line.png

h2-search-line.png

880 ms

img_area_search.png

img_area_search.png

930 ms

ttl_pickup_review.gif

ttl_pickup_review.gif

934 ms

pic_noimage.jpg

pic_noimage.jpg

923 ms

star-85.png

star-85.png

939 ms

bg-review-pic.jpg

bg-review-pic.jpg

887 ms

bg-new-register.jpg

bg-new-register.jpg

1005 ms

btn-new-customer.png

btn-new-customer.png

939 ms

btn-register-member.png

btn-register-member.png

926 ms

bnr-forowner-off.jpg

bnr-forowner-off.jpg

1088 ms

ttl-side.jpg

ttl-side.jpg

927 ms

loading.gif

loading.gif

901 ms

tab-search-map-active.png

tab-search-map-active.png

1012 ms

Accessibility Review

gogo.jp accessibility score

77

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

gogo.jp best practices score

75

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

SEO Factors

gogo.jp SEO score

97

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

High

Tap targets are not sized appropriately

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

gogo.jp

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