8.5 sec in total
468 ms
6 sec
2.1 sec
Welcome to grandstar.blog.com homepage info - get ready to check Grand Star Blog best content for China right away, or after learning these important things about grandstar.blog.com
【御剑乘风来,除魔天地间,有酒乐逍遥,无酒我亦癫,一饮尽江河,再饮吞日月,千杯醉不倒,惟我酒剑仙】
Visit grandstar.blog.comWe analyzed Grandstar.blog.com page load time and found that the first response time was 468 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 85% of websites can load faster.
grandstar.blog.com performance score
468 ms
217 ms
215 ms
218 ms
224 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Grandstar.blog.com, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Grandstar.blog.com.
Page size can be reduced by 773.5 kB (10%)
7.6 MB
6.8 MB
In fact, the total size of Grandstar.blog.com main page is 7.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 36.2 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 36.2 kB or 74% of the original size.
Potential reduce by 610.5 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. Grand Star Blog images are well optimized though.
Potential reduce by 104.0 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 104.0 kB or 55% of the original size.
Potential reduce by 22.8 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. Grandstar.blog.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 78% of the original size.
Number of requests can be reduced by 26 (41%)
63
37
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grand Star Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
grandstar.blog.com
468 ms
style.css
217 ms
admin-bar.css
215 ms
blogcom-admin-bar.css
218 ms
nggallery.css
224 ms
shutter-reloaded.css
228 ms
cssreset-context.css
764 ms
base.css
229 ms
twitter.css
319 ms
google.css
320 ms
browserid.css
323 ms
facebook.css
337 ms
l10n.js
341 ms
jquery.js
458 ms
shutter-reloaded.js
424 ms
swfobject.js
426 ms
ngg.js
429 ms
base.js
450 ms
twitter.js
453 ms
google.js
530 ms
browserid.js
531 ms
include.js
34 ms
facebook.js
535 ms
audio-player.js
563 ms
admin-bar.js
562 ms
jquery.form.js
568 ms
quant.js
28 ms
include.js
53 ms
ados.js
166 ms
ga.js
166 ms
bk_body.jpg
573 ms
ico_bluecheck.png
154 ms
tOBmYqk.png
210 ms
bk_content.jpg
147 ms
bk_line_ornament.jpg
150 ms
bk_line.jpg
144 ms
bk_date.png
145 ms
bk_comments_no.png
150 ms
bell_meta.png
244 ms
515663220_preview_CS1.png
4801 ms
031624alq00zh9xbateftf.jpg
855 ms
031638wmmfgwqhkg6hdbab.jpg
916 ms
031642tsliziczhi4lcizk.jpg
1260 ms
031636rkkmc2qqrvqzh9b6.jpg
851 ms
031653mj6acy9txnjyjysf.jpg
1240 ms
0316568u68ab2h8ubfmml2.jpg
1313 ms
031646pv4zeej41nr21ndm.jpg
1174 ms
024056sjsn968bliotttng.jpg
1257 ms
024108s9i9k0gx1qpv9qvt.jpg
1387 ms
024103psgtocpn3nk4nng3.jpg
1469 ms
024100bbbm4ivzxyvd4f43.jpg
1485 ms
1753311dq2ob5n5z2dd1je.png
1372 ms
175325okopp1qy8py818yv.png
1417 ms
c2233f9bcbf7e718.png
1486 ms
105824up83h3o926zhhtch.png
1493 ms
121150gklqclnzlhhlhxqw.png
1523 ms
122918iccy9jvxrxtzeyeg.png
1695 ms
123645g9xzffkufs2grj1r.png
1599 ms
213247tq6s6xwmcjc3h6js.png.thumb_.png
1713 ms
ados
44 ms
__utm.gif
21 ms
bk_footer.jpg
1917 ms
__utm.gif
32 ms
pixel;r=1770962747;a=p-b3DDIGtNmjMZA;fpan=1;fpa=P0-1205079906-1458444651191;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458444651190;tzo=-180;ref=;url=http%3A%2F%2Fgrandstar.blog.com%2F;ogl=site_name.(GrandStar)%E7%8E%84%E8%BE%B0%2Ctype.blog%2Ctitle.(GrandStar)%E7%8E%84%E8%BE%B0%2Curl.http%3A%2F%2Fgrandstar%252Eblog%252Ecom%2Cdescription.%E3%80%90%E5%BE%A1%E5%89%91%E4%B9%98%E9%A3%8E%E6%9D%A5%252C%E9%99%A4%E9%AD%94%E5%A4%A9%E5%9C%B0%E9%97%B4%252C%E6%9C%89%E9%85%92%E4%B9%90%E9%80%8D%E9%81%A5%252C%E6%97%A0%E9%85%92%E6%88%91%E4%BA%A6%E7%99%AB%252C%E4%B8%80%E9%A5%AE%E5%B0%BD%E6%B1%9F%E6%B2%B3%252C%E5%86%8D%E9%A5%AE%E5%90%9E%E6%97%A5%E6%9C%88%252C%E5%8D%83%E6%9D%AF%E9%86%89%E4%B8%8D%E5%80%92%252C%E6%83%9F%E6%88%91%E9%85%92%E5%89%91%E4%BB%99%E3%80%91%2Cimage.http%3A%2F%2Fblog%252Ecom%2Favatar%2Fblog-25716137-80%252Epng%3Frand%3De2f6e7b97a5d0264e66936f79498d5f
26 ms
admin-bar-bg.png
1394 ms
bc-avatar.png
1478 ms
grandstar.blog.com SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandstar.blog.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Grandstar.blog.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.
grandstar.blog.com
Open Graph data is detected on the main page of Grand Star Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: