7.3 sec in total
341 ms
6.8 sec
155 ms
Visit bunkado.com now to see the best up-to-date Bunkado content for Japan and also check out these interesting facts you probably never knew about bunkado.com
安全・安心な食材をお客様に提供します。 フレッシュフードストア スーパーマーケット文化堂
Visit bunkado.comWe analyzed Bunkado.com page load time and found that the first response time was 341 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
bunkado.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value17.8 s
0/100
25%
Value15.7 s
0/100
10%
Value3,090 ms
2/100
30%
Value0.228
55/100
15%
Value18.1 s
3/100
10%
341 ms
753 ms
715 ms
694 ms
680 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 56% of them (27 requests) were addressed to the original Bunkado.com, 17% (8 requests) were made to Youtube.com and 8% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Bunkado.com.
Page size can be reduced by 114.8 kB (19%)
608.9 kB
494.2 kB
In fact, the total size of Bunkado.com main page is 608.9 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. 45% of websites need less resources to load. Images take 324.0 kB which makes up the majority of the site volume.
Potential reduce by 7.4 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 7.4 kB or 67% of the original size.
Potential reduce by 57.8 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, Bunkado needs image optimization as it can save up to 57.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 36.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 36.7 kB or 18% of the original size.
Potential reduce by 12.9 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. Bunkado.com needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 17% of the original size.
Number of requests can be reduced by 10 (24%)
42
32
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bunkado. 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 from 4 to 1 for CSS and as a result speed up the page load time.
bunkado.com
341 ms
www.bunkado.com
753 ms
base_index.css
715 ms
index_info.css
694 ms
douga.css
680 ms
js
58 ms
jquery-3.5.1.js
21 ms
lity.css
692 ms
lity.js
768 ms
top-umekomi.php
1866 ms
GoDKuLsIaLo
158 ms
IDJRgnttLPM
537 ms
bg.jpg
893 ms
header2_h.jpg
1070 ms
bunkado_rogo2-2.png
982 ms
bana_togoshiginza_opening.jpg
1068 ms
chirashi_tenpo_02.png
981 ms
membership02.png
1822 ms
netshopping.png
2995 ms
osusume02.png
2844 ms
youbibetsu02.png
2810 ms
recipe03.png
2813 ms
tokusimaru03.png
3776 ms
saiyou08.png
4032 ms
syain02.png
3882 ms
part02.png
3981 ms
new_rec02.png
4439 ms
kigyo05.png
4268 ms
message02.png
4458 ms
company02.png
4597 ms
activity02.png
4664 ms
seal.min.js
458 ms
www-player.css
13 ms
www-embed-player.js
44 ms
base.js
73 ms
ad_status.js
260 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
236 ms
embed.js
155 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
50 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
55 ms
id
29 ms
Create
116 ms
Create
117 ms
GenerateIT
18 ms
GenerateIT
20 ms
log_event
29 ms
log_event
18 ms
224 ms
bunkado.com accessibility score
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
<frame> or <iframe> elements do not have a title
bunkado.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
Page has valid source maps
bunkado.com SEO score
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 Bunkado.com 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 Bunkado.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.
bunkado.com
Open Graph description is not detected on the main page of Bunkado. 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: