Tools & Wizards About Us
royole.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

royole.com

折叠手机先驱-折叠屏手机与全柔性技术领导者【柔宇科技】

Page Load Speed

84.4 sec in total

First Response

3.8 sec

Resources Loaded

80.1 sec

Page Rendered

516 ms

royole.com screenshot

About Website

Click here to check amazing Royole content for China. Otherwise, check out these important facts you probably never knew about royole.com

柔宇科技致力于新型显示技术及其相关电子产品研发生产销售，可大规模量产高性能超薄彩色柔性显示器,厚度仅有0.01-0.1毫米，全面覆盖移动终端、智能家居、办公教育、运动时尚、智能交通、文娱传媒等六大领域,更多柔性屏产品访问柔宇科技官网。

Visit royole.com

Key Findings

We analyzed Royole.com page load time and found that the first response time was 3.8 sec and then it took 80.7 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 16 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

royole.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value25.7 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value680 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

royole.com

3786 ms

www.royole.com

3760 ms

style.css

7471 ms

font-awesome.min.css

3478 ms

jquery-1.11.0.min.js

6611 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 90% of them (44 requests) were addressed to the original Royole.com, 4% (2 requests) were made to D333gi46xmu1md.cloudfront.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Royole.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 353.8 kB (33%)

Content Size

1.1 MB

After Optimization

710.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 28.5 kB

  • Original 33.9 kB
  • After minification 25.2 kB
  • After compression 5.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 8.7 kB, which is 26% 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 28.5 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 42.3 kB

  • Original 614.2 kB
  • After minification 571.8 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. Royole images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 207.6 kB

  • Original 322.0 kB
  • After minification 312.3 kB
  • After compression 114.4 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 207.6 kB or 64% of the original size.

CSS Optimization

-80%

Potential reduce by 75.3 kB

  • Original 94.2 kB
  • After minification 84.8 kB
  • After compression 18.8 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. Royole.com needs all CSS files to be minified and compressed as it can save up to 75.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (43%)

Requests Now

30

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royole.com

royole.com

3786 ms

www.royole.com

www.royole.com

3760 ms

style.css

style.css

7471 ms

font-awesome.min.css

font-awesome.min.css

3478 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

6611 ms

kxbdSuperMarquee.js

kxbdSuperMarquee.js

13816 ms

news.css

news.css

14752 ms

common.js

common.js

4853 ms

styleen.css

styleen.css

2849 ms

swiper.css

swiper.css

3759 ms

css.css

css.css

7783 ms

css-en.css

css-en.css

4317 ms

base.js

base.js

19594 ms

swiper.jquery.min.js

swiper.jquery.min.js

18523 ms

syku.js

syku.js

5648 ms

scrolltopcontrol.js

scrolltopcontrol.js

6163 ms

large_right-55b22f0fd2195e7665c4aaf86167316d.png

large_right-55b22f0fd2195e7665c4aaf86167316d.png

142 ms

logo.png

logo.png

5802 ms

loader.gif

loader.gif

3127 ms

banner-4.jpg

banner-4.jpg

20157 ms

video1.jpg

video1.jpg

1514 ms

logo2.png

logo2.png

3666 ms

banner-2.jpg

banner-2.jpg

20155 ms

picm-360.png

picm-360.png

4170 ms

news-1.jpg

news-1.jpg

11014 ms

news-2.jpg

news-2.jpg

20155 ms

news-3.jpg

news-3.jpg

10474 ms

video-2.jpg

video-2.jpg

11649 ms

video-1.jpg

video-1.jpg

15129 ms

video-3.jpg

video-3.jpg

16786 ms

picm-160.png

picm-160.png

12115 ms

p-7.jpg

p-7.jpg

20153 ms

p-8.jpg

p-8.jpg

20154 ms

picm-107.png

picm-107.png

18769 ms

royole_ces_2016_list-400x300.jpg

royole_ces_2016_list-400x300.jpg

20153 ms

ces_royole_x-_list-400x300.jpg

ces_royole_x-_list-400x300.jpg

20154 ms

0012-400x300.jpg

0012-400x300.jpg

20153 ms

forbes_ces_2016-400x300.jpg

forbes_ces_2016-400x300.jpg

20154 ms

ces_2016_thekoalition-400x300.jpg

ces_2016_thekoalition-400x300.jpg

20154 ms

reuters_ces_2016-400x300.jpg

reuters_ces_2016-400x300.jpg

20153 ms

large_left-570f9e37cbaa541ae96d8c3ec02c80b1.png

large_left-570f9e37cbaa541ae96d8c3ec02c80b1.png

128 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

20089 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20089 ms

analytics.js

analytics.js

106 ms

collect

collect

83 ms

collect

collect

256 ms

media-screen900.css

media-screen900.css

2265 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

19928 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

19980 ms

Accessibility Review

royole.com accessibility score

54

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.

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

royole.com SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

royole.com

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