72.3 sec in total
2.4 sec
69.4 sec
421 ms
Visit pcyule.com now to see the best up-to-date Pcyule content for China and also check out these interesting facts you probably never knew about pcyule.com
泡菜娱乐-07-16年记录
Visit pcyule.comWe analyzed Pcyule.com page load time and found that the first response time was 2.4 sec and then it took 69.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.
pcyule.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value3.2 s
71/100
25%
Value6.3 s
41/100
10%
Value110 ms
97/100
30%
Value0.405
25/100
15%
Value4.5 s
82/100
10%
2440 ms
4889 ms
939 ms
2965 ms
2635 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 75% of them (85 requests) were addressed to the original Pcyule.com, 4% (4 requests) were made to Tjs.sjs.sinajs.cn and 3% (3 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Pcyule.com.
Page size can be reduced by 408.4 kB (13%)
3.2 MB
2.7 MB
In fact, the total size of Pcyule.com main page is 3.2 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 139.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. This page needs HTML code to be minified as it can gain 49.7 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 139.1 kB or 86% of the original size.
Potential reduce by 127.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. Pcyule images are well optimized though.
Potential reduce by 115.3 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 115.3 kB or 57% of the original size.
Potential reduce by 26.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. Pcyule.com needs all CSS files to be minified and compressed as it can save up to 26.3 kB or 74% of the original size.
Number of requests can be reduced by 31 (28%)
110
79
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pcyule. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pcyule.com
2440 ms
www.pcyule.com
4889 ms
common.css
939 ms
index.css
2965 ms
bdsstyle.css
2635 ms
wb.js
20 ms
jquery.js
20451 ms
index.js
7695 ms
bdshare.js
15433 ms
z_stat.php
1592 ms
hm.js
3877 ms
taobaoke.jpg
14081 ms
is.png
20446 ms
wxewm.jpg
9892 ms
icon_r1_c3.jpg
972 ms
icon_r1_c2.jpg
2912 ms
pc_logo.jpg
18365 ms
btn.jpg
5989 ms
nav3.jpg
6483 ms
nav4.jpg
7005 ms
nav5.jpg
7498 ms
nav6.jpg
7990 ms
nav7.jpg
8482 ms
nav8.jpg
8974 ms
20160223050733491.jpg
20427 ms
20160223050718227.png
20428 ms
20160223050948478.jpg
20428 ms
20160223050709303.png
20428 ms
20160223053044842.jpg
20461 ms
20160223053022585.jpg
19519 ms
hm.gif
439 ms
20160223052948603.jpg
16096 ms
20160223052928736.jpg
19396 ms
20160223052832696.jpg
16397 ms
20151229040443224.jpg
20425 ms
20151207045224925.jpg
19933 ms
20151207045221920.jpg
15800 ms
20151207045217616.jpg
19947 ms
20151207044608327.jpg
16506 ms
20151204045643516.jpg
16331 ms
20151204045645433.jpg
20017 ms
20151204045641118.jpg
10833 ms
bdsstyle.css
1142 ms
20151207044942797.jpg
16390 ms
stat.htm
165 ms
core.php
706 ms
9.gif
1304 ms
z_stat.php
1953 ms
20151207044940876.jpg
20000 ms
20151207044938630.jpg
12743 ms
20151207044935853.jpg
10797 ms
20151207044933906.jpg
12394 ms
20151207044930247.jpg
17600 ms
20151207044928306.jpg
15651 ms
20151207044725925.jpg
19996 ms
20151204041528267.jpg
19997 ms
20151204041526168.jpg
19998 ms
20151204041525956.jpg
19998 ms
20151204041523936.jpg
20002 ms
20151204040820567.jpg
20000 ms
app.gif
901 ms
20151204040818277.jpg
19659 ms
stat.htm
161 ms
core.php
422 ms
20151204040811512.jpg
20000 ms
9.gif
698 ms
loading1.gif
4387 ms
bundle.js
3685 ms
20151204040808680.jpg
19552 ms
app.gif
454 ms
20151204040804893.jpg
19638 ms
20151204034917383.jpg
20045 ms
20151204024227110.jpg
19949 ms
20151204024224285.jpg
18662 ms
client.js
8 ms
iframeWidget.js
5 ms
aj_relationship.php
692 ms
followbutton.php
2607 ms
20151204024222434.jpg
18444 ms
20151204024219255.jpg
19998 ms
20151204024216876.jpg
19998 ms
20151204024208995.jpg
20233 ms
followButton.css
10 ms
sso.js
21 ms
followButton.js
16 ms
suda.js
17 ms
bg_flbtn.png
2 ms
b.gif
1415 ms
20151204024211963.jpg
20200 ms
20151204023737975.jpg
19602 ms
20151207045719245.jpg
20255 ms
20151207045718931.jpg
18944 ms
20151207045716585.jpg
19583 ms
20151207045715347.jpg
16378 ms
20151207045713265.jpg
20394 ms
20151207045711667.jpg
18373 ms
20151207045709168.jpg
19996 ms
20151207045707945.jpg
19280 ms
F.jpg
13874 ms
20160121054320957.jpg
14309 ms
20160121054301801.jpg
15185 ms
20160121054251559.jpg
15977 ms
20160121054242771.jpg
16498 ms
FS_10.jpg
17300 ms
20160122060516853.jpg
17376 ms
20160122060502784.jpg
19983 ms
20160122060435328.jpg
19082 ms
20160122060415306.jpg
19982 ms
20160122060208815.png
19982 ms
20160122060148169.png
19981 ms
20160122055908700.png
19998 ms
20160122055901298.jpg
19999 ms
20160122055854764.jpg
19483 ms
20160122055848458.png
19998 ms
pcyule.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pcyule.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pcyule.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pcyule.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Pcyule.com 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.
pcyule.com
Open Graph description is not detected on the main page of Pcyule. 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: