1.8 sec in total
30 ms
1.5 sec
276 ms
Click here to check amazing GREE content for Japan. Otherwise, check out these important facts you probably never knew about gree.net
Visit gree.netWe analyzed Gree.net page load time and found that the first response time was 30 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
gree.net performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.2 s
45/100
25%
Value5.0 s
62/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value4.4 s
83/100
10%
30 ms
121 ms
30 ms
35 ms
19 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Gree.net, 10% (7 requests) were made to Apis.google.com and 10% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (472 ms) relates to the external source Product.gree.net.s3.amazonaws.com.
Page size can be reduced by 245.1 kB (18%)
1.4 MB
1.1 MB
In fact, the total size of Gree.net main page is 1.4 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.0 MB which makes up the majority of the site volume.
Potential reduce by 20.0 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 20.0 kB or 79% of the original size.
Potential reduce by 15.0 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. GREE images are well optimized though.
Potential reduce by 149.6 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 149.6 kB or 68% of the original size.
Potential reduce by 60.4 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. Gree.net needs all CSS files to be minified and compressed as it can save up to 60.4 kB or 81% of the original size.
Number of requests can be reduced by 43 (63%)
68
25
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GREE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
product.gree.net
30 ms
en
121 ms
common.css
30 ms
pc.css
35 ms
tablet.css
19 ms
test.css
24 ms
careers.css
25 ms
jquery.smartbanner.css
26 ms
jquery-1.7.2.min.js
36 ms
cssua.min.js
32 ms
jquery.easing.1.3.js
32 ms
common.js
32 ms
jquery.bxSlider.js
41 ms
jquery.colorbox.js
30 ms
jCarousel.min.js
28 ms
jquery.cookie.js
39 ms
jquery.smartbanner.js
40 ms
oct.js
25 ms
ga.js
63 ms
fbds.js
96 ms
adsct
170 ms
adsct
61 ms
837219871024x500_pgn_won.jpg
472 ms
widgets.js
38 ms
plusone.js
141 ms
YT_Subscribe_61x23_red.png
55 ms
header-logo-01.png
22 ms
mainSlider-bg-01.png
21 ms
1024x500_knightsB.jpg
61 ms
button_ios_icon.png
20 ms
black_op70_bg.png
22 ms
mainimg-1024x500-01.jpg
57 ms
bnr-294x166-01.jpg
52 ms
button_ios_small_icon.png
22 ms
button_android_small_icon.png
43 ms
bnr-294x166-01.jpg
52 ms
294x166_knights.jpg
52 ms
externalLink-icon-01.gif
50 ms
button_android_icon.png
54 ms
mainSlider-pager-02.gif
55 ms
mainSlider-pager-01.gif
58 ms
control-icon-01.png
58 ms
1922won_widget.jpg
391 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
39 ms
__utm.gif
20 ms
__utm.gif
22 ms
likebox.php
176 ms
178 ms
mobile.css
37 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
14 ms
like.php
150 ms
print.css
21 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
58 ms
fastbutton
120 ms
postmessageRelay
63 ms
jot
125 ms
FbUd6dZS1Af.css
167 ms
_rx8naC75Dy.js
239 ms
x5F9OMjKyLw.js
347 ms
ICDbTSzjQEg.js
276 ms
TTCre3391I0.js
276 ms
api.js
45 ms
core:rpc:shindig.random:shindig.sha1.js
86 ms
2536007149-postmessagerelay.js
65 ms
cb=gapi.loaded_0
40 ms
cb=gapi.loaded_1
34 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
84 ms
I6-MnjEovm5.js
38 ms
vlXaquuXMrr.js
80 ms
24 ms
gree.net 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
gree.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
gree.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gree.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Gree.net 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.
gree.net
Open Graph data is detected on the main page of GREE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: