Analyze

goo.jp: goo

NTTレゾナントが運営する安心・安全のポータルサイト。使えば使うほど、あなたの興味・関心、趣味・嗜好を学習し、限られた時間で効率よく「あなた専用」のポータルサイトとして必要な情報を収集することができます。

Page load speed analysis

  • 60/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    525 ms

  • Resources loaded

    7.7 sec

  • Page rendered

    378 ms

  • Total page load time

    8.6 sec

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

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

Page optimization

  • HTML 153.1 kB
    Images 227.5 kB
    Javascripts 390.9 kB
    CSS 124.9 kB

    In fact, the total size of Goo.jp main page is 896.4 kB. 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. Javascripts take 390.9 kB which makes up the majority of the site volume.

    • Original 153.1 kB
    • After minification 149.0 kB
    • After compression 35.3 kB

    HTML optimization

    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 117.8 kB or 77% of the original size.

    • Original 227.5 kB
    • After optimization 223.4 kB

    Image optimization

    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. Goo images are well optimized though.

    • Original 390.9 kB
    • After minification 384.9 kB
    • After compression 130.5 kB

    JavaScript optimization

    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 260.4 kB or 67% of the original size.

    • Original 124.9 kB
    • After minification 116.8 kB
    • After compression 36.9 kB

    CSS optimization

    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. Goo.jp needs all CSS files to be minified and compressed as it can save up to 87.9 kB or 70% of the original size.

Network requests diagram

  • goo.jp
  • www.goo.ne.jp
  • 1.3.css
  • x.css
  • march-style.css
  • news.css
  • smarttag-gootop-gootop_goo.js
  • 1.8.js
  • 1.1.js
  • x.js
  • script.min.js
  • logo.min.js
  • clicklog.min.js
  • sgt_serp_ver_r.min.js
  • VLTraceDMD.js
  • rta.js
  • gtm.js
  • pageid=91386710
  • mail.png
  • header_bg.jpg
  • header.jpg
  • gh_logo.png
  • icon-search.png
  • sp_20160301025013_1_PN2016022901001518.-.-.CI0002.jpg
  • sp_20160301025013_1_s_ASJ2Y44NPJ2YOIPE010.jpg
  • sp_20160301025013_1_s_footballchannel-134906.jpg
  • sp_20160301025013_1_s_reuters-20160229040.jpg
  • img_dummy.png
  • banner_renew324_90.jpg
  • icon-theme.png
  • icon_aries.gif
  • 20160301025007_1_r003_today.jpg
  • mesh_p0018_1.jpg
  • 101.png
  • icon-baseball.png
  • icon-soccer.png
  • icon-tennis.png
  • icon-ragby.png
  • privacymark.gif
  • blog.png
  • fortune.png
  • point.png
  • analytics.js
  • linkid.js
  • collect
  • collect
  • collect
  • collect
  • pageid=91386710
  • fontawesome-webfont.woff
  • pr_icon.gif
  • pageid=91386710
  • pageid=91386710
  • pageid=91386710
  • pageid=91386710
  • pageid=91386710
  • pageid=91386710
  • lift_widget.js
  • pageid=91386710
  • 160229canonjp_c_300250_SX_A-277dc93dbc2286614c8847ddf94efc70d7f72d4f.jpg
  • xtrail
  • pageid=91386710
  • lift.json
  • original.jpg
  • bc
  • ajs.php
  • sync.html
  • jstag
  • lg.php
  • sync.js
  • acj
  • pd
  • show_ads.js
  • ri
  • 2c8d10e2-0ca8-e947-9115-8c7c0f43f048
  • pixel
  • zrt_lookup.html
  • show_ads_impl.js
  • sd
  • pixel
  • push_sync
  • idsync
  • sync
  • set
  • cookiesync
  • sd
  • sd
  • ads
  • osd.js
  • b.js
  • gh_logo_bg.png
  • bg-mynews.jpg
  • 1_zoom1_1021726_m.jpg
  • 274_z2.jpg
  • 1_s102_m.jpg
  • 2_l18.jpg
  • r_20160229_kamaboko_top.jpg
  • r_chie160229-thum.jpg
  • r_20160228yy.jpg
  • r_20160227.jpg
  • 542233798_56c579b3c07d1_ORG.jpg
  • gh_logo_eye.png
  • gh_logo_blink.png
  • gh_logo_smile.png
  • gh_logo_zzz.png
  • sd
  • sd
  • map.gif
  • a_62_780.js
  • bridge
  • ins_syncxl.js
  • syncxl.html
  • syncxl.js
  • is
  • r.gif
  • map.gif
  • is

Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Goo.jp, 32% (37 requests) were made to Xgoo.jp and 9% (10 requests) were made to A1.goo.ne.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cdn.logly.co.jp.

Additional info on goo.jp

Requests

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

37

Javascripts

62

Images

4

CSS

7

AJAX

110

All

Possible request optimization

1

Javascripts

37

Images

1

CSS

7

AJAX

64

Optimized

46

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.goo.ne.jp/ before it reached this domain.

IP address

Goo.jp uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

goo.jp

plala.goo.ne.jp

311.goo.ne.jp

www.goo

green.goo.ne.jp

114.179.184.93

DNS records

Type Host Target/ip TTL Other
A

goo.jp

114.179.184.93 300
NS

goo.jp

ns3.via.or.jp 900
NS

goo.jp

ns2.via.or.jp 900
NS

goo.jp

ns2.goo.ne.jp 900
NS

goo.jp

ns1.goo.ne.jp 900

Language and encoding

Good result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goo.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 Goo.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.

HTTPS certificate

SSL Certificate

Goo.jp has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Japan. It’s good for Goo.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Good result

Social Sharing Optimization

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

goo.jp

Share this report in social media

Analyze another website

Analyze