18.4 sec in total
3.7 sec
14 sec
666 ms
Visit ljxhistory.blog.163.com now to see the best up-to-date Ljxhistory Blog 163 content for China and also check out these interesting facts you probably never knew about ljxhistory.blog.163.com
刘继兴的网易博客,很纯粹的文史博客, 刘继兴,作家,文史学者,传媒资深人士,山西柳林县人,现工作定居太原。生于1970年,1992年毕业于天津大学,十余年来,在文、史、哲以及美学、传播学等领域均有建树。共发表各类作品550余万字。有《刘继兴读史》、《魅力毛泽东》、《历史的迷踪》、《哭泣的历史》、《历史上的那些牛人们》、《民国大腕》等著作问世。主编有《读史》丛书系列。 联系方式: Email:ljx...
Visit ljxhistory.blog.163.comWe analyzed Ljxhistory.blog.163.com page load time and found that the first response time was 3.7 sec and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ljxhistory.blog.163.com performance score
3743 ms
18 ms
1004 ms
2296 ms
37 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ljxhistory.blog.163.com, 27% (22 requests) were made to Os.blog.163.com and 18% (15 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Api.blog.163.com.
Page size can be reduced by 636.8 kB (48%)
1.3 MB
695.1 kB
In fact, the total size of Ljxhistory.blog.163.com main page is 1.3 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 489.7 kB which makes up the majority of the site volume.
Potential reduce by 138.3 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 138.3 kB or 80% of the original size.
Potential reduce by 22.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. Ljxhistory 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 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. Ljxhistory.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 31 (38%)
82
51
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ljxhistory 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 13 to 1 for JavaScripts and as a result speed up the page load time.
ljxhistory.blog.163.com
3743 ms
c.css
18 ms
b.css
1004 ms
5747719024432204717.jpg
2296 ms
icon.png
37 ms
5747719024432204716.jpg
1566 ms
5747719024432204714.jpg
921 ms
5717601201924227865.jpg
3593 ms
6598159382740011169.jpg
391 ms
blog_rec.png
108 ms
6630133180817252049.jpg
666 ms
xcode.png
96 ms
1.0.0.js
98 ms
pc.js
98 ms
ph.js
97 ms
5747719024432204715.jpg
4101 ms
lnkbar.png
92 ms
image.png
95 ms
arrow24.png
94 ms
newtopbaricon8.png
93 ms
crossdomain.html
913 ms
crossdomain.html
793 ms
crossdomain.html
899 ms
request.s
900 ms
analyse.png
762 ms
ava.s
2846 ms
loftericon.png
424 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
819 ms
analyse.png
737 ms
analytics.js
31 ms
collect
14 ms
SetupBeanNew.getCustomModulesData.dwr
4514 ms
HomeBeanNew.getFriends.dwr
2858 ms
HomeBeanNew.getAccessStatistics.dwr
1170 ms
HomeBeanNew.getMonthStatistics.dwr
1321 ms
BlogBeanNew.getRecentCommentsByOffset.dwr
1953 ms
blogPhotoAd
355 ms
close_01.png
5 ms
top_bg.png
8 ms
bottom_bg.png
9 ms
left_bg.png
12 ms
right_bg.png
10 ms
left_top.png
11 ms
right_top.png
11 ms
left_bottom.png
12 ms
right_bottom.png
12 ms
shadow.png
8 ms
r
701 ms
BgsBean.getBgsUserByUserId.dwr
1574 ms
ad
804 ms
close2.png
5 ms
face45.gif
17 ms
face5.gif
15 ms
face50.gif
16 ms
face55.gif
16 ms
face56.gif
16 ms
jquery-1.4.2.js
9 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
4271 ms
ava.s
497 ms
ava.s
657 ms
ava.s
920 ms
ava.s
927 ms
ava.s
957 ms
ava.s
2755 ms
ava.s
2443 ms
ava.s
1381 ms
ava.s
1391 ms
ava.s
1446 ms
ava.s
1840 ms
ava.s
1870 ms
ava.s
1931 ms
ava.s
3705 ms
ava.s
2332 ms
ava.s
2335 ms
ava.s
4119 ms
ava.s
4358 ms
ava.s
2801 ms
ava.s
2764 ms
1835216848155107811.jpg
3444 ms
3370662846111248638.jpg
1461 ms
573364527561142975.jpg
4454 ms
1601592617485323232.jpg
1273 ms
3852548006239338448.jpg
3021 ms
ljxhistory.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 Ljxhistory.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 Ljxhistory.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.
ljxhistory.blog.163.com
Open Graph description is not detected on the main page of Ljxhistory 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: