Tools & Wizards About Us
en.yangli.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

en.yangli.com

Metal Forming Complete Solution Provider-Yangli Group

Page Load Speed

7.9 sec in total

First Response

1.6 sec

Resources Loaded

6.2 sec

Page Rendered

143 ms

en.yangli.com screenshot

About Website

Welcome to en.yangli.com homepage info - get ready to check En Yangli best content right away, or after learning these important things about en.yangli.com

YANGLI GROUP was established in 1966 and located in the ancient city named Yangzhou,the core area of theindustrial region of the Yangtze Delta.It was registered RMB 0.1 5 billion and now total assets ...

Visit en.yangli.com

Key Findings

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

Performance Metrics

en.yangli.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.562

12/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

en.yangli.com

1567 ms

style.css

1075 ms

fakeloader.css

429 ms

jquery.js

1295 ms

lib.js

431 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that all of those requests were addressed to En.yangli.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain En.yangli.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 916.9 kB (11%)

Content Size

8.0 MB

After Optimization

7.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of En.yangli.com main page is 8.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. 30% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 102.9 kB

  • Original 112.7 kB
  • After minification 71.4 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 41.4 kB, which is 37% 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 102.9 kB or 91% of the original size.

Image Optimization

-10%

Potential reduce by 770.2 kB

  • Original 7.8 MB
  • After minification 7.0 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. En Yangli images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 31.4 kB

  • Original 90.4 kB
  • After minification 90.4 kB
  • After compression 59.0 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 31.4 kB or 35% of the original size.

CSS Optimization

-37%

Potential reduce by 12.4 kB

  • Original 33.5 kB
  • After minification 33.5 kB
  • After compression 21.0 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. En.yangli.com needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (20%)

Requests Now

79

After Optimization

63

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.yangli.com

en.yangli.com

1567 ms

style.css

style.css

1075 ms

fakeloader.css

fakeloader.css

429 ms

jquery.js

jquery.js

1295 ms

lib.js

lib.js

431 ms

fakeloader.min.js

fakeloader.min.js

431 ms

animate.min.css

animate.min.css

219 ms

jquery.fullPage.css

jquery.fullPage.css

219 ms

wow.min.js

wow.min.js

222 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

657 ms

slick.css

slick.css

436 ms

slick.min.js

slick.min.js

653 ms

logo1.png

logo1.png

225 ms

logo2.png

logo2.png

223 ms

y-p11.jpg

y-p11.jpg

431 ms

i-line1.png

i-line1.png

226 ms

i-so.png

i-so.png

225 ms

mo-tel.png

mo-tel.png

224 ms

mo-tel2.png

mo-tel2.png

431 ms

mo-logo.png

mo-logo.png

434 ms

mo-logo2.png

mo-logo2.png

433 ms

1f71630aa777f226a4f6ed853a0a7d48.png

1f71630aa777f226a4f6ed853a0a7d48.png

2038 ms

c7e625c45a3ae9e0d9b2d7c574f7b4cb.jpg

c7e625c45a3ae9e0d9b2d7c574f7b4cb.jpg

2150 ms

66341d3060eeacc94ba404d2e56ba846.jpg

66341d3060eeacc94ba404d2e56ba846.jpg

1297 ms

0f0c3d1d95c722aa9a4d920d5fb542b7.jpg

0f0c3d1d95c722aa9a4d920d5fb542b7.jpg

1291 ms

8eb16977d4a41b989be645234e3d05c6.jpg

8eb16977d4a41b989be645234e3d05c6.jpg

1310 ms

34648dfe8e81b68019493bacf830d70a.jpg

34648dfe8e81b68019493bacf830d70a.jpg

870 ms

89b7745262e98e61857691139f49c41d.jpg

89b7745262e98e61857691139f49c41d.jpg

1309 ms

y-p4.jpg

y-p4.jpg

2173 ms

y-p7.jpg

y-p7.jpg

1524 ms

y-p72.jpg

y-p72.jpg

1534 ms

y-p73.jpg

y-p73.jpg

1539 ms

y-p74.jpg

y-p74.jpg

1744 ms

map.png

map.png

1756 ms

q-map.png

q-map.png

1765 ms

6c36410b590592fca95caa8135282394.jpg

6c36410b590592fca95caa8135282394.jpg

1977 ms

659dc7c1e4b8853a7dd754922b1ab828.jpg

659dc7c1e4b8853a7dd754922b1ab828.jpg

1996 ms

90446246e7714f8ac8c14e102a5c51c3.jpg

90446246e7714f8ac8c14e102a5c51c3.jpg

2017 ms

fb2c3c49376755c5bd6b9adf6bccdb0a.jpg

fb2c3c49376755c5bd6b9adf6bccdb0a.jpg

2211 ms

2eae3df19834193b1797f1b88e35b38f.jpg

2eae3df19834193b1797f1b88e35b38f.jpg

2230 ms

q-right2.png

q-right2.png

2233 ms

i-l3.png

i-l3.png

2252 ms

i-l2.png

i-l2.png

2361 ms

352b16df5c4ee863af29f10cf41948c1.jpg

352b16df5c4ee863af29f10cf41948c1.jpg

2387 ms

135c326a8e35bd2b328b908d569d2bd9.jpg

135c326a8e35bd2b328b908d569d2bd9.jpg

2427 ms

e2510d79f1a5a7ae3e55cf7f86e68b75.jpg

e2510d79f1a5a7ae3e55cf7f86e68b75.jpg

2444 ms

a6e4f85b05644905c41d452be500e584.jpg

a6e4f85b05644905c41d452be500e584.jpg

2447 ms

08698c7d25494fff41eb1b39acf03247.jpg

08698c7d25494fff41eb1b39acf03247.jpg

2427 ms

df6513355fd552ffe2daf53f1921c636.jpg

df6513355fd552ffe2daf53f1921c636.jpg

2361 ms

fb5e5f409c6e6c9186738be627cc4749.jpg

fb5e5f409c6e6c9186738be627cc4749.jpg

2385 ms

5610970e2e4677432faf7f11747805d7.jpg

5610970e2e4677432faf7f11747805d7.jpg

2424 ms

d13a2266294c11e32df9bda13eedaefd.jpg

d13a2266294c11e32df9bda13eedaefd.jpg

2441 ms

99dcd5c18de882bc4dc374e9217562ca.jpg

99dcd5c18de882bc4dc374e9217562ca.jpg

2441 ms

8659ef0d85bdbfa6f073144a9bf823ff.jpg

8659ef0d85bdbfa6f073144a9bf823ff.jpg

2266 ms

a045ed254298088e584ee732d8d4d5fa.jpg

a045ed254298088e584ee732d8d4d5fa.jpg

2368 ms

c766c308f9b4696b607400c6357e297d.jpg

c766c308f9b4696b607400c6357e297d.jpg

2390 ms

qr1.jpg

qr1.jpg

2429 ms

logo3.png

logo3.png

2009 ms

qr2.png

qr2.png

1593 ms

i-line2.png

i-line2.png

1613 ms

8cf7047fe94f45552b0f11e492f812b9.jpg

8cf7047fe94f45552b0f11e492f812b9.jpg

1720 ms

b-icon2.png

b-icon2.png

1730 ms

b-icon3.png

b-icon3.png

1555 ms

253108b7d9148ed842e7d19deb9e144a.jpg

253108b7d9148ed842e7d19deb9e144a.jpg

1602 ms

6810d4c9b4229e3065d66c32c260fc07.jpg

6810d4c9b4229e3065d66c32c260fc07.jpg

1623 ms

i-down.png

i-down.png

1425 ms

i-sj.png

i-sj.png

1485 ms

i-sj3.png

i-sj3.png

1489 ms

bg1.jpg

bg1.jpg

1328 ms

bg2.jpg

bg2.jpg

1354 ms

i-top.png

i-top.png

1357 ms

i-tel1.png

i-tel1.png

1366 ms

i-kf.png

i-kf.png

1309 ms

i-ly.png

i-ly.png

1294 ms

i-wx1.png

i-wx1.png

1309 ms

i-wb1.png

i-wb1.png

1335 ms

i-n.png

i-n.png

1356 ms

prev1.png

prev1.png

1375 ms

next1.png

next1.png

1310 ms

i-non.png

i-non.png

1291 ms

Accessibility Review

en.yangli.com accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

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

en.yangli.com best practices score

67

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

SEO Factors

en.yangli.com SEO score

85

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

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

en.yangli.com

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