8.4 sec in total
893 ms
6.9 sec
563 ms
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.jpWe analyzed Gogo.jp page load time and found that the first response time was 893 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
gogo.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.1 s
5/100
25%
Value5.8 s
49/100
10%
Value90 ms
98/100
30%
Value0.039
100/100
15%
Value5.9 s
66/100
10%
893 ms
286 ms
443 ms
586 ms
296 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 94% of them (165 requests) were addressed to the original Gogo.jp, 2% (3 requests) were made to Google-analytics.com and 1% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gogo.jp.
Page size can be reduced by 765.0 kB (33%)
2.3 MB
1.5 MB
In fact, the total size of Gogo.jp main page is 2.3 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 76.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. This page needs HTML code to be minified as it can gain 11.4 kB, which is 12% 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 76.5 kB or 83% of the original size.
Potential reduce by 308.3 kB
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. Obviously, Go needs image optimization as it can save up to 308.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 253.3 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 72% of the original size.
Potential reduce by 126.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. 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.
Number of requests can be reduced by 36 (21%)
175
139
The browser has sent 175 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 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
gogo.jp
893 ms
base.css
286 ms
common.css
443 ms
style.css
586 ms
tooltipster.css
296 ms
lightbox.css
297 ms
contact.css
294 ms
tooltipster.css
430 ms
tooltipster-light.css
440 ms
tooltipster-noir.css
442 ms
tooltipster-punk.css
443 ms
tooltipster-shadow.css
576 ms
jquery-ui.css
722 ms
jquery.min.js
42 ms
jquery.tooltipster.min.js
720 ms
lightbox-2.6.min.js
578 ms
jquery.tooltipster.js
871 ms
jquery-ui-1.10.3.custom.min.js
1442 ms
jquery.cookie.js
718 ms
jquery.blockUI.js
870 ms
passwordinput.js
863 ms
mapRollover.js
1012 ms
jquery.layerBoard.js
869 ms
mvp_ok.css
1009 ms
mvp.js
1014 ms
close.png
231 ms
loading.gif
232 ms
prev.png
231 ms
next.png
232 ms
analytics.js
210 ms
widgets.js
221 ms
sdk.js
283 ms
9513e9er490os7umq6u1ipe53q2tqphcwcpf.png
378 ms
2072 ms
img-area-search.png
439 ms
img-area-search-hokkaido.png
153 ms
img-area-search-aomori.png
151 ms
img-area-search-iwate.png
156 ms
img-area-search-miyagi.png
154 ms
img-area-search-akita.png
296 ms
img-area-search-yamagata.png
299 ms
img-area-search-fukushima.png
299 ms
img-area-search-niigata.png
299 ms
img-area-search-toyama.png
445 ms
img-area-search-ishikawa.png
445 ms
img-area-search-fukui.png
444 ms
img-area-search-ibaraki.png
446 ms
img-area-search-tochigi.png
584 ms
img-area-search-gunma.png
589 ms
img-area-search-saitama.png
590 ms
img-area-search-chiba.png
593 ms
img-area-search-tokyo.png
591 ms
img-area-search-kanagawa.png
730 ms
img-area-search-yamanashi.png
738 ms
img-area-search-nagano.png
738 ms
img-area-search-gifu.png
737 ms
img-area-search-shizuoka.png
740 ms
img-area-search-aichi.png
876 ms
img-area-search-mie.png
883 ms
img-area-search-shiga.png
883 ms
img-area-search-kyoto.png
884 ms
img-area-search-osaka.png
894 ms
img-area-search-hyogo.png
1021 ms
img-area-search-nara.png
1028 ms
img-area-search-wakayama.png
1030 ms
img-area-search-tottori.png
1029 ms
img-area-search-shimane.png
1029 ms
img-area-search-okayama.png
1164 ms
linkid.js
14 ms
img-area-search-hiroshima.png
1149 ms
collect
16 ms
collect
100 ms
61 ms
xd_arbiter.php
221 ms
xd_arbiter.php
425 ms
img-area-search-yamaguchi.png
1034 ms
img-area-search-tokushima.png
1035 ms
img-area-search-kagawa.png
1035 ms
img-area-search-ehime.png
1174 ms
img-area-search-kochi.png
1035 ms
img-area-search-fukuoka.png
1033 ms
img-area-search-saga.png
1038 ms
img-area-search-nagasaki.png
1037 ms
img-area-search-kumamoto.png
1035 ms
img-area-search-oita.png
1031 ms
img-area-search-miyazaki.png
1033 ms
img-area-search-kagoshima.png
1037 ms
img-area-search-okinawa.png
1036 ms
bg-wrapper.gif
1032 ms
icon_first.png
1031 ms
logo.png
1178 ms
arrow-orange.png
1036 ms
img_catch.png
1037 ms
btn-search-L.png
1034 ms
bg-mainvisual.gif
1027 ms
star-s.png
1035 ms
icon-review.gif
1035 ms
img-men.png
1170 ms
img-women.png
1036 ms
img-human-1.gif
1033 ms
img-human-2.gif
1034 ms
img-human-3.gif
1036 ms
img-human-4.gif
1164 ms
img-human-5.gif
1036 ms
img-human-6.gif
1035 ms
img-human-7.gif
1034 ms
img-human-8.gif
1035 ms
img-human-9.gif
1150 ms
img-dog.gif
1037 ms
img-cat.gif
1029 ms
img-bird-left.gif
1038 ms
img-bird-right.gif
1031 ms
top.png
1471 ms
h2-search-category.png
1010 ms
bg-category-search.jpg
1318 ms
01.png
1175 ms
02.png
1174 ms
03.png
1178 ms
04.png
1158 ms
05.png
1178 ms
06.png
1324 ms
07.png
1324 ms
0101.jpg
1294 ms
0102.jpg
1321 ms
0103.jpg
1182 ms
0104.jpg
1178 ms
0111.jpg
1441 ms
0113.jpg
1183 ms
0201.jpg
1185 ms
0202.jpg
1330 ms
0203.jpg
1179 ms
0204.jpg
1310 ms
0208.jpg
1184 ms
0209.jpg
1187 ms
0301.jpg
1188 ms
0302.jpg
1443 ms
0303.jpg
1310 ms
0304.jpg
1203 ms
0305.jpg
1184 ms
0306.jpg
1186 ms
0401.jpg
1188 ms
0402.jpg
1313 ms
0403.jpg
1323 ms
0404.jpg
1352 ms
0405.jpg
1192 ms
0501.jpg
1194 ms
0502.jpg
1441 ms
0503.jpg
1314 ms
0601.jpg
1210 ms
0602.jpg
1045 ms
0603.jpg
1047 ms
0604.jpg
1313 ms
0605.jpg
1060 ms
0701.jpg
1047 ms
0704.jpg
1046 ms
0706.jpg
1044 ms
0707.jpg
1032 ms
0708.jpg
1180 ms
0709.jpg
1038 ms
tab-search-map-off.png
1040 ms
tab-search-line-off.png
1042 ms
img-area-search-bg.png
1165 ms
h2-search-map.png
1022 ms
h2-search-line.png
1036 ms
img_area_search.png
1183 ms
ttl_pickup_review.gif
923 ms
pic_noimage.jpg
1034 ms
bg-review-pic.jpg
1030 ms
star-85.png
1037 ms
bg-new-register.jpg
1187 ms
btn-new-customer.png
1144 ms
btn-register-member.png
1034 ms
bnr-forowner-off.jpg
1178 ms
ttl-side.jpg
1041 ms
loading.gif
1039 ms
tab-search-map-active.png
1141 ms
gogo.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gogo.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
gogo.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: