Tools & Wizards About Us
chrenai.org screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

chrenai.org

北京市仁爱慈善基金会 -

Page Load Speed

24.6 sec in total

First Response

683 ms

Resources Loaded

23.7 sec

Page Rendered

239 ms

chrenai.org screenshot

About Website

Welcome to chrenai.org homepage info - get ready to check Chrenai best content right away, or after learning these important things about chrenai.org

北京市仁爱慈善基金会

Visit chrenai.org

Key Findings

We analyzed Chrenai.org page load time and found that the first response time was 683 ms and then it took 23.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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

chrenai.org performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value32.3 s

0/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

www.chrenai.com

683 ms

style_1_common.css

447 ms

style_1_portal_portalcp.css

427 ms

reset.css

429 ms

swiper-3.4.2.min.css

1087 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that all of those requests were addressed to Chrenai.org and no external sources were called. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Chrenai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.2 kB (33%)

Content Size

398.5 kB

After Optimization

266.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Chrenai.org main page is 398.5 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 338.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.6 kB

  • Original 23.2 kB
  • After minification 16.7 kB
  • After compression 4.5 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 6.5 kB, which is 28% 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 80% of the original size.

Image Optimization

-32%

Potential reduce by 109.6 kB

  • Original 338.6 kB
  • After minification 229.0 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 109.6 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-11%

Potential reduce by 4.0 kB

  • Original 36.8 kB
  • After minification 36.8 kB
  • After compression 32.8 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.org needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 31 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 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.chrenai.com

www.chrenai.com

683 ms

style_1_common.css

style_1_common.css

447 ms

style_1_portal_portalcp.css

style_1_portal_portalcp.css

427 ms

reset.css

reset.css

429 ms

swiper-3.4.2.min.css

swiper-3.4.2.min.css

1087 ms

style_pc.css

style_pc.css

433 ms

style_pc_2022.css

style_pc_2022.css

434 ms

dajishi.css

dajishi.css

641 ms

common.js

common.js

857 ms

portal.js

portal.js

648 ms

sea.js

sea.js

649 ms

jquery.min.js

jquery.min.js

880 ms

logo.png

logo.png

224 ms

icons.png

icons.png

216 ms

3.fw.png

3.fw.png

433 ms

2.fw.png

2.fw.png

425 ms

141458yna6yjyw6ziy2e6i.jpg

141458yna6yjyw6ziy2e6i.jpg

7333 ms

141746oxqzm3o3x4fk3m31.jpg

141746oxqzm3o3x4fk3m31.jpg

12296 ms

141249mdcif12vviuf4jg6.jpg

141249mdcif12vviuf4jg6.jpg

13314 ms

111528bwqoubf9vwr39x0x.png

111528bwqoubf9vwr39x0x.png

14568 ms

144020yy2af2bsillblcyq.png

144020yy2af2bsillblcyq.png

19887 ms

152314a9l3eofjrjezqie9.jpg

152314a9l3eofjrjezqie9.jpg

7843 ms

160701au6m4567c5p5osz6.jpg

160701au6m4567c5p5osz6.jpg

8193 ms

xia-1.fw.png

xia-1.fw.png

13080 ms

xia-2.fw.png

xia-2.fw.png

19891 ms

xia-3.fw.png

xia-3.fw.png

19891 ms

xia-4.fw.png

xia-4.fw.png

13511 ms

xia-5.fw.png

xia-5.fw.png

13741 ms

xia-6.fw.png

xia-6.fw.png

16376 ms

jianbian.fw.png

jianbian.fw.png

14977 ms

responsive.js

responsive.js

14725 ms

nav.js

nav.js

14948 ms

myswiper.js

myswiper.js

15160 ms

swiper.js

swiper.js

674 ms

style_mobile_2022.css

style_mobile_2022.css

1301 ms

dajishi_m.css

dajishi_m.css

225 ms

Accessibility Review

chrenai.org accessibility score

43

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

chrenai.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

chrenai.org SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chrenai.org 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.org 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.

Social Sharing Optimization

chrenai.org

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: