Tools & Wizards About Us
yihuale.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

yihuale.com

Yihuale-Jiangxi Yihuale Pen Industry Co, Ltd.

Page Load Speed

38.4 sec in total

First Response

777 ms

Resources Loaded

34.4 sec

Page Rendered

3.2 sec

yihuale.com screenshot

About Website

Welcome to yihuale.com homepage info - get ready to check Yihuale best content right away, or after learning these important things about yihuale.com

Brushing excellence since 1987 - Your one-stop destination for customized brushes tailored to your needs

Visit yihuale.com

Key Findings

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

Performance Metrics

yihuale.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value37.1 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.359

30/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

yihuale.com

777 ms

yihuale.com

1510 ms

swiper.min.css

470 ms

animate3.5.2.min.css

705 ms

yihualeguowai.pc.css

1224 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 85% of them (71 requests) were addressed to the original Yihuale.com, 7% (6 requests) were made to Youtube.com and 2% (2 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Yihuale.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 736.3 kB (9%)

Content Size

7.8 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yihuale.com main page is 7.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 51.6 kB

  • Original 57.4 kB
  • After minification 33.5 kB
  • After compression 5.8 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 23.9 kB, which is 42% 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 51.6 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 289.1 kB

  • Original 7.0 MB
  • After minification 6.7 MB

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. Yihuale images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 240.2 kB

  • Original 485.9 kB
  • After minification 449.3 kB
  • After compression 245.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 240.2 kB or 49% of the original size.

CSS Optimization

-66%

Potential reduce by 155.3 kB

  • Original 234.2 kB
  • After minification 217.6 kB
  • After compression 78.9 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. Yihuale.com needs all CSS files to be minified and compressed as it can save up to 155.3 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (30%)

Requests Now

61

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yihuale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yihuale.com

yihuale.com

777 ms

yihuale.com

yihuale.com

1510 ms

swiper.min.css

swiper.min.css

470 ms

animate3.5.2.min.css

animate3.5.2.min.css

705 ms

yihualeguowai.pc.css

yihualeguowai.pc.css

1224 ms

jquery.js

jquery.js

1182 ms

flexible.js

flexible.js

947 ms

js

js

62 ms

swiper.min.js

swiper.min.js

1206 ms

wow.min.js

wow.min.js

492 ms

layer.js

layer.js

707 ms

vaildform.js

vaildform.js

972 ms

script.pc.js

script.pc.js

943 ms

jquery.kxbdMarquee.js

jquery.kxbdMarquee.js

953 ms

fbevents.js

fbevents.js

140 ms

ie.png

ie.png

484 ms

browse-google.png

browse-google.png

482 ms

browse-for.png

browse-for.png

482 ms

browse-safari.png

browse-safari.png

483 ms

browse-ie.png

browse-ie.png

483 ms

6576717f508d2.png

6576717f508d2.png

925 ms

6573d4669370a.png

6573d4669370a.png

12602 ms

6573e029ab26a.png

6573e029ab26a.png

8961 ms

6577d1fc5ae81.jpg

6577d1fc5ae81.jpg

3099 ms

6577d35048050.jpg

6577d35048050.jpg

16279 ms

65780b8130433.jpg

65780b8130433.jpg

618 ms

65780a3a30e5e.jpg

65780a3a30e5e.jpg

8536 ms

65780c9ddfee5.jpg

65780c9ddfee5.jpg

1132 ms

659505e072c38.JPG

659505e072c38.JPG

3758 ms

6577f7d683fff.PNG

6577f7d683fff.PNG

3335 ms

6577f7d67ff5c.PNG

6577f7d67ff5c.PNG

3571 ms

6577f7d67bf11.PNG

6577f7d67bf11.PNG

4511 ms

6577f7d66a579.JPG

6577f7d66a579.JPG

6395 ms

6577f7d660a76.PNG

6577f7d660a76.PNG

5689 ms

6577f7d66559a.JPG

6577f7d66559a.JPG

6718 ms

6577d5c27dd4a.JPG

6577d5c27dd4a.JPG

13870 ms

6577d5ced955e.JPG

6577d5ced955e.JPG

8605 ms

6577d5ffe0cc2.JPG

6577d5ffe0cc2.JPG

12820 ms

6577d640de7b8.JPG

6577d640de7b8.JPG

11196 ms

6577d65035422.JPG

6577d65035422.JPG

12869 ms

6577d656bfb27.JPG

6577d656bfb27.JPG

13566 ms

6577d65ed130c.JPG

6577d65ed130c.JPG

20054 ms

65743c7e8d446.JPG

65743c7e8d446.JPG

20053 ms

65743c7aa8439.jpg

65743c7aa8439.jpg

14048 ms

65743c805908f.JPG

65743c805908f.JPG

14507 ms

65743c8969c86.JPG

65743c8969c86.JPG

19628 ms

6577d02e3cac1.jpg

6577d02e3cac1.jpg

15116 ms

6577d092be6dd.png

6577d092be6dd.png

20053 ms

65853c919fc15.png

65853c919fc15.png

20053 ms

G3OX_ALz1m4

G3OX_ALz1m4

186 ms

657805ee8955e.png

657805ee8955e.png

19635 ms

layer.css

layer.css

19693 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

39 ms

base.js

base.js

87 ms

ad_status.js

ad_status.js

162 ms

iconfont.woff

iconfont.woff

19428 ms

65864b50d1b8c.png

65864b50d1b8c.png

19577 ms

657800041040e.png

657800041040e.png

19576 ms

659507c8af307.png

659507c8af307.png

19575 ms

RaBoRo_xCymm2dlJSrwnNMYK_3vPxGMh2bfo3dfd9HE.js

RaBoRo_xCymm2dlJSrwnNMYK_3vPxGMh2bfo3dfd9HE.js

120 ms

embed.js

embed.js

45 ms

6594d31ac6926.png

6594d31ac6926.png

20449 ms

6593ccd8d1c53.png

6593ccd8d1c53.png

20439 ms

id

id

14 ms

Create

Create

141 ms

6593d41b805b0.png

6593d41b805b0.png

20128 ms

GenerateIT

GenerateIT

15 ms

6594ce1e747ba.png

6594ce1e747ba.png

19925 ms

log_event

log_event

18 ms

6594bef2c2f22.png

6594bef2c2f22.png

19956 ms

6594f99e99682.png

6594f99e99682.png

19720 ms

6595193b99bb9.png

6595193b99bb9.png

20484 ms

6578041eee655.jpg

6578041eee655.jpg

20297 ms

656d3681cc516.jpg

656d3681cc516.jpg

19524 ms

657806cf650f6.png

657806cf650f6.png

20372 ms

657807234d3a3.png

657807234d3a3.png

18839 ms

6578077008234.png

6578077008234.png

19457 ms

65840226659eb.JPG

65840226659eb.JPG

17902 ms

6583d7492ce3f.PNG

6583d7492ce3f.PNG

20447 ms

6583a7c9ae55f.JPEG

6583a7c9ae55f.JPEG

20096 ms

6583a8147a721.png

6583a8147a721.png

19857 ms

656d67a53905d.jpg

656d67a53905d.jpg

15772 ms

656d48a3cffe6.jpg

656d48a3cffe6.jpg

15407 ms

Accessibility Review

yihuale.com accessibility score

77

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

yihuale.com 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

yihuale.com SEO score

75

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

yihuale.com

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