23.2 sec in total
796 ms
20.7 sec
1.7 sec
Click here to check amazing Zyan content for Pakistan. Otherwise, check out these important facts you probably never knew about zyan.cc
Web系统架构与底层研发
Visit zyan.ccWe analyzed Zyan.cc page load time and found that the first response time was 796 ms and then it took 22.4 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
zyan.cc performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value1.6 s
99/100
25%
Value2.8 s
96/100
10%
Value10 ms
100/100
30%
Value0.002
100/100
15%
Value1.8 s
100/100
10%
796 ms
332 ms
347 ms
351 ms
381 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 56% of them (46 requests) were addressed to the original Zyan.cc, 16% (13 requests) were made to Cdn.phpts.cn and 4% (3 requests) were made to Pic1.zyan.cc. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Pic3.s135.com.
Page size can be reduced by 666.1 kB (23%)
3.0 MB
2.3 MB
In fact, the total size of Zyan.cc main page is 3.0 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. 35% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 91.0 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 91.0 kB or 77% of the original size.
Potential reduce by 440.2 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. Obviously, Zyan needs image optimization as it can save up to 440.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 132.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 132.4 kB or 59% of the original size.
Potential reduce by 2.4 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. Zyan.cc needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 39% of the original size.
Number of requests can be reduced by 46 (60%)
77
31
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zyan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
zyan.cc
796 ms
styles.css
332 ms
5.1.css
347 ms
common.js
351 ms
jslang.js
381 ms
ajax.js
399 ms
swfobject.js
382 ms
SyntaxHighlighter.css
492 ms
shCore.js
367 ms
shBrushCSharp.js
367 ms
shBrushPhp.js
368 ms
shBrushJScript.js
367 ms
shBrushJava.js
393 ms
shBrushVb.js
446 ms
shBrushSql.js
481 ms
shBrushXml.js
489 ms
shBrushCss.js
518 ms
shBrushCpp.js
550 ms
shBrushDelphi.js
588 ms
shBrushPython.js
610 ms
shBrushRuby.js
653 ms
adsbygoogle.js
170 ms
phpts10601.png
5255 ms
tree_linemiddle.gif
782 ms
diannao.gif
773 ms
xinqing.gif
859 ms
desk.gif
762 ms
notebook.png
772 ms
zaishang.gif
634 ms
nalai.gif
706 ms
soft.gif
816 ms
mainmenu.png
1659 ms
phpts10502.jpg
5569 ms
phpts106php.png
1705 ms
phpts106phpext.png
2374 ms
phpts106mysql.png
3316 ms
phpts104heidisql.png
4838 ms
phpts106memcached.png
4161 ms
phpts10506.jpg
4231 ms
phpts10507.jpg
5890 ms
mongodbadmin-1.png
4559 ms
phpts106console.png
6116 ms
phptsbnew.jpg
5361 ms
tree_linebottom.gif
772 ms
mysqlcft.png
827 ms
page_script.gif
783 ms
down.gif
808 ms
nginx.gif
773 ms
phpcws.png
840 ms
doubleleft.gif
485 ms
singleright.gif
544 ms
doubleright.gif
544 ms
starred.gif
588 ms
blank.gif
573 ms
readmore.gif
626 ms
unstarred.gif
637 ms
cu1.jpg
918 ms
cu2.jpg
1065 ms
1.jpg
1135 ms
2.jpg
1130 ms
3.jpg
1056 ms
touch-callout.jpg
1001 ms
rss.png
1091 ms
f5.gif
864 ms
scuec.gif
19612 ms
sina_vnet_podcast.jpg
19612 ms
kingsoft.gif
19612 ms
apmserv_logo.jpg
19613 ms
nginx_book.jpg
896 ms
logo.jpg
1112 ms
menu_a.gif
1145 ms
announce_bg.gif
1170 ms
textbox_top.gif
1179 ms
textbox_bg.gif
1245 ms
panel_header.gif
1213 ms
bg.gif
1287 ms
list.gif
1317 ms
logo-kingsoft.gif
1285 ms
logo-sina.jpg
1288 ms
zhangyan.gif
1312 ms
hm.js
1007 ms
hm.gif
328 ms
zyan.cc accessibility score
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.
zyan.cc best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
zyan.cc 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
Tap targets are not sized appropriately
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zyan.cc 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 Zyan.cc 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.
zyan.cc
Open Graph description is not detected on the main page of Zyan. 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: