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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jidianpeijian.blog.163.com

机电人 - 机电人 - 网易博客

Page Load Speed

26.7 sec in total

First Response

3.9 sec

Resources Loaded

22.5 sec

Page Rendered

323 ms

jidianpeijian.blog.163.com screenshot

About Website

Click here to check amazing Jidianpeijian Blog 163 content for China. Otherwise, check out these important facts you probably never knew about jidianpeijian.blog.163.com

电机配件生产设计工艺及部门,特种电机分类,你不可不知的电机维修小技巧 （二）,三相异步电动机不能起动的原因,电动机过热,你不可不知的电机维修小技巧 （一）,集电环分类,现在天气冷了啊,网易博客积分网易博客等级制度一览表,国家电网公司3月28日发行第五期超短期融资券,机电人的网易博客,咱就是个-机电维修人,咱就是个机电人

Visit jidianpeijian.blog.163.com

Key Findings

We analyzed Jidianpeijian.blog.163.com page load time and found that the first response time was 3.9 sec and then it took 22.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. 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.

Performance Metrics

jidianpeijian.blog.163.com performance score

0

Network Requests Diagram

jidianpeijian.blog.163.com

3873 ms

c.css

210 ms

b.css

866 ms

5775585047126545857.jpg

20241 ms

icon.png

71 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Jidianpeijian.blog.163.com, 21% (12 requests) were made to B.bst.126.net and 17% (10 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Img.bimg.126.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 589.5 kB (66%)

Content Size

891.2 kB

After Optimization

301.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jidianpeijian.blog.163.com main page is 891.2 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. 25% of websites need less resources to load. Javascripts take 489.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 103.0 kB

  • Original 127.4 kB
  • After minification 127.4 kB
  • After compression 24.4 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 103.0 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 9.2 kB

  • Original 90.2 kB
  • After minification 81.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. Jidianpeijian Blog 163 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 326.6 kB

  • Original 489.7 kB
  • After minification 489.7 kB
  • After compression 163.1 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.

CSS Optimization

-82%

Potential reduce by 150.7 kB

  • Original 183.8 kB
  • After minification 179.8 kB
  • After compression 33.2 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. Jidianpeijian.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jidianpeijian 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

jidianpeijian.blog.163.com

jidianpeijian.blog.163.com

3873 ms

c.css

c.css

210 ms

b.css

b.css

866 ms

5775585047126545857.jpg

5775585047126545857.jpg

20241 ms

icon.png

icon.png

71 ms

5782903396520893920.jpg

5782903396520893920.jpg

20232 ms

5791347645822216216.jpg

5791347645822216216.jpg

20231 ms

5782903396520893963.jpg

5782903396520893963.jpg

20231 ms

5775585047126545876.jpg

5775585047126545876.jpg

20231 ms

5775585047126545926.jpg

5775585047126545926.jpg

20231 ms

5782903396520893964.jpg

5782903396520893964.jpg

20231 ms

lnkbar.png

lnkbar.png

67 ms

image.png

image.png

129 ms

6630133180817252049.jpg

6630133180817252049.jpg

1002 ms

xcode.png

xcode.png

411 ms

1.0.0.js

1.0.0.js

144 ms

pc.js

pc.js

438 ms

ph.js

ph.js

490 ms

arrow24.png

arrow24.png

97 ms

newtopbaricon8.png

newtopbaricon8.png

120 ms

crossdomain.html

crossdomain.html

880 ms

crossdomain.html

crossdomain.html

1015 ms

crossdomain.html

crossdomain.html

921 ms

request.s

request.s

891 ms

analyse.png

analyse.png

918 ms

ava.s

ava.s

854 ms

loftericon.png

loftericon.png

401 ms

ava.s

ava.s

1286 ms

analyse.png

analyse.png

824 ms

analytics.js

analytics.js

133 ms

collect

collect

22 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

4786 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1161 ms

NoteBeanNew.getNotesForPrev.dwr

NoteBeanNew.getNotesForPrev.dwr

1163 ms

TagBeanNew.getHostHotTags.dwr

TagBeanNew.getHostHotTags.dwr

1950 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1827 ms

blogPhotoAd

blogPhotoAd

443 ms

close_01.png

close_01.png

21 ms

top_bg.png

top_bg.png

27 ms

bottom_bg.png

bottom_bg.png

27 ms

left_bg.png

left_bg.png

34 ms

right_bg.png

right_bg.png

25 ms

left_top.png

left_top.png

33 ms

right_top.png

right_top.png

33 ms

left_bottom.png

left_bottom.png

43 ms

right_bottom.png

right_bottom.png

40 ms

shadow.png

shadow.png

19 ms

r

r

791 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1303 ms

face50.gif

face50.gif

19 ms

face56.gif

face56.gif

19 ms

bless.png

bless.png

19 ms

fly.gif

fly.gif

23 ms

ad

ad

845 ms

close2.png

close2.png

10 ms

jquery-1.4.2.js

jquery-1.4.2.js

18 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

1754 ms

ava.s

ava.s

503 ms

SEO Factors

jidianpeijian.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 Jidianpeijian.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 Jidianpeijian.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

jidianpeijian.blog.163.com

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