32 sec in total
4.7 sec
26.7 sec
616 ms
Visit istyles.blog.163.com now to see the best up-to-date Istyles Blog 163 content for China and also check out these interesting facts you probably never knew about istyles.blog.163.com
Visit istyles.blog.163.comWe analyzed Istyles.blog.163.com page load time and found that the first response time was 4.7 sec and then it took 27.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
istyles.blog.163.com performance score
4662 ms
509 ms
4628 ms
20081 ms
171 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Istyles.blog.163.com, 25% (18 requests) were made to Os.blog.163.com and 17% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Img.ph.126.net.
Page size can be reduced by 574.4 kB (67%)
859.7 kB
285.3 kB
In fact, the total size of Istyles.blog.163.com main page is 859.7 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. 25% of websites need less resources to load. Javascripts take 521.3 kB which makes up the majority of the site volume.
Potential reduce by 56.9 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 56.9 kB or 76% of the original size.
Potential reduce by 9.2 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. Obviously, Istyles Blog 163 needs image optimization as it can save up to 9.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 358.3 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 358.3 kB or 69% of the original size.
Potential reduce by 149.9 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. Istyles.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.9 kB or 82% of the original size.
Number of requests can be reduced by 31 (46%)
68
37
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Istyles Blog 163. 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.
istyles.blog.163.com
4662 ms
c.css
509 ms
b.css
4628 ms
6630133180817252049.jpg
20081 ms
xcode.png
171 ms
1.0.0.js
201 ms
pc.js
244 ms
ph.js
221 ms
588845651279433262.jpg
732 ms
icon.png
93 ms
1175158027768671087.jpg
821 ms
5637943783515005557.jpg
2120 ms
638948197133914861.jpg
956 ms
1175158027768671084.jpg
3408 ms
1175158027768671083.jpg
1039 ms
1175158027768671090.jpg
2473 ms
1175158027768671089.jpg
1443 ms
1175158027768671153.jpg
1419 ms
5383208929591883518.jpg
1763 ms
5383208929591883517.jpg
1773 ms
1175158027768671085.jpg
1948 ms
lnkbar.png
221 ms
image.png
223 ms
arrow24.png
222 ms
newtopbaricon8.png
223 ms
crossdomain.html
2036 ms
crossdomain.html
2895 ms
request.s
20003 ms
analyse.png
1292 ms
empty.png
68 ms
ava.s
5031 ms
crossdomain.html
1065 ms
ava.s
1897 ms
analyse.png
1544 ms
analytics.js
151 ms
collect
52 ms
blogPhotoAd
2008 ms
close_01.png
76 ms
top_bg.png
146 ms
bottom_bg.png
147 ms
left_bg.png
142 ms
right_bg.png
140 ms
left_top.png
139 ms
right_top.png
196 ms
left_bottom.png
196 ms
right_bottom.png
195 ms
shadow.png
73 ms
UserBeanNew.getVisitor.dwr
1552 ms
NoteBeanNew.getNotesForPrev.dwr
3178 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
3484 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2361 ms
r
826 ms
ava.s
357 ms
ava.s
2567 ms
ava.s
734 ms
ava.s
973 ms
ava.s
993 ms
ava.s
3111 ms
ava.s
1101 ms
ava.s
4549 ms
ava.s
6915 ms
ava.s
4063 ms
ava.s
1506 ms
ava.s
1918 ms
ava.s
2300 ms
ava.s
5815 ms
ava.s
5520 ms
ad
979 ms
close2.png
76 ms
jquery-1.4.2.js
98 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
5950 ms
face22.gif
20 ms
istyles.blog.163.com SEO score
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Istyles.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Istyles.blog.163.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
istyles.blog.163.com
Open Graph description is not detected on the main page of Istyles Blog 163. 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: