15.1 sec in total
661 ms
12.9 sec
1.5 sec
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
Visit oray.comWe analyzed Oray.com page load time and found that the first response time was 661 ms and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
oray.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value23.9 s
0/100
25%
Value14.6 s
1/100
10%
Value1,270 ms
19/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
661 ms
1811 ms
285 ms
1544 ms
1747 ms
Our browser made a total of 231 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Oray.com, 84% (193 requests) were made to Res.orayimg.com and 14% (32 requests) were made to Webchat.7moor.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Res.orayimg.com.
Page size can be reduced by 637.1 kB (6%)
10.7 MB
10.0 MB
In fact, the total size of Oray.com main page is 10.7 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. 65% of websites need less resources to load. Images take 10.2 MB which makes up the majority of the site volume.
Potential reduce by 109.0 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 109.0 kB or 68% of the original size.
Potential reduce by 504.6 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.
Potential reduce by 20.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.
Potential reduce by 2.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. Oray.com needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 13% of the original size.
Number of requests can be reduced by 29 (13%)
225
196
The browser has sent 225 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 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
oray.com
661 ms
www.oray.com
1811 ms
awsc.js
285 ms
ea25a18.css
1544 ms
5d133e9.css
1747 ms
c1b3fc5.css
1949 ms
et_n.js
229 ms
banner_left3.b6f0c53.png
2213 ms
sunlogin.647b0af.png
1889 ms
pgy.0cb5c93.png
1907 ms
hsk.bcfa2f6.png
1847 ms
onion.fc0208c.png
2082 ms
os_pc.632dd71.png
2125 ms
os_mb.d80674b.png
2032 ms
devops-icon.27eb903.png
2086 ms
devops-case1.a39ff00.png
2912 ms
remote-icon.e0d6a9d.png
2226 ms
ssh-icon.f9428de.png
2310 ms
IOT-icon.28e0e9c.png
2289 ms
video-icon.9f1f864.png
2983 ms
logo1.50bd29c.png
2422 ms
logo-1-1.439ff13.png
2420 ms
logo-1-2.18500a8.png
2529 ms
logo-1-3.8a4101a.png
2579 ms
logo-1-4.b47e18a.png
2614 ms
logo-1-5.4077050.png
2624 ms
logo-1-6.9495748.png
2752 ms
logo-1-7.bb582de.png
2831 ms
logo-1-8.549e323.png
2822 ms
logo-1-9.ad2d6f5.png
2828 ms
logo-1-10.2113614.png
2958 ms
logo-1-11.d35df0c.png
3038 ms
logo-1-12.4074ee9.png
3026 ms
logo-1-13.050f973.png
3084 ms
logo-1-14.7744d23.png
3109 ms
logo-1-15.d3cd749.png
3185 ms
logo2.0f668bd.png
3273 ms
logo-2-1.3dfb947.png
3228 ms
logo-2-2.e4ee2d3.png
3236 ms
logo-2-3.1daaf90.png
3338 ms
7moorInit.js
1300 ms
80aef75.js
2063 ms
7018d3a.js
1977 ms
online
335 ms
f5660aa.js
1823 ms
QiMoIMSDK-0564057a6c.js
340 ms
76a2649.js
1574 ms
5a29fe2.js
2558 ms
DINPro-Medium.2e7ded0.otf
1615 ms
logo-2-4.8a9ecfa.png
1545 ms
logo-2-5.cf7456a.png
1556 ms
logo-2-6.41f35d1.png
1553 ms
logo-2-7.2117f34.png
1606 ms
agentLogo.png
258 ms
chatStyle-e5ac22f12b.css
504 ms
online
689 ms
896beb70-d81a-11e7-b6e7-9da891414b0f.png
1535 ms
1.png
717 ms
invite-close.png
725 ms
defaultPhoto.png
1102 ms
small.png
723 ms
big.png
741 ms
close.png
933 ms
moor_chat.html
1216 ms
logo-2-8.98638e0.png
1634 ms
logo-2-9.771794e.png
1596 ms
logo-2-10.a67c8b7.png
1558 ms
logo-2-11.a39c06b.png
1525 ms
logo-2-12.5b373a8.png
1509 ms
logo-2-13.acbf07c.png
1599 ms
logo-2-14.ae3c42c.png
1517 ms
logo-2-15.00999b2.png
1538 ms
logo3.1399157.png
1460 ms
logo-3-1.3e69348.png
1506 ms
logo-3-2.c1a2da1.png
1462 ms
logo-3-3.7516f1c.png
1423 ms
logo-3-4.d29a857.png
1459 ms
logo-3-5.781e7db.png
1518 ms
logo-3-6.0905d75.png
1420 ms
logo-3-7.30b9aeb.png
1451 ms
logo-3-8.667d795.png
1466 ms
logo-3-9.f46ba64.png
1466 ms
logo-3-10.82ffbf4.png
1926 ms
logo-3-11.d9cbce3.png
1495 ms
logo-3-12.80f3238.png
1497 ms
moor_style-c3422f4c70.css
495 ms
idangerous_swiper-9998bd2b30.css
235 ms
iconfont.css
245 ms
m7AllQuote.js
1947 ms
jdate.js
266 ms
distpicker.data.js
453 ms
distpicker.js
460 ms
idangerous_swiper.js
545 ms
base64.min.js
493 ms
fileTypeMap.js
521 ms
swiper-bundle.min.js
743 ms
logo-3-13.ae3c42c.png
1473 ms
logo-3-14.5b373a8.png
1438 ms
logo-3-15.2dba4cc.png
1475 ms
logo1.1cb6833.png
1561 ms
logo-1-1.6a7a97c.png
1492 ms
logo-1-2.cd5191d.png
1520 ms
logo-1-3.180da11.png
1463 ms
logo-1-4.afe8134.png
1514 ms
logo-1-5.ffa3b75.png
1461 ms
logo-1-6.2f16936.png
1486 ms
logo-1-7.7b746e3.png
1437 ms
logo-1-8.e7081f2.png
1470 ms
logo-1-9.83b077f.png
1578 ms
logo-1-10.f7d182a.png
1489 ms
logo-1-11.d3335ac.png
1396 ms
logo-1-12.3fe41a4.png
1469 ms
logo-1-13.54a4249.png
1834 ms
logo-1-14.30b15cf.png
1480 ms
logo-1-15.071f57b.png
1458 ms
logo2.ddb74df.png
1363 ms
logo-2-1.feecab8.png
1346 ms
logo-2-2.9068b0f.png
1489 ms
logo-2-3.b25a748.png
1429 ms
logo-2-4.bcfb4ae.png
1464 ms
logo-2-5.c651a7e.png
1421 ms
logo-2-6.1bde193.png
1348 ms
logo-2-7.934dc88.png
1502 ms
logo-2-8.b02ce26.png
1497 ms
logo-2-9.ccc4d92.png
1448 ms
logo-2-10.767980c.png
1388 ms
logo-2-11.08e3637.png
1401 ms
logo-2-12.2ec0667.png
1429 ms
logo-2-13.28abf61.png
1524 ms
logo-2-14.9eb466a.png
1419 ms
logo-2-15.c1cddf3.png
1386 ms
logo3.644ecbc.png
1426 ms
logo-3-1.46bfe11.png
1398 ms
logo-3-2.d0b3d4e.png
1397 ms
logo-3-3.5628907.png
1395 ms
logo-3-4.3f6670b.png
1364 ms
logo-3-5.2f22c87.png
1376 ms
logo-3-6.c3ea3c9.png
1393 ms
logo-3-7.de362e0.png
1396 ms
logo-3-8.a1e7a4a.png
1366 ms
logo-3-9.1350e7b.png
1397 ms
logo-3-10.551721d.png
1341 ms
logo-3-11.8855d82.png
1387 ms
logo-3-12.75c400a.png
1397 ms
left_float_icon.png
249 ms
right_float_icon.png
244 ms
continue-advisory.png
237 ms
close-icon.png
248 ms
video-invite.png
250 ms
socket.io-2.3.0.js
518 ms
logo-3-13.4b4f9ed.png
1324 ms
logo-3-14.fa64338.png
1368 ms
iconfont.woff
481 ms
logo-3-15.30e4d22.png
1375 ms
logo1.a639751.png
1336 ms
logo-1-1.29e942e.png
1358 ms
logo-1-2.4f54994.png
1323 ms
logo-1-3.768b010.png
1362 ms
logo-1-4.7a7142a.png
1426 ms
logo-1-5.53e59de.png
1239 ms
logo-1-6.d798623.png
1242 ms
logo-1-7.0cde721.png
1296 ms
logo-1-8.088d24b.png
1309 ms
logo-1-9.44f9131.png
1320 ms
logo-1-10.0d43642.png
1301 ms
7moorChat-93c81b84ae.js
872 ms
logo-1-11.c962a34.png
1219 ms
logo-1-12.2966527.png
1255 ms
logo-1-13.01c8ec3.png
1297 ms
logo-1-14.1121c3d.png
1284 ms
logo-1-15.1c3bdf7.png
1311 ms
logo2.ac2d906.png
1291 ms
logo-2-1.8a9c6e4.png
1218 ms
logo-2-2.7f84b62.png
1290 ms
logo-2-3.eaaf133.png
1297 ms
logo-2-4.4369dee.png
1286 ms
logo-2-5.0fd2084.png
1303 ms
logo-2-6.5c28729.png
1276 ms
logo-2-7.57a1a46.png
1215 ms
logo-2-8.000d3c8.png
1362 ms
logo-2-9.8081568.png
1295 ms
logo-2-10.424b983.png
1269 ms
logo-2-11.b9cd22d.png
1246 ms
logo-2-12.5eb7419.png
1267 ms
logo-2-13.3701aa4.png
1222 ms
logo-2-14.8f56350.png
1349 ms
logo-2-15.eab5501.png
1287 ms
logo3.16ddd24.png
1305 ms
logo-3-1.ef46f83.png
1228 ms
logo-3-2.3c39dff.png
1214 ms
logo-3-3.db75aa2.png
1225 ms
logo-3-4.6520311.png
1307 ms
chat
489 ms
logo-3-5.a9e17db.png
1285 ms
logo-3-6.a8c985f.png
1256 ms
logo-3-7.18ddaf6.png
1252 ms
logo-3-8.ea3dda6.png
1272 ms
logo-3-9.7b5b374.png
1215 ms
logo-3-10.0c01fd0.png
1342 ms
logo-3-11.172c4d6.png
1268 ms
logo-3-12.6b34522.png
1282 ms
logo-3-13.9009bfe.png
1263 ms
logo-3-14.de47ced.png
1248 ms
logo-3-15.9d1d484.png
1289 ms
safe-1.e115f61.png
1300 ms
safe-2.00f0df1.png
1258 ms
safe-3.6db640b.png
1289 ms
safe-4.2990079.png
1265 ms
safe-5.4015103.png
1236 ms
safe-6.5c764fb.png
1311 ms
safe-7.bf7ce5a.png
1258 ms
safe-8.08411b3.png
1245 ms
safe-9.586f4d3.png
1269 ms
safe-10.96378b1.png
1244 ms
case-changhong.6d58073.jpg
2015 ms
changhong-logo.9ef1be1.png
1370 ms
case-liangxue.b927d5d.jpg
1805 ms
liangxue-logo.e73b42a.png
1225 ms
case-huawei.fe900f0.png
2220 ms
huawei-logo.92276e5.jpg
1255 ms
case-devops.468a5d9.jpg
2125 ms
devops-logo.7f9e45a.png
1413 ms
case-debang.8606aed.jpg
1986 ms
debang-logo.32e813d.png
1504 ms
case-ziyan.5b08fc3.jpg
2705 ms
ziyan-logo.244b57e.png
1732 ms
programme.b235f34.png
1787 ms
changhong-bg.67e78e1.png
2257 ms
home_banner3.c44e80f.jpg
1875 ms
arrow.10b4a20.png
2000 ms
solution-bg.7bb204d.png
2177 ms
oray.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
oray.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
oray.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
EN
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 it does not match the claimed English language. 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.
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: