121.6 sec in total
15.4 sec
105.3 sec
866 ms
Visit p2pwe.com now to see the best up-to-date P 2 Pwe content for China and also check out these interesting facts you probably never knew about p2pwe.com
首页
Visit p2pwe.comWe analyzed P2pwe.com page load time and found that the first response time was 15.4 sec and then it took 106.2 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 22 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
p2pwe.com performance score
15415 ms
7505 ms
997 ms
5518 ms
1172 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 67% of them (86 requests) were addressed to the original P2pwe.com, 3% (4 requests) were made to Img.alicdn.com and 3% (4 requests) were made to Dspcm.brand.sogou.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain P2pwe.com.
Page size can be reduced by 130.4 kB (31%)
416.8 kB
286.4 kB
In fact, the total size of P2pwe.com main page is 416.8 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. 35% of websites need less resources to load. Images take 228.8 kB which makes up the majority of the site volume.
Potential reduce by 50.9 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 50.9 kB or 76% of the original size.
Potential reduce by 14.7 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. P 2 Pwe images are well optimized though.
Potential reduce by 33.7 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 33.7 kB or 42% of the original size.
Potential reduce by 31.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. P2pwe.com needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 78% of the original size.
Number of requests can be reduced by 28 (27%)
102
74
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P 2 Pwe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.p2pwe.com
15415 ms
style_14_common.css
7505 ms
style_14_portal_index.css
997 ms
common.js
5518 ms
portal.js
1172 ms
font-awesome.min.css
4952 ms
jquery.min.js
19700 ms
jquery.slide.js
4660 ms
s.php
6149 ms
c.js
733 ms
plugin.php
3174 ms
discuz_tips.js
729 ms
154019lwzjg7j4sm77j097.gif
18858 ms
logo.png
2723 ms
arrow_down.gif
770 ms
icon.png
5762 ms
171339dd96q7ubo7bqrcz7.gif
4792 ms
112019jkjd24hh3hudhmkj.jpg
7612 ms
204339ctz976r6b60wu9ej.jpg
4127 ms
212103f029v5w0p2vn7o2m.jpg
4380 ms
205130jnp5jloo2rdd5zmm.jpeg
6817 ms
205816qj7jz5f7lqtlzx16.jpg
5986 ms
30cda6920270bb1e3677e53ca527e964.jpg
7521 ms
f6ea7e6d7a9fc03c74d6d7231e6216fd.jpg
7000 ms
2850504ebaf3c3234a6880007996887f.jpg
9632 ms
519feabc80a7561a1002a41ca7a150ed.jpg
7869 ms
35232705786d72dce8383df394f79876.jpg
10180 ms
04dc02ec220a84ddedcc3c1199c2a43a.jpg
8534 ms
578fb59fa5985fba1590b31b2be5b1f0.jpg
8637 ms
36832ae2d4eb96d2c4c62476852e7b22.jpg
12659 ms
5e6cda38773d94e11769b28d3ac8a0ef.jpg
9333 ms
7a03dfcc5bed51967c66fb9601475bf1.jpg
16103 ms
b378b440c31446ea11327096f80de5b9.jpg
14556 ms
30e2bb4a8241df7d50665bd33320032c.jpg
12549 ms
3bee52c5f38766988188e5e52b72a64e.jpg
16086 ms
7c6f972c8532efebfb65857c8ca390d0.jpg
19978 ms
8eabae9100f551f25343a0a664b5650b.jpg
19754 ms
86b0031f5846bc538897d5706da130e0.jpg
19977 ms
38afcee5c1625971dae44f71cf4803ca.jpg
17621 ms
278c54a2183d479d35e76ed6b68ea0c9.jpg
19555 ms
759bfcf2e1864483c76f63c8e8a28f39.jpg
19977 ms
00e028b7f86447f7195d1e563a3b9d87.jpg
19978 ms
252f6fec522531e278d1c04a2e43ebae.jpg
19979 ms
8647701f4537bb0f26dd9a451b08c948.jpg
19979 ms
bd1f1ff2e8cc6d420e3386a03e39653f.jpg
19970 ms
ask
2091 ms
common_extra.js
20216 ms
ct
7272 ms
lm.jpg
1139 ms
ex
1506 ms
hm.js
874 ms
stat.php
2707 ms
fontawesome-webfont.woff
20263 ms
hm.gif
275 ms
qi
736 ms
tanxssp.js
381 ms
t.gif
782 ms
t.gif
1797 ms
b334031d5388e3b0cedcf6529b9566c7.jpg
17358 ms
ex
993 ms
f8b627e882578c910f81385d00d35eb1.jpg
17083 ms
ecc0533466f9ad4542bb14f9034a32ab.jpg
20194 ms
qqcm
382 ms
pixel
740 ms
stat.htm
236 ms
core.php
836 ms
acbeacon2.html
413 ms
spf
1874 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
195 ms
T1mf0CFpdbXXbMsGbX.html
415 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
194 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
193 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
195 ms
t.gif
988 ms
tns.simba.taobao.com
20371 ms
7e805c9fbd890bfda770b7c97525ed97.jpg
20226 ms
9.gif
933 ms
pic.gif
779 ms
pixel
361 ms
b9271844d493096536794dc39a91b525.jpg
18906 ms
app.gif
872 ms
app.gif
788 ms
fdedcadac6a3fbe29f4ba4415e3fadcd.jpg
20169 ms
9f952e11f0496d8286905b92fdbc4cc7.jpg
19419 ms
um.js
369 ms
img
947 ms
2eb066b15a573028a31be0963eddca9d.jpg
16703 ms
da415edf152ec28529952c8a307eb834.jpg
18077 ms
85778117d90c19aab7bd52d9202eb6bc.jpg
19823 ms
um.json
1683 ms
getDeviceInfo
2493 ms
65898e16287b8f8e0e30ee0f3a3f273f.jpg
20449 ms
486614997049cab6e13862ddd2f62df1.jpg
20346 ms
4b7b33b8f2c9b5b70d589eb834deb66d.jpg
19649 ms
sogou_icon_wz_1.png
3355 ms
fc.js
453 ms
getDeviceInfo
7749 ms
98eb714b5dd612c6de7d9ee3a5b2965b.jpg
18149 ms
75d745e6aa5e7339473f63c21cccf894.jpg
19803 ms
93_avatar_small.jpg
16844 ms
54_avatar_middle.jpg
16556 ms
a07aa930bf5f54902b73f73f0a268bb4.jpg
19518 ms
64505f8b514fe76d5f8b47469ba086b0.jpg
20321 ms
noavatar_middle.gif
18275 ms
31469258c52c78e2a35e37c9a08b34c0.jpg
18109 ms
1c1e9c69f294cd9ecf2268375f34d4b3.jpg
15116 ms
e34a6df26036cfab03a0bae2b9eaf7b4.jpg
16931 ms
83479cdb95a154422daa802268ebbbda.jpg
15246 ms
27ecf6778bfcbce86181f55845d4d28d.jpg
14667 ms
dac813417cb1f989dcce01e7c6fd29c3.jpg
17456 ms
18a62071ae1bc1d4b88c3fdb2d0f7926.jpg
20223 ms
qa_wen.png
13922 ms
gs.png
18022 ms
anva.png
14751 ms
nav_bg.jpg
14617 ms
nav_line.png
16401 ms
focus.png
15766 ms
slider-arrow.png
16613 ms
focus02.png
17406 ms
dot.gif
15792 ms
weikan_next.png
16190 ms
weikan_prev.png
16779 ms
fontawesome-webfont.ttf
19759 ms
logo_bottom.png
15422 ms
scrolltop.png
13803 ms
tanxclick.js
77 ms
T1qmFdFDFmXXb4F32o-80-60.gif
339 ms
fontawesome-webfont.svg
19893 ms
hm.gif
977 ms
p2pwe.com SEO score
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise P2pwe.com 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that P2pwe.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.
p2pwe.com
Open Graph description is not detected on the main page of P 2 Pwe. 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: