7.1 sec in total
582 ms
6.2 sec
314 ms
Visit bs-oya.com now to see the best up-to-date Bs Oya content and also check out these interesting facts you probably never knew about bs-oya.com
乳酸菌生成エキス智通(ちつう)は、自分が持っている乳酸菌を増やすパワーがあります。智通で善玉菌を増やして健康に。智通の通販《送料・代引手数料無料》。
Visit bs-oya.comWe analyzed Bs-oya.com page load time and found that the first response time was 582 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
bs-oya.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value7.4 s
4/100
25%
Value5.4 s
57/100
10%
Value20 ms
100/100
30%
Value0.218
57/100
15%
Value4.7 s
80/100
10%
582 ms
716 ms
539 ms
361 ms
28 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 96% of them (64 requests) were addressed to the original Bs-oya.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Bs-oya.com.
Page size can be reduced by 42.9 kB (56%)
77.2 kB
34.3 kB
In fact, the total size of Bs-oya.com main page is 77.2 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. 20% of websites need less resources to load. CSS take 33.3 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.9 kB or 67% of the original size.
Potential reduce by 1.0 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, Bs Oya needs image optimization as it can save up to 1.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.4 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 28.6 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. Bs-oya.com needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 86% of the original size.
Number of requests can be reduced by 3 (5%)
65
62
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bs Oya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
bs-oya.com
582 ms
www.bs-oya.com
716 ms
bsoya.css
539 ms
common.js
361 ms
jquery.min.js
28 ms
opacity-rollover2.1.js
389 ms
reset.css
194 ms
analytics.js
69 ms
logo.gif
353 ms
header_tel3.gif
369 ms
hnavi3.gif
362 ms
hnavi2.gif
363 ms
hnavi1.gif
381 ms
gnavibg.gif
382 ms
gnavi1o.gif
695 ms
gnavi2.gif
706 ms
gnavi3.gif
721 ms
gnavi4.gif
754 ms
gnavi5.gif
733 ms
catch_txt.gif
756 ms
item1b.gif
1373 ms
item2b.gif
1397 ms
item_bg.gif
1097 ms
item1s.gif
1115 ms
item2s.gif
1112 ms
item3s.gif
1113 ms
item4s.gif
1439 ms
index_topics.gif
1454 ms
side_bnr.gif
1996 ms
side_msg_header.gif
1830 ms
side_msg_bottom.gif
2120 ms
footerbg1.gif
1729 ms
footerbg2.gif
1788 ms
footer_index_about_shopping.gif
1795 ms
footer_index_shiharai.gif
2112 ms
footer_lbl_daibiki.gif
2142 ms
footer_img_yamato11.gif
2157 ms
footer_img_yamato12.gif
2202 ms
footer_img_yamato13.gif
2357 ms
footer_img_emoney.gif
2452 ms
footer_lbl_card.gif
2462 ms
footer_img_card.gif
2509 ms
footer_lbl_yucho.gif
2515 ms
footer_img_yucho.gif
2512 ms
collect
13 ms
footer_lbl_convini.gif
2348 ms
footer_img_convini.gif
2736 ms
footer_index_otodoke.gif
2488 ms
footer_img_yamato2.gif
2517 ms
footer_lbl_otodoke.gif
2502 ms
footer_img_otodoke.gif
2951 ms
footer_index_soryo.gif
2353 ms
footer_img_soryo_daibiki_fr.gif
2494 ms
footer_index_henpin.gif
2499 ms
footer_tel.gif
2503 ms
footer_sp.gif
2681 ms
footer_qr.gif
3045 ms
footer_address.gif
2461 ms
pagetop.png
2458 ms
copyright.png
2471 ms
hnavi3o.gif
176 ms
hnavi2o.gif
339 ms
hnavi1o.gif
338 ms
gnavi2o.gif
354 ms
gnavi3o.gif
367 ms
gnavi4o.gif
364 ms
gnavi5o.gif
534 ms
bs-oya.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [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
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.
bs-oya.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
bs-oya.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bs-oya.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Bs-oya.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.
bs-oya.com
Open Graph description is not detected on the main page of Bs Oya. 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: