31 sec in total
5.5 sec
24.4 sec
1.1 sec
Welcome to ng6991233.blog.163.com homepage info - get ready to check Ng 6991233 Blog 163 best content for China right away, or after learning these important things about ng6991233.blog.163.com
Visit ng6991233.blog.163.comWe analyzed Ng6991233.blog.163.com page load time and found that the first response time was 5.5 sec and then it took 25.5 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 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ng6991233.blog.163.com performance score
5511 ms
94 ms
825 ms
9094 ms
1038 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ng6991233.blog.163.com, 31% (38 requests) were made to Os.blog.163.com and 15% (18 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 1.1 MB (16%)
6.6 MB
5.6 MB
In fact, the total size of Ng6991233.blog.163.com main page is 6.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. 45% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 133.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 133.5 kB or 79% of the original size.
Potential reduce by 189.1 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. Ng 6991233 Blog 163 images are well optimized though.
Potential reduce by 584.2 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 584.2 kB or 67% of the original size.
Potential reduce by 149.4 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. Ng6991233.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.4 kB or 82% of the original size.
Number of requests can be reduced by 41 (36%)
113
72
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ng 6991233 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 19 to 1 for JavaScripts and as a result speed up the page load time.
ng6991233.blog.163.com
5511 ms
c.css
94 ms
b.css
825 ms
1579356094341574712.jpg
9094 ms
1558526946064930315.jpg
1038 ms
6598215457833618261.jpg
388 ms
6598170377856867330.jpg
1097 ms
1877156619783608000.jpg
382 ms
6597361137239267792.jpg
765 ms
6598101108624400280.jpg
5013 ms
4846717624081632443.jpg
2682 ms
6630765400002530783.jpg
622 ms
6598109904717167450.jpg
1025 ms
6598065924192904150.jpg
743 ms
6631369031890952806.jpg
618 ms
6598162681275266272.png
4227 ms
6630133180817252049.jpg
7120 ms
6631451495262963485.jpg
551 ms
6598222054903142584.jpg
642 ms
2275725186706123389.jpg
20361 ms
blog_rec.png
219 ms
1982991210927205362.jpg
20349 ms
1982991210927205359.jpg
20349 ms
1982991210927205368.jpg
20349 ms
1982991210927205365.jpg
20349 ms
4546102348854346056.jpg
20349 ms
2039286206269077640.jpg
20349 ms
goodbloghead.png
209 ms
icon.png
213 ms
lnkbar.png
212 ms
image.png
211 ms
arrow24.png
211 ms
xcode.png
23 ms
newtopbaricon8.png
10 ms
1.0.0.js
88 ms
pc.js
54 ms
ph.js
56 ms
crossdomain.html
2190 ms
crossdomain.html
2029 ms
request.s
650 ms
analyse.png
885 ms
ava.s
826 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
2453 ms
crossdomain.html
1998 ms
ava.s
785 ms
analyse.png
13293 ms
analytics.js
112 ms
collect
56 ms
blogPhotoAd
432 ms
close_01.png
52 ms
top_bg.png
77 ms
bottom_bg.png
73 ms
left_bg.png
74 ms
right_bg.png
72 ms
left_top.png
74 ms
right_top.png
71 ms
left_bottom.png
89 ms
right_bottom.png
89 ms
shadow.png
47 ms
r
882 ms
SetupBeanNew.getResourceModulesData.dwr
773 ms
HomeBeanNew.getFriends.dwr
5076 ms
HomeBeanNew.getAccessStatistics.dwr
1113 ms
UserSpaceBean.getUserSpace.dwr
3503 ms
HomeBeanNew.getMonthStatistics.dwr
1171 ms
UserBeanNew.getVisitor.dwr
1113 ms
NoteBeanNew.getNotesForPrev.dwr
4007 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1496 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1730 ms
ad
669 ms
close2.png
7 ms
jquery-1.4.2.js
19 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
4473 ms
BgsBean.getBgsUserByUserId.dwr
801 ms
ava.s
413 ms
ava.s
408 ms
ava.s
772 ms
ava.s
787 ms
ava.s
787 ms
ava.s
789 ms
ava.s
788 ms
ava.s
790 ms
ava.s
1153 ms
ava.s
1167 ms
ava.s
1178 ms
ava.s
1183 ms
ava.s
2906 ms
ava.s
3399 ms
ava.s
3652 ms
AlbumBeanNew.getUserSpace.dwr
4626 ms
sniff.png
441 ms
face59.gif
17 ms
face49.gif
16 ms
face50.gif
16 ms
face50.gif
17 ms
face25.gif
17 ms
face58.gif
16 ms
bless.png
16 ms
dbf.gif
9 ms
ava.s
787 ms
ava.s
378 ms
ava.s
784 ms
ava.s
378 ms
ava.s
396 ms
ava.s
396 ms
ava.s
757 ms
ava.s
762 ms
ava.s
2382 ms
ava.s
769 ms
ava.s
1139 ms
ava.s
1143 ms
ava.s
1149 ms
ava.s
1162 ms
ava.s
1163 ms
ava.s
1500 ms
ava.s
1501 ms
ava.s
3157 ms
ava.s
1581 ms
ava.s
5371 ms
73667294276566.js
179 ms
-1.gif
16 ms
116548245199269.js
2940 ms
empty.png
31 ms
6619558077980199108.jpg
804 ms
ng6991233.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 Ng6991233.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 Ng6991233.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.
ng6991233.blog.163.com
Open Graph description is not detected on the main page of Ng 6991233 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: