Tools & Wizards About Us
yizong.org screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

yizong.org

Home

Page Load Speed

2.9 sec in total

First Response

401 ms

Resources Loaded

2.3 sec

Page Rendered

240 ms

yizong.org screenshot

About Website

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

Luo Dexiu website homepage

Visit yizong.org

Key Findings

We analyzed Yizong.org page load time and found that the first response time was 401 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

yizong.org performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

401 ms

style.css

235 ms

style.css

237 ms

ic_rounded_module.css

239 ms

slideshow.css

241 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 84% of them (46 requests) were addressed to the original Yizong.org, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (744 ms) belongs to the original domain Yizong.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (61%)

Content Size

1.7 MB

After Optimization

654.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yizong.org main page is 1.7 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. 50% of websites need less resources to load. Images take 813.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.2 kB

  • Original 49.6 kB
  • After minification 45.3 kB
  • After compression 10.4 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 39.2 kB or 79% of the original size.

Image Optimization

-44%

Potential reduce by 358.1 kB

  • Original 813.7 kB
  • After minification 455.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, Yizong needs image optimization as it can save up to 358.1 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 352.8 kB

  • Original 499.6 kB
  • After minification 487.8 kB
  • After compression 146.8 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 352.8 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 265.2 kB

  • Original 306.8 kB
  • After minification 240.9 kB
  • After compression 41.6 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. Yizong.org needs all CSS files to be minified and compressed as it can save up to 265.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (63%)

Requests Now

46

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yizong. 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 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

401 ms

style.css

style.css

235 ms

style.css

style.css

237 ms

ic_rounded_module.css

ic_rounded_module.css

239 ms

slideshow.css

slideshow.css

241 ms

template.css

template.css

240 ms

jquery.min.js

jquery.min.js

409 ms

jquery-noconflict.js

jquery-noconflict.js

312 ms

jquery-migrate.min.js

jquery-migrate.min.js

316 ms

caption.js

caption.js

318 ms

mootools-core.js

mootools-core.js

517 ms

core.js

core.js

317 ms

mootools-more.js

mootools-more.js

744 ms

bootstrap.min.js

bootstrap.min.js

395 ms

jQuery.highlightToday.min.js

jQuery.highlightToday.min.js

395 ms

system.css

system.css

395 ms

bootstrap.css

bootstrap.css

635 ms

typo.css

typo.css

474 ms

jstuff.css

jstuff.css

475 ms

animate.css

animate.css

569 ms

font-awesome.css

font-awesome.css

554 ms

nexus.css

nexus.css

635 ms

responsive.css

responsive.css

594 ms

css

css

19 ms

css

css

37 ms

css

css

39 ms

modernizr.js

modernizr.js

23 ms

jquery.visible.js

jquery.visible.js

560 ms

jquery.sticky.js

jquery.sticky.js

576 ms

responsive-nav.js

responsive-nav.js

599 ms

jquery.slides.min.js

jquery.slides.min.js

636 ms

system.css

system.css

80 ms

cks_memorial_hall.png

cks_memorial_hall.png

85 ms

logo-transp.PNG

logo-transp.PNG

334 ms

fr.gif

fr.gif

83 ms

zh_tw.gif

zh_tw.gif

84 ms

menu_arrow.png

menu_arrow.png

84 ms

prev.png

prev.png

83 ms

next.png

next.png

156 ms

DSC_2028-1-border.jpg

DSC_2028-1-border.jpg

238 ms

DSC_2109-1-border.jpg

DSC_2109-1-border.jpg

238 ms

DSC_2194-1-border.jpg

DSC_2194-1-border.jpg

238 ms

heaven_gua.png

heaven_gua.png

160 ms

earth_resized.jpg

earth_resized.jpg

234 ms

luo_resized.jpg

luo_resized.jpg

239 ms

temple_resized.jpg

temple_resized.jpg

312 ms

logo_resized.jpg

logo_resized.jpg

316 ms

jizaRExUiTo99u79D0KEwA.ttf

jizaRExUiTo99u79D0KEwA.ttf

14 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

24 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

24 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

301 ms

IcoMoon.woff

IcoMoon.woff

289 ms

iCicons.woff

iCicons.woff

292 ms

Accessibility Review

yizong.org accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

yizong.org best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yizong.org SEO score

99

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yizong.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yizong.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

yizong.org

Open Graph description is not detected on the main page of Yizong. 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: