Tools & Wizards About Us
yelangu.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yelangu.com

Yelangu pocket slider and wireless microphone for camera and smartphone.

Page Load Speed

8.2 sec in total

First Response

368 ms

Resources Loaded

7.5 sec

Page Rendered

283 ms

yelangu.com screenshot

About Website

Click here to check amazing Yelangu content. Otherwise, check out these important facts you probably never knew about yelangu.com

Yelangu pocket slider and wireless microphone for camera and smartphone. camera slider, pocket slider, video light, camera microphone,

Visit yelangu.com

Key Findings

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

Performance Metrics

yelangu.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.959

2/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

yelangu.com

368 ms

www.yelangu.com

637 ms

index.css

75 ms

jqueryV173.js

2015 ms

Public.js

1755 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 58% of them (23 requests) were addressed to the original Yelangu.com, 33% (13 requests) were made to 1.rc.xiniu.com and 8% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Yelangu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 671.4 kB (21%)

Content Size

3.2 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 44.6 kB

  • Original 52.1 kB
  • After minification 31.7 kB
  • After compression 7.5 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 20.4 kB, which is 39% 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 44.6 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 519.7 kB

  • Original 3.0 MB
  • After minification 2.5 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. Obviously, Yelangu needs image optimization as it can save up to 519.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 94.1 kB

  • Original 142.0 kB
  • After minification 139.1 kB
  • After compression 47.9 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 94.1 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 13.0 kB

  • Original 16.2 kB
  • After minification 13.7 kB
  • After compression 3.2 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. Yelangu.com needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

35

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yelangu.com

yelangu.com

368 ms

www.yelangu.com

www.yelangu.com

637 ms

index.css

index.css

75 ms

jqueryV173.js

jqueryV173.js

2015 ms

Public.js

Public.js

1755 ms

index.js

index.js

145 ms

shareWeixin.min.js

shareWeixin.min.js

1474 ms

logo.png

logo.png

76 ms

CgAGe1qvd8KAf9FcAABLOOn9ZJA251.png

CgAGe1qvd8KAf9FcAABLOOn9ZJA251.png

1569 ms

ihpsp1_top_bg.gif

ihpsp1_top_bg.gif

707 ms

yuyan.png

yuyan.png

293 ms

icpsp1_index_company_img.jpg

icpsp1_index_company_img.jpg

501 ms

20171204145319765.png

20171204145319765.png

73 ms

20171204145623968.png

20171204145623968.png

129 ms

copy_bg01ss.png

copy_bg01ss.png

144 ms

hsjjf_more_btn.png

hsjjf_more_btn.png

253 ms

index_join_bg.jpg

index_join_bg.jpg

307 ms

index_join_btn_border.png

index_join_btn_border.png

543 ms

index_news_more_btn2.png

index_news_more_btn2.png

541 ms

index_case_right_img.jpg

index_case_right_img.jpg

647 ms

hm.js

hm.js

653 ms

img_loading.png

img_loading.png

117 ms

20230208153857376.jpg

20230208153857376.jpg

1546 ms

20220429180140791.jpg

20220429180140791.jpg

419 ms

news.png

news.png

712 ms

news_curr.png

news_curr.png

739 ms

637445709588560170911223889.jpg

637445709588560170911223889.jpg

217 ms

638114683160635931940337390.jpg

638114683160635931940337390.jpg

303 ms

637868526002548320773392268.jpg

637868526002548320773392268.jpg

543 ms

6381146825847540363058293.jpg

6381146825847540363058293.jpg

241 ms

637445710137030174113420669.jpg

637445710137030174113420669.jpg

361 ms

637037250884800524915448840.jpg

637037250884800524915448840.jpg

886 ms

6381146915229297861347960634.jpg

6381146915229297861347960634.jpg

816 ms

6381146934931821091035071652.jpg

6381146934931821091035071652.jpg

816 ms

637461424616687343729441567.png

637461424616687343729441567.png

2648 ms

637461424320553893700336420.png

637461424320553893700336420.png

4136 ms

637048255605483643368077580.jpg

637048255605483643368077580.jpg

1767 ms

hm.js

hm.js

943 ms

hm.gif

hm.gif

294 ms

Load.ashx

Load.ashx

79 ms

Accessibility Review

yelangu.com accessibility score

48

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

yelangu.com best practices score

58

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

Page has valid source maps

SEO Factors

yelangu.com SEO score

92

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

    ZH

  • Encoding

    UTF-8

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

yelangu.com

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