30.9 sec in total
3.1 sec
26.9 sec
851 ms
Click here to check amazing Grender content. Otherwise, check out these important facts you probably never knew about grender.com
,北雀麻将机商城在北京拥有500平米的麻将机精品店,销售雀雅麻将机,宣和麻将机,雀骄麻将机,中友麻将机,北雀麻将机,雀秀麻将机.
Visit grender.comWe analyzed Grender.com page load time and found that the first response time was 3.1 sec and then it took 27.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
grender.com performance score
3139 ms
3369 ms
2637 ms
1152 ms
3982 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 85% of them (45 requests) were addressed to the original Grender.com, 4% (2 requests) were made to Hm.baidu.com and 4% (2 requests) were made to Item.jd.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Grender.com.
Page size can be reduced by 409.8 kB (48%)
855.6 kB
445.8 kB
In fact, the total size of Grender.com main page is 855.6 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. 30% of websites need less resources to load. Javascripts take 354.2 kB which makes up the majority of the site volume.
Potential reduce by 63.3 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 63.3 kB or 86% of the original size.
Potential reduce by 77 B
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. Grender images are well optimized though.
Potential reduce by 157.8 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 157.8 kB or 45% of the original size.
Potential reduce by 188.6 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. Grender.com needs all CSS files to be minified and compressed as it can save up to 188.6 kB or 84% of the original size.
Number of requests can be reduced by 9 (24%)
38
29
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grender. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
grender.com
3139 ms
style.css
3369 ms
jquery-1.2.6.pack.js
2637 ms
base-2011.js
1152 ms
common.js
3982 ms
8d6a84140b2342e22a2a2f5c41b6bc22
242 ms
transport.js
1173 ms
utils.js
929 ms
lib-v1.js
1999 ms
home.js
464 ms
style1024.css
491 ms
hm.js
1273 ms
grenderlogo.png
1866 ms
dianhua.gif
270 ms
433_thumb_G_1625091623627.jpg
4980 ms
540_thumb_G_1579019080595.jpg
5421 ms
538_thumb_G_1579019539879.jpg
2035 ms
529_thumb_G_1574707668475.jpg
2327 ms
451_thumb_G_1560278898224.jpg
5713 ms
564_thumb_G_1610488175893.jpg
9157 ms
563_thumb_G_1610488058484.jpg
7756 ms
562_thumb_G_1610487973371.jpg
5183 ms
561_thumb_G_1610487890989.jpg
11020 ms
560_thumb_G_1610487816084.jpg
9938 ms
559_thumb_G_1610487749699.jpg
10470 ms
532_thumb_G_1574708948092.jpg
15316 ms
531_thumb_G_1574708846596.jpg
16717 ms
526_thumb_G_1572552508546.jpg
19231 ms
525_thumb_G_1572552448902.jpg
13551 ms
431_thumb_G_1540161927429.jpg
16213 ms
67_thumb_G_1479229133676.jpg
19534 ms
76_thumb_G_1479314638320.jpg
20192 ms
295_thumb_G_1548608083103.jpg
19710 ms
164_thumb_G_1479179304477.jpg
20192 ms
xml_rss2.gif
19408 ms
1472213219.html
854 ms
20111221C.png
19456 ms
20120112B.png
20176 ms
141_40_ImuQYM.gif
19650 ms
loading.gif
19710 ms
20120208A.png
20143 ms
cat_tit_bg.gif
19925 ms
cat_tit_l.gif
20140 ms
trykantonglan.jpg
20139 ms
xuanhetonglan.jpg
20133 ms
queyatonglan.jpg
20132 ms
beitretonglan.jpg
20126 ms
quexiutonglan.jpg
20125 ms
1472213219.html
595 ms
hm.gif
335 ms
b.js
1773 ms
www.jd.com
601 ms
affim.js
1713 ms
grender.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grender.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Grender.com 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.
grender.com
Open Graph description is not detected on the main page of Grender. 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: