11 sec in total
2.2 sec
7.9 sec
893 ms
Visit o-ohsho.jp now to see the best up-to-date O Ohsho content for Japan and also check out these interesting facts you probably never knew about o-ohsho.jp
Visit o-ohsho.jpWe analyzed O-ohsho.jp page load time and found that the first response time was 2.2 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
o-ohsho.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value12.7 s
0/100
25%
Value14.9 s
1/100
10%
Value350 ms
73/100
30%
Value0.269
45/100
15%
Value12.1 s
16/100
10%
2173 ms
330 ms
494 ms
334 ms
333 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 73% of them (151 requests) were addressed to the original O-ohsho.jp, 1% (3 requests) were made to Image.rakuten.co.jp and 1% (3 requests) were made to Kdex004.deqwas.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain O-ohsho.jp.
Page size can be reduced by 363.2 kB (13%)
2.9 MB
2.5 MB
In fact, the total size of O-ohsho.jp main page is 2.9 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 68.5 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 15.4 kB, which is 18% 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 68.5 kB or 82% of the original size.
Potential reduce by 5.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. O Ohsho images are well optimized though.
Potential reduce by 203.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 203.7 kB or 71% of the original size.
Potential reduce by 85.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. O-ohsho.jp needs all CSS files to be minified and compressed as it can save up to 85.4 kB or 84% of the original size.
Number of requests can be reduced by 59 (32%)
183
124
The browser has sent 183 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O Ohsho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
o-ohsho.jp
2173 ms
import.css
330 ms
css.js
494 ms
navi.js
334 ms
win_op.js
333 ms
site.js
706 ms
jquery-1.11.1.min.js
1640 ms
eccube.js
1027 ms
jquery.bxslider.min.js
857 ms
ah-placeholder.js
656 ms
jquery-ui.min.js
31 ms
jquery.cookie.js
819 ms
jquery.switchHat.js
880 ms
ticker.js
974 ms
common.js
982 ms
heightLine.js
1020 ms
jquery.socialbutton-1.8.1.js
1409 ms
social-tracking.js
1137 ms
reset.css
823 ms
common.css
1026 ms
contents.css
1195 ms
table.css
978 ms
bloc.css
1314 ms
bloc_alpha.css
1141 ms
popup.css
1190 ms
newtop.css
1263 ms
jquery.bxslider.css
1304 ms
print.css
1354 ms
layout.css
1358 ms
layout_sp.css
1440 ms
special_sale_layout.css
1466 ms
new_year_sale2016_layout.css
1474 ms
analytics.js
142 ms
pointbg_oroshin.jpg
290 ms
head_bg.jpg
181 ms
logo.jpg
182 ms
menu.jpg
532 ms
ticker_bg.jpg
184 ms
ticker_title.jpg
183 ms
line.jpg
184 ms
payment_way_pc.gif
327 ms
headc_1r.jpg
330 ms
headc_2r.jpg
331 ms
headc_3r.jpg
335 ms
headc_4r.jpg
335 ms
headc_5r.jpg
489 ms
headc_6r.jpg
493 ms
s_bt.jpg
496 ms
yokubari_slide.jpg
1158 ms
mar2016_960x390.jpg
1810 ms
yukishio_slide.jpg
1144 ms
yokubari_slides.jpg
656 ms
mar2016_238x90.jpg
985 ms
yukishio_slides.jpg
706 ms
teiban_title.jpg
821 ms
teiban_img1.jpg
884 ms
teiban_img2.jpg
984 ms
teiban_img3.jpg
1060 ms
teiban_img4.jpg
1148 ms
teiban_img5.jpg
1150 ms
line_margin.jpg
1237 ms
bngroupa_1.jpg
1306 ms
bngroupa_2.jpg
1311 ms
bngroupa_3.jpg
1642 ms
bngroupa_4.jpg
1318 ms
bngroupa_5.jpg
1590 ms
selection322x123.jpg
1469 ms
butaman322x123.jpg
1476 ms
gyok322x123.jpg
1484 ms
otameshi_slide.jpg
289 ms
otameshi8ver194x70.jpg
219 ms
first_time.jpg
1544 ms
top.js
339 ms
widgets.js
21 ms
collect
29 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
25 ms
collect
68 ms
login_title.jpg
1468 ms
email.jpg
1478 ms
pass.jpg
1593 ms
forget_bg.jpg
1623 ms
btn_bloc_login.jpg
1634 ms
like.php
160 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
15 ms
ga-audiences
37 ms
magazine_bn.jpg
1496 ms
magazine_entry.jpg
1501 ms
magazine_detail.jpg
1620 ms
otoriyose_bn.jpg
1635 ms
ranking_title.jpg
1639 ms
Dt46LmMjzaB.js
23 ms
LVx-xkvaJ0b.png
18 ms
jot
81 ms
KcDeqwasAgent.js
156 ms
ranking_bg.jpg
1487 ms
rank1_bg.jpg
1487 ms
rank1_bn.jpg
1492 ms
rank1_title.jpg
1600 ms
Collection.aspx
160 ms
rank2_bg.jpg
1476 ms
rank2_bn.jpg
1433 ms
rtbsync.js
8 ms
Sync.aspx
356 ms
Sync.aspx
329 ms
Sync.aspx
375 ms
Sync.aspx
338 ms
Sync.aspx
303 ms
Sync.aspx
308 ms
Sync.aspx
303 ms
Sync.aspx
317 ms
Sync.aspx
312 ms
Sync.aspx
314 ms
Sync.aspx
296 ms
Sync.aspx
317 ms
Sync.aspx
315 ms
Sync.aspx
302 ms
Sync.aspx
304 ms
Sync.aspx
296 ms
DynamicRetargetUserSync.aspx
322 ms
Collection.aspx
334 ms
rank2_title.jpg
1317 ms
rank3_bg.jpg
1258 ms
rank3_bn.jpg
1167 ms
rank3_title.jpg
1320 ms
package_size.jpg
1235 ms
sync
9 ms
319 ms
sync
585 ms
cs
345 ms
tap.php
5 ms
setuid
23 ms
cookiesync
327 ms
sd
5 ms
Sync.aspx
483 ms
search_title.jpg
1159 ms
btn_bloc_search.jpg
1153 ms
category_title1.jpg
1155 ms
category_bg.jpg
1148 ms
category_title2.jpg
1221 ms
category_title3.jpg
1159 ms
category_title4.jpg
1155 ms
category_title5.jpg
1161 ms
mapuser
162 ms
Collection.aspx
153 ms
Collection.aspx
157 ms
Collection.aspx
148 ms
category_title6.jpg
997 ms
info_company.jpg
1001 ms
info_privacy.jpg
1136 ms
info_law.jpg
1038 ms
Collection.aspx
158 ms
pixel
20 ms
Collection.aspx
158 ms
mobile_bn.jpg
995 ms
pixel
16 ms
contents_line.jpg
991 ms
alti_bn.jpg
1172 ms
ranger_bn2.jpg
1537 ms
Collection.aspx
154 ms
Collection.aspx
162 ms
1505chibo_bn.jpg
1180 ms
contents_title.jpg
994 ms
kantan.jpg
1322 ms
recipe_bn.jpg
1154 ms
anshin_bn.jpg
1140 ms
recommend_title.jpg
1156 ms
Collection.aspx
377 ms
resize_image.php
1339 ms
detail_btn.jpg
1165 ms
resize_image.php
1275 ms
resize_image.php
1365 ms
resize_image.php
1448 ms
resize_image.php
1423 ms
resize_image.php
1423 ms
resize_image.php
1372 ms
resize_image.php
1432 ms
resize_image.php
1494 ms
resize_image.php
1542 ms
resize_image.php
1537 ms
resize_image.php
1464 ms
resize_image.php
1525 ms
page_top.jpg
1431 ms
footinfo_title.jpg
1493 ms
ymail_btn.jpg
1544 ms
footpay_title.jpg
1535 ms
footpay_image2.jpg
1436 ms
rakuten_id.gif
1458 ms
kessai_banner_001.gif
1495 ms
footdelivery_title.jpg
1535 ms
footdelivery_image.jpg
1534 ms
footprivacy_title.jpg
1535 ms
footbusiness_title.jpg
1437 ms
footreturn_title.jpg
1458 ms
footcontact_title.jpg
1496 ms
magazine_entry_on.jpg
165 ms
magazine_detail_on.jpg
166 ms
rank1_bn_on.jpg
183 ms
rank2_bn_on.jpg
168 ms
rank3_bn_on.jpg
167 ms
package_size_on.jpg
172 ms
info_company_on.jpg
326 ms
info_privacy_on.jpg
328 ms
info_law_on.jpg
330 ms
recipe_bn_on.jpg
495 ms
anshin_bn_on.jpg
337 ms
detail_btn_on.jpg
355 ms
page_top_on.jpg
489 ms
ymail_btn_on.jpg
493 ms
o-ohsho.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
o-ohsho.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
o-ohsho.jp SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O-ohsho.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 O-ohsho.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.
o-ohsho.jp
Open Graph description is not detected on the main page of O Ohsho. 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: