Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

open.oray.com

花生壳,向日葵,蒲公英软硬件嵌入,DDNS,远程控制,智能组网接入-贝锐

Page Load Speed

73.5 sec in total

First Response

8.5 sec

Resources Loaded

64.6 sec

Page Rendered

378 ms

open.oray.com screenshot

About Website

Welcome to open.oray.com homepage info - get ready to check Open Oray best content for China right away, or after learning these important things about open.oray.com

花生壳软硬件嵌入,向日葵软硬件嵌入,蒲公英软硬件嵌入,智能组网接入,DDNS接入,远程控制接入,软硬件嵌入开发,花生壳嵌入开发,向日葵嵌入开发

Visit open.oray.com

Key Findings

We analyzed Open.oray.com page load time and found that the first response time was 8.5 sec and then it took 65 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

open.oray.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

developer.oray.com

8451 ms

style-1.0.4.css

3991 ms

jquery-1.7.2.js

15591 ms

8505 ms

common-1.0.5.js

8611 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Open.oray.com, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Developer.oray.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Static.orayimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.5 kB (60%)

Content Size

226.4 kB

After Optimization

89.8 kB

In fact, the total size of Open.oray.com main page is 226.4 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. Only 10% of websites need less resources to load. Javascripts take 165.2 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 5.4 kB

  • Original 7.8 kB
  • After minification 6.5 kB
  • After compression 2.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 1.3 kB, which is 17% 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 5.4 kB or 69% of the original size.

Image Optimization

-23%

Potential reduce by 6.6 kB

  • Original 28.3 kB
  • After minification 21.7 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, Open Oray needs image optimization as it can save up to 6.6 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 105.1 kB

  • Original 165.2 kB
  • After minification 165.2 kB
  • After compression 60.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 105.1 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 19.4 kB

  • Original 25.1 kB
  • After minification 24.4 kB
  • After compression 5.7 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. Open.oray.com needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

14

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Oray. 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.

Accessibility Review

open.oray.com accessibility score

80

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

open.oray.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

open.oray.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

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

    EN

  • Encoding

    UTF-8

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