Tools & Wizards About Us
junhuakd1218.blog.163.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

57.5 sec in total

First Response

18.8 sec

Resources Loaded

38.1 sec

Page Rendered

679 ms

junhuakd1218.blog.163.com screenshot

About Website

Welcome to junhuakd1218.blog.163.com homepage info - get ready to check Junhuakd 1218 Blog 163 best content for China right away, or after learning these important things about junhuakd1218.blog.163.com

Visit junhuakd1218.blog.163.com

Key Findings

We analyzed Junhuakd1218.blog.163.com page load time and found that the first response time was 18.8 sec and then it took 38.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

junhuakd1218.blog.163.com performance score

0

Network Requests Diagram

junhuakd1218.blog.163.com

18761 ms

c.css

10 ms

b.css

689 ms

6630851161909500111.jpg

2544 ms

6630145275443670481.jpg

1334 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Junhuakd1218.blog.163.com, 34% (14 requests) were made to Img.bimg.126.net and 17% (7 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (18.8 sec) belongs to the original domain Junhuakd1218.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 559.9 kB (32%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Junhuakd1218.blog.163.com main page is 1.7 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 975.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 89.7 kB

  • Original 115.8 kB
  • After minification 115.8 kB
  • After compression 26.1 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 89.7 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 975.5 kB
  • After minification 967.0 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. Junhuakd 1218 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 310.4 kB

  • Original 448.7 kB
  • After minification 448.7 kB
  • After compression 138.4 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 310.4 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 151.3 kB

  • Original 184.6 kB
  • After minification 180.6 kB
  • After compression 33.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. Junhuakd1218.blog.163.com needs all CSS files to be minified and compressed as it can save up to 151.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (38%)

Requests Now

40

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Junhuakd 1218 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.

Network Requests Diagram

junhuakd1218.blog.163.com

junhuakd1218.blog.163.com

18761 ms

c.css

c.css

10 ms

b.css

b.css

689 ms

6630851161909500111.jpg

6630851161909500111.jpg

2544 ms

6630145275443670481.jpg

6630145275443670481.jpg

1334 ms

1454099729788347590.jpg

1454099729788347590.jpg

1123 ms

6630819276071461262.jpg

6630819276071461262.jpg

3528 ms

1957376988146243619.jpg

1957376988146243619.jpg

4151 ms

6630251928071362839.jpg

6630251928071362839.jpg

3264 ms

2665005079514603788.jpg

2665005079514603788.jpg

2829 ms

5772207347405842278.jpg

5772207347405842278.jpg

1081 ms

blog_rec.png

blog_rec.png

38 ms

5774177672242824107.jpg

5774177672242824107.jpg

1078 ms

5774177672242824162.jpg

5774177672242824162.jpg

1085 ms

5774177672242824161.jpg

5774177672242824161.jpg

1084 ms

5774177672242824163.jpg

5774177672242824163.jpg

5404 ms

5774177672242824164.jpg

5774177672242824164.jpg

1117 ms

5774177672242824165.jpg

5774177672242824165.jpg

1535 ms

5774177672242824166.jpg

5774177672242824166.jpg

1535 ms

5774177672242824168.jpg

5774177672242824168.jpg

1605 ms

5774177672242824167.jpg

5774177672242824167.jpg

1605 ms

6597157727589082857.jpg

6597157727589082857.jpg

840 ms

1147573480067534014.jpg

1147573480067534014.jpg

2651 ms

1181631952249358335.jpg

1181631952249358335.jpg

1120 ms

3974989621124976846.jpg

3974989621124976846.jpg

12728 ms

1203868475408549071.jpg

1203868475408549071.jpg

12651 ms

5770799973321951917.jpg

5770799973321951917.jpg

12376 ms

icon.png

icon.png

14 ms

lnkbar.png

lnkbar.png

9 ms

image.png

image.png

10 ms

arrow24.png

arrow24.png

10 ms

5774177672242824105.jpg

5774177672242824105.jpg

2333 ms

6630133180817252049.jpg

6630133180817252049.jpg

1105 ms

xcode.png

xcode.png

10 ms

1.0.0.js

1.0.0.js

387 ms

pc.js

pc.js

208 ms

ph.js

ph.js

9 ms

newtopbaricon8.png

newtopbaricon8.png

6 ms

analyse.png

analyse.png

1019 ms

analytics.js

analytics.js

25 ms

collect

collect

27 ms

SEO Factors

junhuakd1218.blog.163.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Junhuakd1218.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 Junhuakd1218.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.

Social Sharing Optimization

junhuakd1218.blog.163.com

Open Graph description is not detected on the main page of Junhuakd 1218 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: