25.2 sec in total
2.2 sec
22.5 sec
449 ms
Welcome to 15260000.blog.163.com homepage info - get ready to check 15260000 Blog 163 best content for China right away, or after learning these important things about 15260000.blog.163.com
嫩模雅蒂的拍摄,pm:2:50 pm2.5 雾气罩京城 嫩模韩子萱亲情出演的时尚大片,希威社的网易博客,北京地区有影响力的摄影活动团体希威社,
Visit 15260000.blog.163.comWe analyzed 15260000.blog.163.com page load time and found that the first response time was 2.2 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
15260000.blog.163.com performance score
2248 ms
74 ms
48 ms
102 ms
83 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 15260000.blog.163.com, 32% (28 requests) were made to Os.blog.163.com and 23% (20 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 Gorgon.youdao.com.
Page size can be reduced by 574.2 kB (60%)
955.6 kB
381.4 kB
In fact, the total size of 15260000.blog.163.com main page is 955.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 489.7 kB which makes up the majority of the site volume.
Potential reduce by 86.8 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 86.8 kB or 79% of the original size.
Potential reduce by 12.6 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. 15260000 Blog 163 images are well optimized though.
Potential reduce by 326.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 326.6 kB or 67% of the original size.
Potential reduce by 148.3 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. 15260000.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.3 kB or 82% of the original size.
Number of requests can be reduced by 36 (42%)
85
49
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 15260000 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 14 to 1 for JavaScripts and as a result speed up the page load time.
15260000.blog.163.com
2248 ms
c.css
74 ms
nb.css
48 ms
top_banner.jpg
102 ms
bg_tab.jpg
83 ms
tap_on.gif
84 ms
blog_rec.png
82 ms
goodbloghead.png
33 ms
bg_web_b.gif
27 ms
6630133180817252049.jpg
7490 ms
1.0.0.js
99 ms
pc.js
33 ms
ph.js
32 ms
icon.png
14 ms
lnkbar.png
23 ms
image.png
22 ms
arrow24.png
22 ms
newtopbaricon8.png
21 ms
xcode.png
14 ms
crossdomain.html
959 ms
crossdomain.html
989 ms
crossdomain.html
2008 ms
request.s
20090 ms
analyse.png
794 ms
empty.png
43 ms
1850416496995882233.jpg
1816 ms
ava.s
10243 ms
loftericon.png
522 ms
ava.s
860 ms
6608273790143089395.jpg
2198 ms
analyse.png
864 ms
analytics.js
88 ms
collect
39 ms
HomeBeanNew.getFriends.dwr
1063 ms
HomeBeanNew.getAccessStatistics.dwr
3069 ms
UserBeanNew.getVisitor.dwr
1497 ms
NoteBeanNew.getNotesForPrev.dwr
6568 ms
HomeBeanNew.getClassifyModuleData.dwr
1513 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1948 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3917 ms
blogPhotoAd
1597 ms
close_01.png
51 ms
top_bg.png
49 ms
bottom_bg.png
96 ms
left_bg.png
95 ms
right_bg.png
95 ms
left_top.png
97 ms
right_top.png
97 ms
left_bottom.png
97 ms
right_bottom.png
158 ms
shadow.png
52 ms
ava.s
418 ms
ava.s
769 ms
ava.s
781 ms
ava.s
859 ms
ava.s
14887 ms
ava.s
887 ms
ava.s
1191 ms
ava.s
5943 ms
ava.s
1298 ms
ava.s
5750 ms
ava.s
5671 ms
ava.s
1273 ms
ava.s
5051 ms
ava.s
5847 ms
ava.s
10147 ms
ava.s
10929 ms
ava.s
10484 ms
ava.s
9062 ms
ava.s
8519 ms
ava.s
8879 ms
ava.s
9224 ms
ava.s
9493 ms
ava.s
9572 ms
ava.s
10235 ms
ava.s
9914 ms
ava.s
12977 ms
r
2289 ms
BgsBean.getBgsUserByUserId.dwr
986 ms
close2.png
7 ms
ad
2338 ms
jquery-1.4.2.js
166 ms
face0.gif
40 ms
face50.gif
39 ms
face51.gif
44 ms
face58.gif
40 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1299 ms
15260000.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 15260000.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 15260000.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.
15260000.blog.163.com
Open Graph description is not detected on the main page of 15260000 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: