Tools & Wizards About Us

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ylocare.com

触摸屏网_手机电脑触摸屏电容电阻屏_工业电容式触摸屏一体机_触摸屏显示器厂家

Page Load Speed

72.8 sec in total

First Response

4 sec

Resources Loaded

68.3 sec

Page Rendered

555 ms

About Website

Welcome to ylocare.com homepage info - get ready to check Ylocare best content right away, or after learning these important things about ylocare.com

触摸屏|电容屏-触摸屏网作为触摸屏行业资讯平台，包括电容式触摸屏产品报价，工业触摸屏，触摸屏电容屏新闻资讯，触摸屏厂家，触摸屏设备和材料，及导电玻璃保护膜油墨导电银浆导电膜贴合机贴片机等相关设备及材料，是专业的触摸屏网站。

Visit ylocare.com

Key Findings

We analyzed Ylocare.com page load time and found that the first response time was 4 sec and then it took 68.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ylocare.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

ylocare.com

3959 ms

www.ylocare.com

8920 ms

style.css

19528 ms

index.css

19979 ms

lang.js

7825 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 84% of them (62 requests) were addressed to the original Ylocare.com, 5% (4 requests) were made to Pos.baidu.com and 4% (3 requests) were made to Dup.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Dup.baidustatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.7 kB (51%)

Content Size

500.1 kB

After Optimization

245.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ylocare.com main page is 500.1 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. 15% of websites need less resources to load. Images take 177.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 89.5 kB

  • Original 107.1 kB
  • After minification 97.6 kB
  • After compression 17.7 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 89.5 kB or 83% of the original size.

Image Optimization

-17%

Potential reduce by 29.6 kB

  • Original 177.7 kB
  • After minification 148.1 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. Obviously, Ylocare needs image optimization as it can save up to 29.6 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

-59%

Potential reduce by 104.9 kB

  • Original 176.9 kB
  • After minification 171.4 kB
  • After compression 72.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 104.9 kB or 59% of the original size.

CSS Optimization

-80%

Potential reduce by 30.8 kB

  • Original 38.4 kB
  • After minification 33.2 kB
  • After compression 7.6 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. Ylocare.com needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ylocare.com accessibility score

46

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

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

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