46.5 sec in total
763 ms
42.7 sec
3 sec
Visit nginx.cn now to see the best up-to-date Nginx content for China and also check out these interesting facts you probably never knew about nginx.cn
分享nginx中文资料的网站,从nginx入门安装到配置到优化,如nginx的rewrite、反向代理、负载均衡、缓存等配置,也会看到我业余时间研究PHP、Linux、数据库、Android、iOS开发遇到的有趣问题和经验总结。
Visit nginx.cnWe analyzed Nginx.cn page load time and found that the first response time was 763 ms and then it took 45.7 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
nginx.cn performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.2 s
71/100
25%
Value9.8 s
10/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value4.3 s
84/100
10%
763 ms
1963 ms
20103 ms
233 ms
234 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 46% of them (21 requests) were addressed to the original Nginx.cn, 11% (5 requests) were made to Uml.org.cn and 9% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Libs.baidu.com.
Page size can be reduced by 217.7 kB (36%)
602.0 kB
384.4 kB
In fact, the total size of Nginx.cn main page is 602.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. 35% of websites need less resources to load. Images take 329.1 kB which makes up the majority of the site volume.
Potential reduce by 58.7 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 58.7 kB or 69% of the original size.
Potential reduce by 61.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. Obviously, Nginx needs image optimization as it can save up to 61.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34.2 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 34.2 kB or 31% of the original size.
Potential reduce by 63.1 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. Nginx.cn needs all CSS files to be minified and compressed as it can save up to 63.1 kB or 81% of the original size.
Number of requests can be reduced by 16 (42%)
38
22
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nginx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
nginx.cn
763 ms
www.nginx.cn
1963 ms
jquery.js
20103 ms
chinese.css
233 ms
base.js
234 ms
menu.js
242 ms
embed.js
801 ms
adsbygoogle.js
91 ms
copy.js
117 ms
wp-embed.min.js
219 ms
style.css
208 ms
wp-emoji-release.min.js
145 ms
hm.js
1252 ms
2012110651.jpg
5643 ms
0_1280551287S777.gif
1210 ms
2012110652.jpg
3279 ms
2012110653.jpg
11246 ms
2012110654.jpg
19745 ms
2012110655.jpg
19744 ms
bg.jpg
122 ms
light.gif
215 ms
header.jpg
213 ms
menu.gif
123 ms
sidesep.gif
142 ms
main_shadow.gif
214 ms
icons.gif
215 ms
blockquote.gif
213 ms
gtest.png
230 ms
sidebar_shadow.gif
239 ms
0_1280550787I2K8.gif
1292 ms
0_128055089469yL.gif
1197 ms
embed.default.css
113 ms
embed.compat.js
803 ms
ca-pub-8728612882429404.js
660 ms
zrt_lookup.html
737 ms
show_ads_impl.js
652 ms
widgetsep.png
651 ms
footer.jpg
653 ms
ads
328 ms
counts.json
1175 ms
osd.js
23 ms
ads
278 ms
0_128055089469yL.gif
5087 ms
0_1280551287S777.gif
4306 ms
hm.gif
468 ms
0_1280550787I2K8.gif
4862 ms
nginx.cn accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
nginx.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
nginx.cn SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nginx.cn 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 Nginx.cn 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.
nginx.cn
Open Graph description is not detected on the main page of Nginx. 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: