Tools & Wizards About Us
pjhome.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pjhome.net

舜子的博客

Page Load Speed

62.4 sec in total

First Response

16.4 sec

Resources Loaded

44.8 sec

Page Rendered

1.2 sec

pjhome.net screenshot

About Website

Visit pjhome.net now to see the best up-to-date Pjhome content for China and also check out these interesting facts you probably never knew about pjhome.net

一名斜杆前端工程师，不限于技术的个人博客

Visit pjhome.net

Key Findings

We analyzed Pjhome.net page load time and found that the first response time was 16.4 sec and then it took 46 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 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

pjhome.net performance score

0

Network Requests Diagram

pjhome.net

16407 ms

global.css

3856 ms

layout.css

5743 ms

typography.css

6452 ms

link.css

6466 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 95% of them (60 requests) were addressed to the original Pjhome.net, 2% (1 request) were made to File.service.qq.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Pjhome.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.4 kB (38%)

Content Size

171.2 kB

After Optimization

106.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pjhome.net main page is 171.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. Only 5% of websites need less resources to load. Images take 91.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 35.6 kB

  • Original 47.7 kB
  • After minification 46.9 kB
  • After compression 12.2 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 35.6 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 5.2 kB

  • Original 91.8 kB
  • After minification 86.6 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. Pjhome images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 9.2 kB

  • Original 11.6 kB
  • After minification 5.5 kB
  • After compression 2.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 9.2 kB or 80% of the original size.

CSS Optimization

-72%

Potential reduce by 14.4 kB

  • Original 20.0 kB
  • After minification 16.2 kB
  • After compression 5.6 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. Pjhome.net needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (83%)

Requests Now

47

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pjhome.net

pjhome.net

16407 ms

global.css

global.css

3856 ms

layout.css

layout.css

5743 ms

typography.css

typography.css

6452 ms

link.css

link.css

6466 ms

editor.css

editor.css

4602 ms

Dphighlighter.css

Dphighlighter.css

6767 ms

common.js

common.js

19767 ms

ajax.js

ajax.js

7203 ms

AjaxRequest.js

AjaxRequest.js

11383 ms

Action.js

Action.js

18686 ms

background.jpg

background.jpg

17037 ms

downCount.js

downCount.js

13484 ms

getDCount.asp

getDCount.asp

20063 ms

102223.jpg

102223.jpg

6583 ms

bar.png

bar.png

410 ms

top.jpg

top.jpg

4138 ms

logo.png

logo.png

777 ms

twitter.png

twitter.png

3883 ms

menu.png

menu.png

1196 ms

background_tbody.png

background_tbody.png

4849 ms

link_button.gif

link_button.gif

2485 ms

day.png

day.png

2816 ms

note.gif

note.gif

2881 ms

connect.gif

connect.gif

3220 ms

more.gif

more.gif

3658 ms

page_copy.gif

page_copy.gif

3609 ms

page.gif

page.gif

5221 ms

quote.png

quote.png

5320 ms

layout.gif

layout.gif

4780 ms

getPJBlog.png

getPJBlog.png

19962 ms

house.gif

house.gif

5873 ms

rss.png

rss.png

5170 ms

monitor.gif

monitor.gif

11630 ms

bug.gif

bug.gif

6851 ms

book_open.gif

book_open.gif

6314 ms

cog.gif

cog.gif

5696 ms

page_white_flash.gif

page_white_flash.gif

6094 ms

page_white_code.gif

page_white_code.gif

7294 ms

information.gif

information.gif

6475 ms

heart.gif

heart.gif

6705 ms

photo.gif

photo.gif

6854 ms

logos.gif

logos.gif

7498 ms

valid-rss.png

valid-rss.png

7636 ms

valid-atom.png

valid-atom.png

7234 ms

xhtml.png

xhtml.png

7631 ms

css.png

css.png

8081 ms

detect.gif

detect.gif

7905 ms

h20121114171235.jpg

h20121114171235.jpg

19959 ms

b201272174420.png

b201272174420.png

14884 ms

3201234183641.jpg

3201234183641.jpg

19958 ms

1201234184516.jpg

1201234184516.jpg

19959 ms

120125713510.png

120125713510.png

19959 ms

download.asp

download.asp

19960 ms

92011121818932.png

92011121818932.png

19960 ms

j2011121818942.png

j2011121818942.png

19961 ms

n2011111516727.png

n2011111516727.png

19960 ms

d201172121111.png

d201172121111.png

19961 ms

42011720234956.png

42011720234956.png

19961 ms

c2011421105825.jpg

c2011421105825.jpg

19961 ms

branding.css

branding.css

18 ms

branding.css

branding.css

26 ms

foot.png

foot.png

13057 ms

SEO Factors

pjhome.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    UT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pjhome.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is . Our system also found out that Pjhome.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

pjhome.net

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