7.4 sec in total
322 ms
6.9 sec
183 ms
Visit oro.co.jp now to see the best up-to-date Oro content for Japan and also check out these interesting facts you probably never knew about oro.co.jp
株式会社オロの公式企業サイトです。会社概要、サービス、オロの歩み、拠点一覧、採用情報などを掲載しています。
Visit oro.co.jpWe analyzed Oro.co.jp page load time and found that the first response time was 322 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
oro.co.jp performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.0 s
48/100
25%
Value7.9 s
22/100
10%
Value24,180 ms
0/100
30%
Value0.102
89/100
15%
Value34.9 s
0/100
10%
322 ms
295 ms
612 ms
446 ms
594 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 55% of them (59 requests) were addressed to the original Oro.co.jp, 18% (19 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Oro.co.jp.
Page size can be reduced by 151.6 kB (22%)
682.1 kB
530.5 kB
In fact, the total size of Oro.co.jp main page is 682.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. 40% of websites need less resources to load. Images take 459.2 kB which makes up the majority of the site volume.
Potential reduce by 13.9 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 13.9 kB or 67% of the original size.
Potential reduce by 6.5 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. Oro images are well optimized though.
Potential reduce by 108.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 108.8 kB or 62% of the original size.
Potential reduce by 22.4 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. Oro.co.jp needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 81% of the original size.
Number of requests can be reduced by 68 (67%)
102
34
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
oro.co.jp
322 ms
www.oro.co.jp
295 ms
www.oro.co.jp
612 ms
index.css
446 ms
jquery.js
594 ms
pngfix.js
443 ms
scroll.js
442 ms
site.js
465 ms
ga.js
536 ms
tracker.js
904 ms
swfobject.js
976 ms
jsapi
35 ms
jquery.ah-placeholder.js
982 ms
import.css
563 ms
default.css
235 ms
module.css
291 ms
style.css
459 ms
print.css
515 ms
global_header_corporate.css
543 ms
gtm.js
110 ms
vr-separator.png
213 ms
btn-corporate_on.png
530 ms
btn-zac_off.png
531 ms
btn-cd_off.png
534 ms
logo.png
534 ms
pic-dummy.jpg
1542 ms
title-cd.gif
749 ms
txt-web.gif
988 ms
btn-details_off.gif
1063 ms
title-zac.gif
1065 ms
txt-zac.gif
1111 ms
bnr_reforma.jpg
1554 ms
nicori_bnr.jpg
1917 ms
ttls-topics.gif
1647 ms
icn-rss.gif
1751 ms
btn-list_off.gif
1752 ms
bnr-recruit.jpg
2019 ms
bnr-president.jpg
2324 ms
bnr_eco.gif
2162 ms
bnr-bro.gif
2188 ms
btn-corporate_off.gif
2227 ms
btn-pressroom_off.gif
2429 ms
btn-freshers_off.gif
2561 ms
btn-inquiry_off.gif
2624 ms
btn-zac_off.gif
2730 ms
btn-cd_off.gif
2817 ms
btn-inquiry_off.gif
2857 ms
btn-individual_off.gif
2943 ms
btn-security_off.gif
3094 ms
btn-policy_off.gif
3165 ms
btn-sitemap_off.gif
3192 ms
copy.gif
3331 ms
39 ms
default+ja.css
5 ms
minimalist.css
18 ms
default+ja.I.js
19 ms
minimalist.css
62 ms
conversion_async.js
93 ms
analytics.js
161 ms
likebox.php
407 ms
conversion.js
953 ms
async-ads.js
101 ms
small-logo.png
67 ms
bg-web.jpg
3345 ms
bg-zac.jpg
3457 ms
line-dashed.gif
3410 ms
icn-yellowring.gif
3458 ms
bg-navi-about.jpg
3470 ms
105 ms
127 ms
collect
26 ms
collect
55 ms
18 ms
19 ms
jTuqQ-OPDr6.css
280 ms
n370yiaI2G6.css
348 ms
dbNRhrdsQao.css
420 ms
1-xIpmMldel.css
546 ms
cCIltMJutxu.css
554 ms
mqajJoRXkq3.js
568 ms
x5F9OMjKyLw.js
616 ms
ICDbTSzjQEg.js
488 ms
TTCre3391I0.js
488 ms
njO1TPvGzoR.js
586 ms
b_6HNn_J2BZ.js
586 ms
7cm7D75Y0Sf.js
676 ms
rFmE1g6Dkoz.js
814 ms
336JejShbZp.js
629 ms
bg-navi-service.jpg
3319 ms
bg_footer.gif
3532 ms
bg-search_form.gif
3592 ms
btn-search_off.gif
3583 ms
conversion.js
1083 ms
528752_414333335299553_2021495003_n.jpg
196 ms
safe_image.php
196 ms
189048_139238612809028_7830876_n.jpg
189 ms
12662667_1004333186299562_650528659417159238_n.jpg
189 ms
12494875_996520577080823_8154146041783807506_n.jpg
189 ms
safe_image.php
192 ms
safe_image.php
193 ms
wL6VQj7Ab77.png
207 ms
s7jcwEQH7Sx.png
208 ms
QDwYpIaRyfG.png
205 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
71 ms
889 ms
fbevents.js
47 ms
23 ms
oro.co.jp 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
Links do not have a discernible name
oro.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
oro.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oro.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Oro.co.jp 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.
oro.co.jp
Open Graph data is detected on the main page of Oro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: