Tools & Wizards About Us
pengke.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pengke.com

彭客网 - 徐州首席生活服务平台

Page Load Speed

50.4 sec in total

First Response

1.3 sec

Resources Loaded

48.6 sec

Page Rendered

495 ms

pengke.com screenshot

About Website

Click here to check amazing Pengke content for China. Otherwise, check out these important facts you probably never knew about pengke.com

彭客网是徐州报业传媒集团旗下综合性社区门户网站，《彭城晚报》战略合作伙伴，致力于为网民提供新鲜、真实、有用、好玩的生活资讯，打造徐州首席生活服务平台 ,彭客网

Visit pengke.com

Key Findings

We analyzed Pengke.com page load time and found that the first response time was 1.3 sec and then it took 49.1 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 were 49 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

pengke.com performance score

0

Network Requests Diagram

pengke.com

1337 ms

www.pengke.com

17742 ms

lightapp.js

5018 ms

layout.css

2564 ms

new_index.css

4195 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 27% of them (32 requests) were addressed to the original Pengke.com, 34% (41 requests) were made to Res.5236524.com and 15% (18 requests) were made to Avatar.5236524.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Pengke.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.6 kB (21%)

Content Size

829.0 kB

After Optimization

651.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pengke.com main page is 829.0 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. 20% of websites need less resources to load. Images take 558.0 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 113.7 kB

  • Original 173.0 kB
  • After minification 166.6 kB
  • After compression 59.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 113.7 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 16.0 kB

  • Original 558.0 kB
  • After minification 542.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. Pengke images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 22.8 kB

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 43.5 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 22.8 kB or 34% of the original size.

CSS Optimization

-79%

Potential reduce by 25.1 kB

  • Original 31.7 kB
  • After minification 27.0 kB
  • After compression 6.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. Pengke.com needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (27%)

Requests Now

62

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pengke.com

pengke.com

1337 ms

www.pengke.com

www.pengke.com

17742 ms

lightapp.js

lightapp.js

5018 ms

layout.css

layout.css

2564 ms

new_index.css

new_index.css

4195 ms

jquery1.8.js

jquery1.8.js

20008 ms

jquery.pause.min.js

jquery.pause.min.js

6290 ms

weiboscroll.js

weiboscroll.js

1927 ms

index.js

index.js

3788 ms

3459506.js

3459506.js

990 ms

ping.js

ping.js

2301 ms

index_ad_woman_0821.jpg

index_ad_woman_0821.jpg

19984 ms

tgly.jpg

tgly.jpg

19984 ms

152510ecsf6rvqbmccf2by.jpg

152510ecsf6rvqbmccf2by.jpg

19984 ms

95_avatar_small.jpg

95_avatar_small.jpg

1218 ms

1658371ztiigkzngm1vy11.jpg

1658371ztiigkzngm1vy11.jpg

8735 ms

14_avatar_small.jpg

14_avatar_small.jpg

1227 ms

21_avatar_small.jpg

21_avatar_small.jpg

2828 ms

86_avatar_small.jpg

86_avatar_small.jpg

2838 ms

15_avatar_small.jpg

15_avatar_small.jpg

1281 ms

73_avatar_small.jpg

73_avatar_small.jpg

2974 ms

63_avatar_small.jpg

63_avatar_small.jpg

1608 ms

84_avatar_small.jpg

84_avatar_small.jpg

1632 ms

27_avatar_small.jpg

27_avatar_small.jpg

3068 ms

05_avatar_small.jpg

05_avatar_small.jpg

2005 ms

09_avatar_small.jpg

09_avatar_small.jpg

2036 ms

43_avatar_small.jpg

43_avatar_small.jpg

2403 ms

64_avatar_small.jpg

64_avatar_small.jpg

3765 ms

79_avatar_small.jpg

79_avatar_small.jpg

3751 ms

87_avatar_small.jpg

87_avatar_small.jpg

3630 ms

68_avatar_small.jpg

68_avatar_small.jpg

4836 ms

32_avatar_small.jpg

32_avatar_small.jpg

6550 ms

0952453gythtj87boz23h5.jpg

0952453gythtj87boz23h5.jpg

4673 ms

120840fppmeqnipgiqibjj.jpg

120840fppmeqnipgiqibjj.jpg

8966 ms

1252164x86szsk464xxo8a.jpeg

1252164x86szsk464xxo8a.jpeg

7903 ms

1011468z82jbptgnc37b31.jpg

1011468z82jbptgnc37b31.jpg

12800 ms

ad1.jpg

ad1.jpg

3291 ms

misc.php

misc.php

19974 ms

misc.php

misc.php

13132 ms

misc.php

misc.php

13163 ms

misc.php

misc.php

19066 ms

misc.php

misc.php

19969 ms

misc.php

misc.php

19970 ms

misc.php

misc.php

19971 ms

misc.php

misc.php

19971 ms

misc.php

misc.php

19971 ms

misc.php

misc.php

19973 ms

misc.php

misc.php

19974 ms

misc.php

misc.php

19973 ms

misc.php

misc.php

19974 ms

misc.php

misc.php

19974 ms

101448joon5gijl8gzh9ww.jpg

101448joon5gijl8gzh9ww.jpg

17200 ms

144727v9gq97xx4z7xr7qr.jpg

144727v9gq97xx4z7xr7qr.jpg

8280 ms

110245i55ptdvzqt5vvdzd.jpg

110245i55ptdvzqt5vvdzd.jpg

18867 ms

111153sr0j67ruur0zxs7b.jpg

111153sr0j67ruur0zxs7b.jpg

19974 ms

115052w36wkwb6rwwz0rk7.jpg

115052w36wkwb6rwwz0rk7.jpg

11260 ms

bg.jpg

bg.jpg

19974 ms

logo.png

logo.png

1811 ms

sprites.jpg

sprites.jpg

3279 ms

pk2wei.jpg

pk2wei.jpg

865 ms

1.jpg

1.jpg

19973 ms

1.png

1.png

2868 ms

2.jpg

2.jpg

5038 ms

2.png

2.png

3098 ms

3.jpg

3.jpg

19973 ms

3.png

3.png

4737 ms

4.jpg

4.jpg

8328 ms

4.png

4.png

5153 ms

5.jpg

5.jpg

13533 ms

5.png

5.png

5975 ms

apple.jpg

apple.jpg

9686 ms

apple.png

apple.png

8782 ms

7.jpg

7.jpg

18246 ms

7.png

7.png

17975 ms

8.jpg

8.jpg

17213 ms

8.png

8.png

18242 ms

1.jpg

1.jpg

19969 ms

2.jpg

2.jpg

19970 ms

3.jpg

3.jpg

19970 ms

21.png

21.png

19971 ms

4.jpg

4.jpg

19970 ms

idx_ylh_tl_0814.jpg

idx_ylh_tl_0814.jpg

6102 ms

index_ad_qingshaonian_0424.jpg

index_ad_qingshaonian_0424.jpg

19970 ms

hot.png

hot.png

19949 ms

jujiao.png

jujiao.png

19950 ms

icon2.png

icon2.png

19896 ms

ft_2wei.jpg

ft_2wei.jpg

19896 ms

wljc.gif

wljc.gif

19895 ms

aw.jpg

aw.jpg

19896 ms

ind36.gif

ind36.gif

19896 ms

jb.gif

jb.gif

19896 ms

wmlogo.gif

wmlogo.gif

19896 ms

sprites.png

sprites.png

19896 ms

ga.js

ga.js

14 ms

icon_0.gif

icon_0.gif

497 ms

h.js

h.js

449 ms

__utm.gif

__utm.gif

19 ms

toss_11.gif

toss_11.gif

227 ms

MzI3ODYxMA==.js

MzI3ODYxMA==.js

484 ms

hm.gif

hm.gif

222 ms

navbarapp_api

navbarapp_api

1128 ms

helper-utils-moplus-monitor_cccb3ce.js

helper-utils-moplus-monitor_cccb3ce.js

2134 ms

ping_hotclick.js

ping_hotclick.js

227 ms

noavatar_small.gif

noavatar_small.gif

4968 ms

8d5085dc27d58086_256_180.jpg

8d5085dc27d58086_256_180.jpg

20114 ms

8e1e7ac9610a129f_256_180.jpg

8e1e7ac9610a129f_256_180.jpg

19696 ms

1b1f2310ec3f657e_256_180.jpg

1b1f2310ec3f657e_256_180.jpg

20277 ms

push-smartBar_25501fa.js

push-smartBar_25501fa.js

20235 ms

app-socialshare_b5c9f0e.js

app-socialshare_b5c9f0e.js

5814 ms

94a191f1f0819132_256_180.jpg

94a191f1f0819132_256_180.jpg

19858 ms

00b6ef4ae26a8d37_256_180.jpg

00b6ef4ae26a8d37_256_180.jpg

19461 ms

9519932a4deae54e_256_180.png

9519932a4deae54e_256_180.png

20438 ms

cf1fd45f777b9793_265_330.jpg

cf1fd45f777b9793_265_330.jpg

20020 ms

8090a0e71025f85a_265_330.jpg

8090a0e71025f85a_265_330.jpg

19603 ms

5b1d63fe20bbabfb_265_330.jpg

5b1d63fe20bbabfb_265_330.jpg

20472 ms

81f829acc3b68214_265_330.jpg

81f829acc3b68214_265_330.jpg

20163 ms

fd0620d044fcb3a0_265_330.jpg

fd0620d044fcb3a0_265_330.jpg

20072 ms

4f6b909edacfc0d1_265_330.jpg

4f6b909edacfc0d1_265_330.jpg

20056 ms

382b3f36d16f88cf_265_330.jpg

382b3f36d16f88cf_265_330.jpg

19747 ms

cda4c07f8e40a247_265_330.jpg

cda4c07f8e40a247_265_330.jpg

19657 ms

SEO Factors

pengke.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 Pengke.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 Pengke.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

pengke.com

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