3.1 sec in total
126 ms
2.2 sec
797 ms
Click here to check amazing 72 No content. Otherwise, check out these important facts you probably never knew about 72no.com
Visit 72no.comWe analyzed 72no.com page load time and found that the first response time was 126 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
72no.com performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value2.2 s
95/100
25%
Value3.6 s
87/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.2 s
99/100
10%
126 ms
109 ms
45 ms
86 ms
46 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 95% of them (77 requests) were addressed to the original 72no.com, 1% (1 request) were made to Tui1999.com and 1% (1 request) were made to S11.cnzz.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Tui1999.com.
Page size can be reduced by 103.7 kB (11%)
940.1 kB
836.4 kB
In fact, the total size of 72no.com main page is 940.1 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. 50% of websites need less resources to load. Images take 835.0 kB which makes up the majority of the site volume.
Potential reduce by 59.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 59.0 kB or 83% of the original size.
Potential reduce by 19.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. 72 No images are well optimized though.
Potential reduce by 7.9 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 7.9 kB or 64% of the original size.
Potential reduce by 17.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. 72no.com needs all CSS files to be minified and compressed as it can save up to 17.3 kB or 79% of the original size.
Number of requests can be reduced by 13 (16%)
80
67
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 72 No. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
72no.com
126 ms
style1.css
109 ms
caonimei.js
45 ms
logo.gif
86 ms
a74ecc4cjw1e18mb1rm7lg.gif
46 ms
a74eed94jw1e18mbormz3g.gif
48 ms
duilian.js
23 ms
testj.js
31 ms
1202 ms
z_stat.php
1187 ms
a74ecc4cjw1e18mgoyfqug.gif
86 ms
a74eed94jw1e18mh38njqg.gif
87 ms
a74eed94jw1e18mjsfvnng.gif
89 ms
a74e55b4jw1e18mihaquug.gif
91 ms
a74e55b4jw1e18mhfumsng.gif
90 ms
zha2017.gif
110 ms
a74e55b4jw1e18mkals5tg.gif
91 ms
a74eed94jw1e18mkx8na2g.gif
94 ms
a74e55b4jw1e18ml8mhdug.gif
92 ms
2014617555065769.jpg
93 ms
20145286384092125.jpg
94 ms
2014628195519701.jpg
94 ms
201462863731954.jpg
98 ms
201462835269590.jpg
97 ms
201462803846205.jpg
96 ms
201462758371334.jpg
98 ms
2014627544284087.jpg
100 ms
a74ecc4cjw1e18mln0z89g.gif
103 ms
201631920162878172.jpg
100 ms
201631919581362026.jpg
109 ms
201631912472036873.jpg
105 ms
201631912414736012.jpg
106 ms
20163191236811338.jpg
107 ms
201631912143999285.jpg
108 ms
20163169125051890.jpg
122 ms
2016316935949766.jpg
122 ms
2016316913734685.jpg
126 ms
20163168573666110.jpg
128 ms
20163142094663319.jpg
128 ms
20163142041775233.jpg
130 ms
20163141958222624.jpg
146 ms
2016386351186700.jpg
143 ms
2016386294769750.jpg
157 ms
20163177574634600.jpg
146 ms
20163177535370266.jpg
158 ms
20163177504393851.jpg
83 ms
20163176335293395.jpg
85 ms
20163176292620091.jpg
88 ms
201631911431149237.jpg
85 ms
20163196312958603.jpg
83 ms
20163187225388057.jpg
84 ms
20163187123262036.jpg
84 ms
20163186461461463.jpg
98 ms
201631920103418244.jpg
100 ms
20163197465585133.jpg
99 ms
20163196381568852.jpg
99 ms
20163181203755466.jpg
102 ms
20163178412617386.jpg
101 ms
201622920263276178.jpg
114 ms
201622920101564360.jpg
115 ms
2016229661137352.jpg
115 ms
20162295253897614.jpg
135 ms
2016225835540422.jpg
116 ms
2015125691767073.jpg
115 ms
2015112619593133069.jpg
125 ms
2015112619555537107.jpg
126 ms
2015112619494598991.jpg
127 ms
20151126194894595.jpg
131 ms
20163106403264972.jpg
157 ms
20163106262178290.jpg
143 ms
20163620134254289.jpg
151 ms
20163519572835244.jpg
152 ms
20163319355155971.jpg
127 ms
201631919225825424.jpg
131 ms
20163191918616073.jpg
142 ms
20163191910233808.jpg
148 ms
201631912224333579.jpg
138 ms
201631912172763233.jpg
136 ms
zha2017-1.gif
138 ms
stat.htm
251 ms
core.php
762 ms
72no.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.
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.
72no.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
72no.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 72no.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 72no.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.
72no.com
Open Graph description is not detected on the main page of 72 No. 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: