Tools & Wizards About Us
oray.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

oray.com

花生壳动态域名解析服务-贝锐官网|花生壳官网|DNS内网穿透|域名注册|向日葵远程控制|远程桌面|蒲公英路由器-贝锐官网

Page Load Speed

73.5 sec in total

First Response

2.1 sec

Resources Loaded

71.2 sec

Page Rendered

305 ms

oray.com screenshot

About Website

Visit oray.com now to see the best up-to-date Oray content for China and also check out these interesting facts you probably never knew about oray.com

Oray花生壳官网提供花生壳动态域名、花生壳域名注册、向日葵远程控制、蒲公英智能组网路由器、橄榄邮企业邮箱、智能建站、云空间等互联网服务，是开放的互联网应用服务引领者，所有服务都可以免费使用。

Visit oray.com

Key Findings

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

Performance Metrics

oray.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value8,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

oray.com

2055 ms

www.oray.com

8484 ms

style-2.2.9.css

3580 ms

style-2.0.1.css

13447 ms

jquery-1.7.2.js

19618 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 10% of them (4 requests) were addressed to the original Oray.com, 74% (31 requests) were made to Static.orayimg.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Static.orayimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.2 kB (47%)

Content Size

667.0 kB

After Optimization

352.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oray.com main page is 667.0 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 288.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 25.0 kB

  • Original 31.8 kB
  • After minification 25.1 kB
  • After compression 6.8 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 6.7 kB, which is 21% 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 25.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 10.5 kB

  • Original 288.6 kB
  • After minification 278.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. Oray images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 50.5 kB

  • Original 73.2 kB
  • After minification 64.5 kB
  • After compression 22.7 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 50.5 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 228.1 kB

  • Original 273.3 kB
  • After minification 221.1 kB
  • After compression 45.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. Oray.com needs all CSS files to be minified and compressed as it can save up to 228.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

34

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

oray.com

oray.com

2055 ms

www.oray.com

www.oray.com

8484 ms

style-2.2.9.css

style-2.2.9.css

3580 ms

style-2.0.1.css

style-2.0.1.css

13447 ms

jquery-1.7.2.js

jquery-1.7.2.js

19618 ms

jquery-1.4.4.js

jquery-1.4.4.js

6368 ms

jquery-banner-loop2.0.1.js

jquery-banner-loop2.0.1.js

4033 ms

4562 ms

5746 ms

remind.php

remind.php

504 ms

home-1.0.6.js

home-1.0.6.js

6382 ms

getheader

getheader

6935 ms

analytics.js

analytics.js

36 ms

hm.js

hm.js

885 ms

push.js

push.js

3732 ms

logo_80x104.png

logo_80x104.png

2370 ms

hsk_20151214.png

hsk_20151214.png

2097 ms

hardware_20151214.png

hardware_20151214.png

1941 ms

router_20151214.png

router_20151214.png

3212 ms

domain_20151214.png

domain_20151214.png

2917 ms

hsk_logo.png

hsk_logo.png

993 ms

pic_hsb.png

pic_hsb.png

3833 ms

sunlogin_logo.png

sunlogin_logo.png

2435 ms

pic_hardware.png

pic_hardware.png

5048 ms

pgy_logo.png

pgy_logo.png

4254 ms

pic_router.png

pic_router.png

13683 ms

qrcode_oray20160406.png

qrcode_oray20160406.png

8033 ms

pic_31.png

pic_31.png

8005 ms

pic_34.jpg

pic_34.jpg

20427 ms

pic_08.jpg

pic_08.jpg

14266 ms

pic_32.png

pic_32.png

12395 ms

slide_bg.png

slide_bg.png

8463 ms

icon_sprite.png

icon_sprite.png

10331 ms

domain_logo.png

domain_logo.png

8920 ms

picp_bg.jpg

picp_bg.jpg

12019 ms

check

check

3679 ms

www.oray.com

www.oray.com

569 ms

collect

collect

8 ms

collect

collect

58 ms

iconfont.woff

iconfont.woff

15161 ms

iconfont.woff

iconfont.woff

20337 ms

iconfont.ttf

iconfont.ttf

20469 ms

Accessibility Review

oray.com accessibility score

67

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.

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

oray.com best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oray.com SEO score

85

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

    N/A

  • Encoding

    UTF-8

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

oray.com

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