Tools & Wizards About Us
yiloong.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

yiloong.com

国内专业稳定木工厂,固化木工厂,树脂滴胶工艺品工厂,刀具刀柄材料木艺厂，树脂木工艺品工厂

Page Load Speed

7.7 sec in total

First Response

2.5 sec

Resources Loaded

4.9 sec

Page Rendered

324 ms

yiloong.com screenshot

About Website

Welcome to yiloong.com homepage info - get ready to check Yiloong best content for Russia right away, or after learning these important things about yiloong.com

稳定木供应商，稳定木厂家,树脂厂家,稳定木树脂刀柄,咖啡手柄，树脂木产品工厂

Visit yiloong.com

Key Findings

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

Performance Metrics

yiloong.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

yiloong.com

2519 ms

outerChain.jsp

902 ms

siteBase2.min.css

595 ms

base2.min.css

676 ms

module.min.css

656 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 11% of them (8 requests) were addressed to the original Yiloong.com, 27% (20 requests) were made to 2.ss.faisys.com and 23% (17 requests) were made to 1.ss.faisys.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Yiloong.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.8 kB (7%)

Content Size

4.0 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yiloong.com main page is 4.0 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. Only a small number of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 170.7 kB

  • Original 202.6 kB
  • After minification 199.4 kB
  • After compression 31.9 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 170.7 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 122.0 kB

  • Original 2.8 MB
  • After minification 2.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. Yiloong images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 41 B

  • Original 865.4 kB
  • After minification 865.4 kB
  • After compression 865.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 154 B

  • Original 134.1 kB
  • After minification 134.1 kB
  • After compression 133.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. Yiloong.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (50%)

Requests Now

70

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yiloong.com

yiloong.com

2519 ms

outerChain.jsp

outerChain.jsp

902 ms

siteBase2.min.css

siteBase2.min.css

595 ms

base2.min.css

base2.min.css

676 ms

module.min.css

module.min.css

656 ms

fkTheme.min.css

fkTheme.min.css

835 ms

themeMixin.min.css

themeMixin.min.css

656 ms

fkModule.min.css

fkModule.min.css

847 ms

newSearchBoxStyle.min.css

newSearchBoxStyle.min.css

657 ms

floatBtn1.min.css

floatBtn1.min.css

657 ms

jzcusstyle.jsp

jzcusstyle.jsp

797 ms

webRightBar.min.css

webRightBar.min.css

659 ms

vue-2.7.14.min.js

vue-2.7.14.min.js

823 ms

comMethods.min.js

comMethods.min.js

855 ms

jzUtils.min.js

jzUtils.min.js

885 ms

polyfill.min.js

polyfill.min.js

887 ms

jzRequest.min.js

jzRequest.min.js

420 ms

jzUtils.min.js

jzUtils.min.js

467 ms

bizShared.min.js

bizShared.min.js

500 ms

bizShared.min.css

bizShared.min.css

483 ms

jquery-core.min.js

jquery-core.min.js

897 ms

jquery-mousewheel.min.js

jquery-mousewheel.min.js

886 ms

frontend.min.js

frontend.min.js

892 ms

jquery-ui-core.min.js

jquery-ui-core.min.js

1062 ms

partitionSite.min.js

partitionSite.min.js

1089 ms

2052.min.js

2052.min.js

483 ms

site.min.js

site.min.js

1088 ms

module.min.js

module.min.js

1087 ms

city2.min.js

city2.min.js

1086 ms

jquery-menu-aim.min.js

jquery-menu-aim.min.js

1086 ms

fontsIco.min.css

fontsIco.min.css

145 ms

hawkEye.min.js

hawkEye.min.js

860 ms

national.png

national.png

34 ms

ABUIABACGAAgruDW1gUoi9zGjAQw9AM4_gE.jpg

ABUIABACGAAgruDW1gUoi9zGjAQw9AM4_gE.jpg

641 ms

vbg01.png

vbg01.png

468 ms

dot.gif

dot.gif

463 ms

AD0I57eMBRACGAAgo5SfvgUo1azQzwYwgA841AM.jpg

AD0I57eMBRACGAAgo5SfvgUo1azQzwYwgA841AM.jpg

748 ms

qrCode.jsp

qrCode.jsp

606 ms

ABUIABACGAAguff01gUo_OjhlgUwoAs49AM.jpg

ABUIABACGAAguff01gUo_OjhlgUwoAs49AM.jpg

731 ms

locater_Arrow3.png

locater_Arrow3.png

60 ms

2000041.gif

2000041.gif

61 ms

sound_0_on.gif

sound_0_on.gif

61 ms

jt4_6.png

jt4_6.png

32 ms

datepicker.min.css

datepicker.min.css

35 ms

icomoon.ttf

icomoon.ttf

351 ms

icomoon.ttf

icomoon.ttf

352 ms

icomoon.ttf

icomoon.ttf

352 ms

icomoon.ttf

icomoon.ttf

416 ms

photoSlide.min.js

photoSlide.min.js

350 ms

imageEffect.min.js

imageEffect.min.js

349 ms

ajaxLoadModuleDom_h.jsp

ajaxLoadModuleDom_h.jsp

1074 ms

mail_h.jsp

mail_h.jsp

284 ms

site_h.jsp

site_h.jsp

515 ms

login_h.jsp

login_h.jsp

832 ms

login.min.css

login.min.css

72 ms

ABUIABACGAAgsMD92wUo1qaKkAQwoAs49AM.jpg

ABUIABACGAAgsMD92wUo1qaKkAQwoAs49AM.jpg

989 ms

ABUIABACGAAg0PD01gUojdiztgYwoAs49AM.jpg

ABUIABACGAAg0PD01gUojdiztgYwoAs49AM.jpg

415 ms

ABUIABACGAAgu-f01gUowvnVqgcwoAs49AM.jpg

ABUIABACGAAgu-f01gUowvnVqgcwoAs49AM.jpg

442 ms

ABUIABACGAAg0vD01gUo1-uUzwUwoAs49AM.jpg

ABUIABACGAAg0vD01gUo1-uUzwUwoAs49AM.jpg

442 ms

index.min.js

index.min.js

79 ms

loading_2b.gif

loading_2b.gif

62 ms

AD0Iu7S6BhAEGAAgwMzaywUo0OPY_gMwpAI4bg.png

AD0Iu7S6BhAEGAAgwMzaywUo0OPY_gMwpAI4bg.png

262 ms

AD0I57eMBRAEGAAgo5SfvgUoqLj1ggcwJjgm.png

AD0I57eMBRAEGAAgo5SfvgUoqLj1ggcwJjgm.png

35 ms

ABUIABAEGAAgj4zm1gUorO-88QUwqgE4qgE.png

ABUIABAEGAAgj4zm1gUorO-88QUwqgE4qgE.png

36 ms

ABUIABAEGAAg5I7m1gUo0NWptgIwqgE4qgE.png

ABUIABAEGAAg5I7m1gUo0NWptgIwqgE4qgE.png

36 ms

ABUIABAEGAAg4qOn3QUoxKus7wEwyAE4yAE!160x160.png

ABUIABAEGAAg4qOn3QUoxKus7wEwyAE4yAE!160x160.png

36 ms

ABUIABACGAAgit3m1gUokOCTgwMw7gU45gU!300x300.jpg

ABUIABACGAAgit3m1gUokOCTgwMw7gU45gU!300x300.jpg

35 ms

ABUIABACGAAgzZPRhgYo-fTphQcwkA44oA0!400x400.jpg

ABUIABACGAAgzZPRhgYo-fTphQcwkA44oA0!400x400.jpg

162 ms

ABUIABACGAAgwZXm1gUonIrFsgcw0wQ4lAM.jpg

ABUIABACGAAgwZXm1gUonIrFsgcw0wQ4lAM.jpg

81 ms

AD0Iu7S6BhAEGAAggs7aywUog-eTkQcwpAI4bg.png

AD0Iu7S6BhAEGAAggs7aywUog-eTkQcwpAI4bg.png

292 ms

AD0Iu7S6BhAEGAAgjc-aywUokJH67AQwpAI4bg.png

AD0Iu7S6BhAEGAAgjc-aywUokJH67AQwpAI4bg.png

323 ms

AD0Iu7S6BhACGAAgtNPaywUotvGbuAQwsAk4AQ.jpg

AD0Iu7S6BhACGAAgtNPaywUotvGbuAQwsAk4AQ.jpg

326 ms

mgClue_h.jsp

mgClue_h.jsp

642 ms

module_webRightBar.min.js

module_webRightBar.min.js

343 ms

vbg01.png

vbg01.png

77 ms

Accessibility Review

yiloong.com accessibility score

95

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.

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

yiloong.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

yiloong.com SEO score

69

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

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 Yiloong.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 Yiloong.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

yiloong.com

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