28.7 sec in total
3.7 sec
24.8 sec
238 ms
Visit gengjb1100.blog.163.com now to see the best up-to-date Gengjb 1100 Blog 163 content for China and also check out these interesting facts you probably never knew about gengjb1100.blog.163.com
Visit gengjb1100.blog.163.comWe analyzed Gengjb1100.blog.163.com page load time and found that the first response time was 3.7 sec and then it took 25 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
gengjb1100.blog.163.com performance score
3664 ms
48 ms
3893 ms
699 ms
38 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Gengjb1100.blog.163.com, 27% (6 requests) were made to B2.bst.126.net and 27% (6 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 554.8 kB (57%)
972.4 kB
417.6 kB
In fact, the total size of Gengjb1100.blog.163.com main page is 972.4 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. 15% of websites need less resources to load. Javascripts take 455.6 kB which makes up the majority of the site volume.
Potential reduce by 82.7 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 82.7 kB or 78% of the original size.
Potential reduce by 8.4 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. Gengjb 1100 Blog 163 images are well optimized though.
Potential reduce by 313.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 313.9 kB or 69% of the original size.
Potential reduce by 149.7 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. Gengjb1100.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.7 kB or 82% of the original size.
Number of requests can be reduced by 10 (50%)
20
10
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gengjb 1100 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 4 to 1 for JavaScripts and as a result speed up the page load time.
gengjb1100.blog.163.com
3664 ms
c.css
48 ms
b.css
3893 ms
6630133180817252049.jpg
699 ms
xcode.png
38 ms
1.0.0.js
133 ms
pc.js
1016 ms
ph.js
1019 ms
5774459147219359392.jpg
19704 ms
icon.png
795 ms
5792473545728813558.jpg
2249 ms
5791629120798681638.jpg
1766 ms
5792473545728813445.jpg
1826 ms
5792473545728813447.jpg
1827 ms
5792473545728813446.jpg
2071 ms
lnkbar.png
657 ms
image.png
659 ms
arrow24.png
658 ms
newtopbaricon8.png
658 ms
analyse.png
890 ms
analytics.js
58 ms
collect
44 ms
gengjb1100.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 Gengjb1100.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 Gengjb1100.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.
gengjb1100.blog.163.com
Open Graph description is not detected on the main page of Gengjb 1100 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: