Tools & Wizards About Us
yealink.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yealink.com

Yealink | UC & C Terminal, Video Collaboration, Conference Phone, IP Phone, Headsets & Video Conferencing

Page Load Speed

3.1 sec in total

First Response

369 ms

Resources Loaded

2.4 sec

Page Rendered

336 ms

yealink.com screenshot

About Website

Visit yealink.com now to see the best up-to-date Yealink content for United States and also check out these interesting facts you probably never knew about yealink.com

Yealink (Stock Code: 300628) is a global brand that specializes in video conferencing, voice communications and collaboration solutions with best-in-class quality, innovative technology and user-frien...

Visit yealink.com

Key Findings

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

Performance Metrics

yealink.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

www.yealink.com

369 ms

en

198 ms

gtm.js

61 ms

iconfont.css

151 ms

styles.css

185 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 75% of them (50 requests) were addressed to the original Yealink.com, 6% (4 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (541 ms) belongs to the original domain Yealink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.5 kB (20%)

Content Size

545.8 kB

After Optimization

439.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Yealink.com main page is 545.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 409.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 78.0 kB

  • Original 93.4 kB
  • After minification 82.8 kB
  • After compression 15.4 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 10.7 kB, which is 11% 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 78.0 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 28.4 kB

  • Original 409.5 kB
  • After minification 381.0 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. Yealink images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

Requests Breakdown

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

Requests Now

63

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.yealink.com

www.yealink.com

369 ms

en

en

198 ms

gtm.js

gtm.js

61 ms

iconfont.css

iconfont.css

151 ms

styles.css

styles.css

185 ms

main.dedee53bccfad80ac904.css

main.dedee53bccfad80ac904.css

222 ms

home.dedee53bccfad80ac904.css

home.dedee53bccfad80ac904.css

222 ms

package.js

package.js

277 ms

layer.min.js

layer.min.js

443 ms

home.css

home.css

448 ms

js

js

105 ms

element.js

element.js

50 ms

classie.js

classie.js

392 ms

bxslider.js

bxslider.js

389 ms

home.js

home.js

393 ms

main.dedee53bccfad80ac904.js

main.dedee53bccfad80ac904.js

394 ms

home.dedee53bccfad80ac904.js

home.dedee53bccfad80ac904.js

421 ms

analytics.js

analytics.js

64 ms

insight.min.js

insight.min.js

48 ms

lftracker_v1_YEgkB8lWGV1aep3Z.js

lftracker_v1_YEgkB8lWGV1aep3Z.js

55 ms

c920529fd70a4f1988f1f9cd0cec777b.js

c920529fd70a4f1988f1f9cd0cec777b.js

101 ms

insight_tag_errors.gif

insight_tag_errors.gif

283 ms

collect

collect

17 ms

collect

collect

29 ms

js

js

48 ms

ga-audiences

ga-audiences

214 ms

js

js

127 ms

logo_2021_en.png

logo_2021_en.png

238 ms

mouse-icon.svg

mouse-icon.svg

237 ms

meetingborad-homepage.png

meetingborad-homepage.png

240 ms

headset.png

headset.png

239 ms

ipphone.png

ipphone.png

235 ms

webcam.png

webcam.png

238 ms

yealinkmeeting.png

yealinkmeeting.png

262 ms

smartworkspace.png

smartworkspace.png

262 ms

managementplatform.png

managementplatform.png

262 ms

microsoftzoom.png

microsoftzoom.png

262 ms

yealink_logo.png

yealink_logo.png

262 ms

close.svg

close.svg

263 ms

arrow-down-bold.png

arrow-down-bold.png

323 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

225 ms

60f76f87ea348500148a9214

60f76f87ea348500148a9214

352 ms

20240411102958381395b70f8440c80fc14b67d1da4cd.jpg

20240411102958381395b70f8440c80fc14b67d1da4cd.jpg

398 ms

20240410095902853fbb1d28d4e27952b3d48d5968f84.jpg

20240410095902853fbb1d28d4e27952b3d48d5968f84.jpg

404 ms

202403111027537695a5a5e174d0cbbc71984fe657a1d.jpg

202403111027537695a5a5e174d0cbbc71984fe657a1d.jpg

340 ms

2023103002003278e6e6eb104b408a46719a09229809.jpg

2023103002003278e6e6eb104b408a46719a09229809.jpg

340 ms

20230527012246737250b97b44d13a879be99527fe676.jpg

20230527012246737250b97b44d13a879be99527fe676.jpg

285 ms

20230608053742128e9f625444f27957385c31a37d025.jpg

20230608053742128e9f625444f27957385c31a37d025.jpg

404 ms

vcdevicebg.png

vcdevicebg.png

348 ms

headsetbg.png

headsetbg.png

412 ms

ipphonebg.png

ipphonebg.png

402 ms

webcambg.png

webcambg.png

411 ms

yealinkmeetingbg.png

yealinkmeetingbg.png

459 ms

smartworkspacebg.png

smartworkspacebg.png

464 ms

managementplatformbg.png

managementplatformbg.png

466 ms

microsoftzoombg.png

microsoftzoombg.png

466 ms

2021_three_back.png

2021_three_back.png

476 ms

bg_five.png

bg_five.png

473 ms

FrostSullivan2019.png

FrostSullivan2019.png

522 ms

FrostSullivan2020.png.png

FrostSullivan2020.png.png

526 ms

ITSPAAwards.png

ITSPAAwards.png

530 ms

2023083108041023f24dfc6748f599a8f9ffb07bdbc4.png

2023083108041023f24dfc6748f599a8f9ffb07bdbc4.png

539 ms

20230821015830477d52b9ef646999701d7704fa35608.png

20230821015830477d52b9ef646999701d7704fa35608.png

540 ms

20230718012049684dc982a024e35aac631dffbca1206.jpg

20230718012049684dc982a024e35aac631dffbca1206.jpg

541 ms

lftracker_v1_kn9Eq4RK3glaRlvP.js

lftracker_v1_kn9Eq4RK3glaRlvP.js

148 ms

iconfont.woff

iconfont.woff

538 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

26 ms

Accessibility Review

yealink.com accessibility score

74

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

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

SEO Factors

yealink.com SEO score

83

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

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

yealink.com

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