25.4 sec in total
2.5 sec
22.6 sec
334 ms
Click here to check amazing Devilswrwr Blog 163 content for China. Otherwise, check out these important facts you probably never knew about devilswrwr.blog.163.com
去除inline-block元素间间距的N种方法,使用iScroll时,input等不能输入内容、文本不能选择的解决方法,为什么我们放弃了 Zepto,魏武挥:媒体们做“内容产品化”之前,所需要的虎牙前期准备(转),连BAT设计师都在使用的视觉动线技巧(上)原创: skys 我们的设计日记,一款APP的交互文档从撰写到交付② (转自UI中国),站在风口上的交互,未来的发展令人期待。(转自UI中国)...
Visit devilswrwr.blog.163.comWe analyzed Devilswrwr.blog.163.com page load time and found that the first response time was 2.5 sec and then it took 22.9 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
devilswrwr.blog.163.com performance score
2516 ms
389 ms
385 ms
116 ms
5520 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Devilswrwr.blog.163.com, 35% (26 requests) were made to B.bst.126.net and 11% (8 requests) were made to B2.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.bimg.126.net.
Page size can be reduced by 620.5 kB (53%)
1.2 MB
559.6 kB
In fact, the total size of Devilswrwr.blog.163.com main page is 1.2 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. 45% of websites need less resources to load. Javascripts take 499.7 kB which makes up the majority of the site volume.
Potential reduce by 119.5 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 119.5 kB or 80% of the original size.
Potential reduce by 19.9 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. Devilswrwr Blog 163 images are well optimized though.
Potential reduce by 331.9 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 331.9 kB or 66% of the original size.
Potential reduce by 149.2 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. Devilswrwr.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.2 kB or 82% of the original size.
Number of requests can be reduced by 39 (58%)
67
28
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Devilswrwr 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 15 to 1 for JavaScripts and as a result speed up the page load time.
devilswrwr.blog.163.com
2516 ms
c.css
389 ms
nb.css
385 ms
top.jpg
116 ms
bee1c1aa7d02d49d0a87e084ca419.png
5520 ms
5789658796761600565.jpg
20089 ms
20150419154540534.png
6122 ms
20160125213435_580.jpg
20087 ms
531400.jpg
1633 ms
1209576-33c43d3e35a41ad4.png
1428 ms
20141023_31_51377_0.jpg!view
5492 ms
icon.png
97 ms
6630133180817252049.jpg
1718 ms
1.0.0.js
116 ms
pc.js
89 ms
ph.js
89 ms
bg.gif
78 ms
line.gif
78 ms
xcode.png
82 ms
434923.jpg
1681 ms
465088.png
1672 ms
lnkbar.png
79 ms
image.png
84 ms
arrow24.png
81 ms
newtopbaricon8.png
83 ms
crossdomain.html
1883 ms
crossdomain.html
672 ms
crossdomain.html
993 ms
request.s
628 ms
analyse.png
933 ms
empty.png
40 ms
ava.s
843 ms
loftericon.png
440 ms
nb.css
13 ms
ava.s
852 ms
background.gif
7 ms
player_02.gif
6 ms
player_06.gif
5 ms
player_16.gif
8 ms
player_17.gif
8 ms
player_23.gif
9 ms
timeline_1.gif
10 ms
player_29.gif
9 ms
analyse.png
820 ms
analytics.js
14 ms
collect
14 ms
UserSpaceBean.getUserSpace.dwr
802 ms
blogPhotoAd
8264 ms
close_01.png
27 ms
top_bg.png
29 ms
bottom_bg.png
25 ms
left_bg.png
28 ms
right_bg.png
23 ms
left_top.png
27 ms
right_top.png
28 ms
left_bottom.png
27 ms
right_bottom.png
28 ms
shadow.png
24 ms
45079991258605.js
2756 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
894 ms
HomeBeanNew.getAccessStatistics.dwr
2453 ms
HomeBeanNew.getWeatherCityCode.dwr
2191 ms
NoteBeanNew.getNotesForPrev.dwr
1278 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1282 ms
-1.gif
25 ms
20890734366110.js
3606 ms
.gif
5 ms
BgsBean.getBgsUserByUserId.dwr
2025 ms
winy2015test-403
1242 ms
6631303061191795211.jpg
1608 ms
r
815 ms
ad
790 ms
close2.png
8 ms
jquery-1.4.2.js
8 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
1117 ms
devilswrwr.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 Devilswrwr.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 Devilswrwr.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.
devilswrwr.blog.163.com
Open Graph description is not detected on the main page of Devilswrwr 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: