Tools & Wizards About Us
holyart.en.alibaba.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

holyart.en.alibaba.com

Alibaba Manufacturer Directory - Suppliers, Manufacturers, Exporters & Importers

Page Load Speed

2.4 sec in total

First Response

60 ms

Resources Loaded

2.1 sec

Page Rendered

302 ms

holyart.en.alibaba.com screenshot

About Website

Visit holyart.en.alibaba.com now to see the best up-to-date Holyart En Alibaba content for China and also check out these interesting facts you probably never knew about holyart.en.alibaba.com

Visit holyart.en.alibaba.com

Key Findings

We analyzed Holyart.en.alibaba.com page load time and found that the first response time was 60 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

holyart.en.alibaba.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

holyart.en.alibaba.com

60 ms

holyart.en.alibaba.com

57 ms

error404.htm

99 ms

i.alicdn.com

80 ms

error.css

88 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Holyart.en.alibaba.com, 47% (45 requests) were made to S.alicdn.com and 14% (13 requests) were made to Gj.mmstat.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Fourier.taobao.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (57%)

Content Size

2.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Holyart.en.alibaba.com main page is 2.6 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. 70% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 550.8 kB

  • Original 656.0 kB
  • After minification 599.5 kB
  • After compression 105.2 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 550.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 2.7 kB

  • Original 105.5 kB
  • After minification 102.7 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. Holyart En Alibaba images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 696.0 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 800.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 696.0 kB or 46% of the original size.

CSS Optimization

-68%

Potential reduce by 206.6 kB

  • Original 302.9 kB
  • After minification 302.8 kB
  • After compression 96.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. Holyart.en.alibaba.com needs all CSS files to be minified and compressed as it can save up to 206.6 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (66%)

Requests Now

87

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

holyart.en.alibaba.com

holyart.en.alibaba.com

60 ms

holyart.en.alibaba.com

holyart.en.alibaba.com

57 ms

error404.htm

error404.htm

99 ms

i.alicdn.com

i.alicdn.com

80 ms

error.css

error.css

88 ms

atom.js

atom.js

86 ms

95 ms

202212-image-hack.bundle.js

202212-image-hack.bundle.js

92 ms

index.css

index.css

83 ms

index.js

index.js

90 ms

polyfill.min.js

polyfill.min.js

163 ms

index.js

index.js

90 ms

common.js

common.js

90 ms

error.js

error.js

90 ms

index.js

index.js

134 ms

135 ms

50 ms

TB1VtZtebH1gK0jSZFwXXc7aXXa-65-70.gif

TB1VtZtebH1gK0jSZFwXXc7aXXa-65-70.gif

75 ms

TB1QhYprKT2gK0jSZFvXXXnFXXa-20-20.png

TB1QhYprKT2gK0jSZFvXXXnFXXa-20-20.png

114 ms

queryNicheMaterial.do

queryNicheMaterial.do

109 ms

TB1hVGkvVP7gK0jSZFjXXc5aXXa-365-49.svg

TB1hVGkvVP7gK0jSZFjXXc5aXXa-365-49.svg

71 ms

TB1mHDTXMaH3KVjSZFpXXbhKpXa-600-400.png

TB1mHDTXMaH3KVjSZFpXXbhKpXa-600-400.png

29 ms

O1CN01ghhT9i1HWsCDe82rV_!!6000000000766-2-tps-20-28.png

O1CN01ghhT9i1HWsCDe82rV_!!6000000000766-2-tps-20-28.png

100 ms

AAA=

AAA=

4 ms

AAA=

AAA=

3 ms

font_3610275_m1jmy24w8q.woff

font_3610275_m1jmy24w8q.woff

74 ms

iconfont.woff

iconfont.woff

69 ms

eg.js

eg.js

79 ms

gatewayService

gatewayService

229 ms

footer.css

footer.css

8 ms

TB1SU4upFT7gK0jSZFpXXaTkpXa-440-348.png

TB1SU4upFT7gK0jSZFpXXaTkpXa-440-348.png

8 ms

i.alicdn.com

i.alicdn.com

22 ms

package.js

package.js

48 ms

index.js

index.js

22 ms

async.css

async.css

14 ms

header.js

header.js

63 ms

sc.sc_header_footer.schd_coms

sc.sc_header_footer.schd_coms

12 ms

index.js

index.js

59 ms

need_show_cookie_setting.do

need_show_cookie_setting.do

115 ms

7.gif

7.gif

17 ms

font_1516980_tt14kzligp.woff

font_1516980_tt14kzligp.woff

16 ms

store-proxy.html

store-proxy.html

35 ms

sc.sc_header_footer.sc_hds

sc.sc_header_footer.sc_hds

10 ms

sc.sc_header_footer.sc_hds

sc.sc_header_footer.sc_hds

7 ms

sc.migrate.event

sc.migrate.event

7 ms

sc.sc_header_footer.sc_hds

sc.sc_header_footer.sc_hds

8 ms

queryIpAjax.do

queryIpAjax.do

55 ms

sc.error.exp

sc.error.exp

8 ms

H522339ab58e246ea8d965fe2ff46762eK.jpg_220x220.jpg

H522339ab58e246ea8d965fe2ff46762eK.jpg_220x220.jpg

166 ms

H0a590dc44671474fb314e01252b1a7487.jpg_220x220.jpg

H0a590dc44671474fb314e01252b1a7487.jpg_220x220.jpg

4 ms

H49780099d9d940b687c07d1664d17872U.jpg_220x220.jpg

H49780099d9d940b687c07d1664d17872U.jpg_220x220.jpg

162 ms

Hf4aa9b9700954f1dae19d72999987c97k.png_220x220.png

Hf4aa9b9700954f1dae19d72999987c97k.png_220x220.png

12 ms

Hb6ba4ce3de814f05a3e12d5937c38d76R.jpg_220x220.jpg

Hb6ba4ce3de814f05a3e12d5937c38d76R.jpg_220x220.jpg

88 ms

H27b4234597cb41c4ab056cdba6f397dbZ.jpg_220x220.jpg

H27b4234597cb41c4ab056cdba6f397dbZ.jpg_220x220.jpg

8 ms

Hbe530ab6cb5b460d95894b25fb261d8eP.png_220x220.png

Hbe530ab6cb5b460d95894b25fb261d8eP.png_220x220.png

9 ms

H42871cf49c4e47b6be5ea31d7665a54bb.jpg_220x220.jpg

H42871cf49c4e47b6be5ea31d7665a54bb.jpg_220x220.jpg

14 ms

Hc9f6dbeb9bff4e78bbb60da6c8c61028h.jpg_220x220.jpg

Hc9f6dbeb9bff4e78bbb60da6c8c61028h.jpg_220x220.jpg

23 ms

H52ca684922384ce2bd571203a66f8afb8.jpg_220x220.jpg

H52ca684922384ce2bd571203a66f8afb8.jpg_220x220.jpg

20 ms

Ha903dcd18114407585f6ae180b2f365dX.jpg_220x220.jpg

Ha903dcd18114407585f6ae180b2f365dX.jpg_220x220.jpg

16 ms

H3456567a223b40b79c23e427aa44f441O.jpg_220x220.jpg

H3456567a223b40b79c23e427aa44f441O.jpg_220x220.jpg

19 ms

H3e6d6ca1c5a74da9bf38104f35b341b87.jpg_220x220.jpg

H3e6d6ca1c5a74da9bf38104f35b341b87.jpg_220x220.jpg

24 ms

sc.error.exp

sc.error.exp

5 ms

data

data

157 ms

index.js

index.js

19 ms

defer-common.js

defer-common.js

239 ms

defer-common.css

defer-common.css

11 ms

index.js

index.js

3 ms

awsc.js

awsc.js

7 ms

baxiaCommon.js

baxiaCommon.js

10 ms

rp

rp

1023 ms

et_f.js

et_f.js

4 ms

header.json

header.json

267 ms

personRoleInfo.do

personRoleInfo.do

269 ms

queryRedirectUrl.json

queryRedirectUrl.json

226 ms

unread.htm

unread.htm

372 ms

countryCurrencyDataService

countryCurrencyDataService

184 ms

sc.sc_header_footer.sc_hds

sc.sc_header_footer.sc_hds

145 ms

countryCurrencyDataService

countryCurrencyDataService

177 ms

categoryNaviViewService

categoryNaviViewService

97 ms

sc.sc_header_footer.sc_hds

sc.sc_header_footer.sc_hds

40 ms

queryIpAjax.do

queryIpAjax.do

120 ms

queryIpAjax.do

queryIpAjax.do

117 ms

third-part-login.js

third-part-login.js

16 ms

thirdpart-login-min.js

thirdpart-login-min.js

11 ms

xman_config_sc.js

xman_config_sc.js

127 ms

queryIpAjax.do

queryIpAjax.do

124 ms

69221370.png

69221370.png

44 ms

countryCurrencyDataService

countryCurrencyDataService

38 ms

sc.sc_header_footer_ship_to.init

sc.sc_header_footer_ship_to.init

6 ms

iconfont.woff

iconfont.woff

10 ms

eg.js

eg.js

5 ms

O1CN01wlImAt1sGy58OFEjA_!!6000000005740-2-tps-79-79.png

O1CN01wlImAt1sGy58OFEjA_!!6000000005740-2-tps-79-79.png

6 ms

TB1gBp7SSzqK1RjSZPcXXbTepXa-40-40.png

TB1gBp7SSzqK1RjSZPcXXbTepXa-40-40.png

12 ms

TB1mhSNafc3T1VjSZPfXXcWHXXa-40-32.png

TB1mhSNafc3T1VjSZPfXXcWHXXa-40-32.png

10 ms

TB196hmTbPpK1RjSZFFXXa5PpXa-40-40.png

TB196hmTbPpK1RjSZFFXXa5PpXa-40-40.png

11 ms

TB1C7nRNFYqK1RjSZLeXXbXppXa-66-40.svg

TB1C7nRNFYqK1RjSZLeXXbXppXa-66-40.svg

9 ms

Accessibility Review

holyart.en.alibaba.com accessibility score

76

Accessibility Issues

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

Best Practices

holyart.en.alibaba.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

holyart.en.alibaba.com SEO score

85

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Holyart.en.alibaba.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Holyart.en.alibaba.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

holyart.en.alibaba.com

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