43.6 sec in total
1.7 sec
41.4 sec
520 ms
Welcome to chrenai.com homepage info - get ready to check Chrenai best content right away, or after learning these important things about chrenai.com
Visit chrenai.comWe analyzed Chrenai.com page load time and found that the first response time was 1.7 sec and then it took 41.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 26 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
chrenai.com performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value6.8 s
7/100
25%
Value18.8 s
0/100
10%
Value190 ms
90/100
30%
Value0
100/100
15%
Value8.5 s
38/100
10%
1659 ms
1098 ms
735 ms
85 ms
2232 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 43% of them (37 requests) were addressed to the original Chrenai.com, 10% (9 requests) were made to Img.t.sinajs.cn and 9% (8 requests) were made to Ww2.sinaimg.cn. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Chrenai.com.
Page size can be reduced by 332.0 kB (46%)
718.9 kB
386.9 kB
In fact, the total size of Chrenai.com main page is 718.9 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. 40% of websites need less resources to load. Javascripts take 354.8 kB which makes up the majority of the site volume.
Potential reduce by 18.6 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 3.8 kB, which is 14% 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 18.6 kB or 71% of the original size.
Potential reduce by 27.5 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, Chrenai needs image optimization as it can save up to 27.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 219.6 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 219.6 kB or 62% of the original size.
Potential reduce by 66.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. Chrenai.com needs all CSS files to be minified and compressed as it can save up to 66.3 kB or 82% of the original size.
Number of requests can be reduced by 17 (29%)
59
42
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chrenai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
chrenai.com
1659 ms
index.css
1098 ms
index.js
735 ms
wb.js
85 ms
rili.js
2232 ms
jquery.min.js
20122 ms
jquery.yx_rotaion.js
2917 ms
logo.png
15478 ms
sgj.jpg
6429 ms
43-1603151352540-L.jpg
18188 ms
43-1603151351220-L.jpg
20010 ms
43-1603151350110-L.jpg
20011 ms
43-1603151344170-L.jpg
20012 ms
43-1603151340590-L.jpg
20014 ms
14584513266223.jpg
20015 ms
4-160112204R70-L.jpg
20016 ms
2-16040FZZ90-L.jpg
20016 ms
4-16040QK5280-L.jpg
20017 ms
4-1604042220250-L.jpg
20016 ms
4-160305220K30-L.jpg
20017 ms
2-1505051551120-L.jpg
20016 ms
1460081460817-lp.jpg
20016 ms
fghj.jpg
20016 ms
dsfhf.jpg
20016 ms
wz.jpg
20015 ms
01.jpg
20016 ms
ma01.jpg
20015 ms
hjadf.jpg
20015 ms
ma02.jpg
20015 ms
dfhj.jpg
20015 ms
sdgjh01.jpg
20015 ms
sdgjh02.jpg
20014 ms
dgfg.jpg
19883 ms
sag.jpg
19884 ms
index.php
4072 ms
index.php
758 ms
dfh.jpg
19991 ms
sp1.jpg
6938 ms
sdfg.jpg
13423 ms
dhks.png
5946 ms
loading1.gif
58 ms
bundle.js
56 ms
client.js
10 ms
iframeWidget.js
43 ms
aj_relationship.php
1920 ms
jquery.js
736 ms
quickfollownewstyle5.css
465 ms
follow_quick_05.js
491 ms
weiboShow.css
167 ms
skin_default.css
172 ms
gaea_1_19.js
136 ms
quickfollowbgnew.gif
237 ms
1
110 ms
63784d15jw1f2ow30wpsoj20zk0qo7bs.jpg
712 ms
icon_user.png
52 ms
btns_bg.png
52 ms
icon_follow.png
68 ms
63784d15jw1f2nz1hd99oj20zd0qodo6.jpg
505 ms
63784d15jw1f2cr1onnpoj20kf0k6787.jpg
243 ms
63784d15jw1f2nyvtbetmj20zk0qogu1.jpg
566 ms
63784d15jw1f2covf4o2jj21kw11xkc1.jpg
203 ms
63784d15jw1f2infca6quj21kw11xdqm.jpg
271 ms
63784d15jw1f2dwsnzncoj21kw11tws1.jpg
26 ms
followbutton.php
5674 ms
63784d15jw1f2cmbu6xp2j21kw11xh5x.jpg
73 ms
63784d15jw1f2clf83ev6j21kw16oe5g.jpg
72 ms
63784d15jw1f24f0ocxm0j21kw16o1kx.jpg
66 ms
suda.js
22 ms
63784d15jw1f1uuc4uo9zj20zk0qon4t.jpg
52 ms
63784d15jw1f21gaq5f38j21kw166hdt.jpg
55 ms
63784d15jw1f1vglbj2c8j20zk0qe77b.jpg
54 ms
63784d15jw1f1uup1wmzij20zk0qodnm.jpg
45 ms
63784d15jw1f1uuibv2gcj20zk0qotgr.jpg
48 ms
63784d15jw1f28uw5lpowj20zd0qoakl.jpg
49 ms
63784d15jw1f28ulvg6b6j20zk0qoakm.jpg
56 ms
63784d15jw1f24e9p3lsyj20zk0qoqbu.jpg
57 ms
63784d15jw1f1v1nc75eqj20zk0qoqf7.jpg
54 ms
63784d15jw1f1uvw7g8hij20zk0qo7gg.jpg
51 ms
show.js
15 ms
bg_trans.png
24 ms
icon_tips.png
19 ms
tmp.gif
932 ms
followButton.css
6 ms
sso.js
11 ms
followButton.js
16 ms
bg_flbtn.png
39 ms
b.gif
441 ms
chrenai.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.
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
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
Links do not have a discernible name
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.
chrenai.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
chrenai.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses plugins
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chrenai.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 Chrenai.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.
chrenai.com
Open Graph description is not detected on the main page of Chrenai. 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: