GREE.JP GREE(グリー)


gree.jp website information.

gree.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.

Following name servers are specified for gree.jp domain:

  • ns7-64.akam.net
  • ns4-64.akam.net
  • ns5-64.akam.net
  • ns1-56.akam.net

and probably website gree.jp is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.

According to Alexa traffic rank the highest website gree.jp position was 14845 (in the world). The lowest Alexa rank position was 992544. Now website gree.jp ranked in Alexa database as number 41226 (in the world).

Website gree.jp Desktop speed measurement score (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

gree.jp Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of gree.jp (43/100) is better than the results of 22.8% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-27-2024 41,226173
Nov-26-2024 41,399102
Nov-25-2024 41,501-772
Nov-24-2024 40,729418
Nov-23-2024 41,147545
Nov-22-2024 41,692-539
Nov-21-2024 41,153310

Advertisement

gree.jp Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



gree.jp whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


gree.jp server information

Servers Location

IP Address
157.112.206.9
Country
Japan
Region
Tokyo
City
Tokyo

gree.jp desktop page speed rank

Last tested: 2018-02-01


Desktop Speed Medium
84/100

gree.jp Desktop Speed Test Quick Summary


priority - 8 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://aimg-m.gree.net/img/application/thumbnail/59/56259/p72.jpg (60 minutes)
http://aimg-static.gree.net/ggp/css/pc/mint/portal.css (60 minutes)
http://aimg-static.gree.net/ggp/img/pc/common/cate.png?2 (60 minutes)
http://aimg-static.gree.net/ggp/img/pc/common/s18_arw.png?2 (60 minutes)
http://aimg-static.gree.net/ggp/img/pc/common/s24_hl.png?4 (60 minutes)
http://aimg-static.gree.net/ggp/js/jquery-1.11.1.min.js (60 minutes)
http://aimg-static.gree.net/ggp/js/jquery-1.11.1.min.js?20140903000 (60 minutes)
http://aimg-static.gree.net/ggp/js/quill.js (60 minutes)
http://aimg-static.gree.net/ggp/js/quill.min.js?20180201001 (60 minutes)
http://aimg-static.gree.net/ggp/js/slick/slick.css (60 minutes)
http://aimg-static.gree.net/ggp/js/slick/slick.min.js (60 minutes)
http://aimg-static.gree.net/js/LAB-2.0.3.min.js?20140903000 (60 minutes)
http://aimg-static.gree.net/js/lazy-load.pc.min.js?20140903002 (60 minutes)
http://aimg-static.gree.net/js/navigation_pc_en_1.0.11.js (60 minutes)
https://aimg-m-ssl.gree.net/img/application/thumbnail/57/56257/p72.jpg (60 minutes)
https://aimg-m-ssl.gree.net/img/application/thumbnail/58/56258/p72.jpg (60 minutes)
https://secure.gree.jp/img/gree/2009/footer_qr02.gif (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

http://aimg-static.gree.net/ggp/css/pc/mint/portal.css

priority - 0 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.6KiB (12% reduction).

Compressing http://aimg-static.gree.net/ggp/img/pc/common/cate.png?2 could save 444B (17% reduction).
Compressing https://aimg-m-ssl.gree.net/img/application/thumbnail/57/56257/p72.jpg could save 400B (12% reduction).
Compressing https://aimg-m-ssl.gree.net/img/application/thumbnail/58/56258/p72.jpg could save 388B (11% reduction).
Compressing http://aimg-m.gree.net/img/application/thumbnail/59/56259/p72.jpg could save 384B (11% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 983B (30% reduction).

Minifying http://aimg-static.gree.net/ggp/js/quill.js could save 983B (30% reduction) after compression.

gree.jp Desktop Resources

Total Resources20
Number of Hosts6
Static Resources18
JavaScript Resources9
CSS Resources2

gree.jp Desktop Resource Breakdown

gree.jp mobile page speed rank

Last tested: 2018-02-02


Mobile Speed Bad
43/100

gree.jp Mobile Speed Test Quick Summary


priority - 102 Avoid landing page redirects

Your page has 5 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://gree.jp/
http://games.gree.net/?mode=&act=top
https://games.gree.net/welcome
http://product.gree.net/us/en/
https://corp.gree.net/jp/en/index.html
http://corp.gree.net/jp/en/sp/index.html

priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://corp.gree.net/share/v2/sp/lib/jquery.js
http://corp.gree.net/share/v2/sp/lib/jquery.easing.js
http://corp.gree.net/share/v2/sp/lib/jquery.virotation.js
http://corp.gree.net/share/v2/sp/lib/customAccordion.js
http://corp.gree.net/share/v2/sp/js/common.js
http://corp.gree.net/share/v2/sp/js/changeAgentSp.js

Optimize CSS Delivery of the following:

http://corp.gree.net/share/v2/sp/css/reset.css
http://corp.gree.net/share/v2/sp/css/global.css
http://corp.gree.net/jp/en/sp/share/css/style.css
http://corp.gree.net/jp/en/sp/css/style.css

priority - 12 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://corp.gree.net/share/v2/sp/js/changeAgentSp.js (expiration not specified)
http://corp.gree.net/share/v2/sp/js/common.js (expiration not specified)
http://corp.gree.net/share/v2/sp/lib/customAccordion.js (expiration not specified)
http://corp.gree.net/share/v2/sp/lib/jquery.easing.js (expiration not specified)
http://corp.gree.net/share/v2/sp/lib/jquery.js (expiration not specified)
http://corp.gree.net/share/v2/sp/lib/jquery.virotation.js (expiration not specified)
http://corp.gree.net/jp/en/sp/css/style.css (60 seconds)
http://corp.gree.net/jp/en/sp/share/css/style.css (60 seconds)
http://corp.gree.net/share/v2/sp/css/global.css (60 seconds)
http://corp.gree.net/share/v2/sp/css/reset.css (60 seconds)
https://syndication.twitter.com/settings (10 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-KNWBFZ (15 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 8 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 79.8KiB (48% reduction).

Compressing http://corp.gree.net/jp/en/share/img/pic_index_vi_01.jpg could save 39.1KiB (41% reduction).
Compressing http://corp.gree.net/jp/en/sp/img/bg_pic_index_04.jpg could save 14.6KiB (65% reduction).
Compressing http://corp.gree.net/jp/en/sp/img/bg_pic_index_01.jpg could save 11.6KiB (61% reduction).
Compressing http://corp.gree.net/jp/en/sp/img/bg_pic_index_03.jpg could save 9KiB (60% reduction).
Compressing http://corp.gree.net/jp/en/sp/img/bg_pic_index_02.jpg could save 5.5KiB (39% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.2KiB (47% reduction).

Minifying http://corp.gree.net/share/v2/sp/lib/jquery.easing.js could save 1.1KiB (58% reduction) after compression.
Minifying http://corp.gree.net/share/v2/sp/lib/customAccordion.js could save 1.1KiB (55% reduction) after compression.
Minifying http://corp.gree.net/share/v2/sp/lib/jquery.virotation.js could save 750B (51% reduction) after compression.
Minifying http://corp.gree.net/share/v2/sp/js/common.js could save 250B (17% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.1KiB (14% reduction).

Minifying http://corp.gree.net/share/v2/sp/css/global.css could save 1,020B (14% reduction) after compression.
Minifying http://corp.gree.net/share/v2/sp/css/reset.css could save 144B (19% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 348B (12% reduction).

Minifying http://corp.gree.net/jp/en/sp/index.html could save 348B (12% reduction) after compression.

gree.jp Mobile Resources

Total Resources50
Number of Hosts13
Static Resources35
JavaScript Resources19
CSS Resources4

gree.jp Mobile Resource Breakdown

gree.jp mobile page usability

Last tested: 2018-02-02


Mobile Usability Good
100/100

gree.jp similar domains

Similar domains:
www.gree.com
www.gree.net
www.gree.org
www.gree.info
www.gree.biz
www.gree.us
www.gree.mobi
www.ree.jp
www.gree.jp
www.free.jp
www.gfree.jp
www.fgree.jp
www.vree.jp
www.gvree.jp
www.vgree.jp
www.tree.jp
www.gtree.jp
www.tgree.jp
www.bree.jp
www.gbree.jp
www.bgree.jp
www.yree.jp
www.gyree.jp
www.ygree.jp
www.hree.jp
www.ghree.jp
www.hgree.jp
www.gee.jp
www.geee.jp
www.greee.jp
www.geree.jp
www.gdee.jp
www.grdee.jp
www.gdree.jp
www.gfee.jp
www.grfee.jp
www.gtee.jp
www.grtee.jp
www.gre.jp
www.grwe.jp
www.grewe.jp
www.grwee.jp
www.grse.jp
www.grese.jp
www.grsee.jp
www.grde.jp
www.grede.jp
www.grre.jp
www.grere.jp
www.grree.jp
www.grew.jp
www.greew.jp
www.gres.jp
www.grees.jp
www.gred.jp
www.greed.jp
www.grer.jp
www.greer.jp

gree.jp Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


gree.jp TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.