6.4 sec in total
911 ms
5.3 sec
164 ms
Click here to check amazing Bungoff content for Japan. Otherwise, check out these important facts you probably never knew about bungoff.com
激安文具通販サイトです。
Visit bungoff.comWe analyzed Bungoff.com page load time and found that the first response time was 911 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
bungoff.com performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value16.2 s
0/100
25%
Value20.4 s
0/100
10%
Value110 ms
97/100
30%
Value0
100/100
15%
Value17.1 s
4/100
10%
911 ms
349 ms
387 ms
1218 ms
530 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Bungoff.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajaxzip3.googlecode.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Bungoff.com.
Page size can be reduced by 101.1 kB (44%)
228.0 kB
126.9 kB
In fact, the total size of Bungoff.com main page is 228.0 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. 15% of websites need less resources to load. Javascripts take 118.8 kB which makes up the majority of the site volume.
Potential reduce by 15.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 2.4 kB, which is 12% 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 15.5 kB or 77% of the original size.
Potential reduce by 0 B
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. Bungoff images are well optimized though.
Potential reduce by 64.0 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 64.0 kB or 54% of the original size.
Potential reduce by 21.5 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. Bungoff.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 72% of the original size.
Number of requests can be reduced by 26 (43%)
61
35
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bungoff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
bungoff.com
911 ms
colorbox.css
349 ms
import.css
387 ms
jquery-1.4.2.min.js
1218 ms
eccube.js
530 ms
eccube.legacy.js
544 ms
jquery.colorbox-min.js
741 ms
ajaxzip3-https.js
98 ms
plg_ajaxzip3.js
377 ms
reset.css
377 ms
common.css
859 ms
contents.css
1130 ms
table.css
842 ms
bloc.css
1100 ms
bloc_alpha.css
1026 ms
popup.css
1197 ms
print.css
1424 ms
logo.gif
526 ms
btn_header_home.jpg
380 ms
btn_header_mypage.jpg
401 ms
btn_header_entry.jpg
403 ms
btn_header_cart.jpg
411 ms
btn_bloc_search.jpg
423 ms
free.jpg
1089 ms
bg_btn_list.jpg
756 ms
ico_arrow_02.gif
776 ms
101.jpg
792 ms
175.jpg
799 ms
177.jpg
901 ms
171.jpg
1156 ms
130.jpg
1131 ms
112.jpg
1176 ms
132.jpg
1190 ms
103.jpg
1254 ms
116.jpg
1457 ms
150.jpg
1485 ms
152.jpg
1508 ms
154.jpg
1552 ms
121.jpg
1587 ms
102.jpg
1629 ms
140.jpg
1815 ms
117.jpg
1863 ms
118.jpg
1905 ms
119.jpg
1950 ms
104.jpg
1974 ms
162.jpg
1982 ms
164.jpg
2140 ms
160.jpg
2230 ms
105.jpg
2295 ms
115.jpg
2343 ms
120.jpg
2370 ms
107.jpg
2357 ms
analytics.js
26 ms
114.jpg
2484 ms
collect
14 ms
k2.jpg
2212 ms
172.jpg
2303 ms
173.jpg
2287 ms
174.jpg
2325 ms
bg_btn_bloc_02.jpg
2343 ms
tit_bloc_news.png
2430 ms
line_dot_01.gif
2168 ms
bungoff.com accessibility score
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.
bungoff.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
bungoff.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 doesn't use 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 Bungoff.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 Bungoff.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.
bungoff.com
Open Graph description is not detected on the main page of Bungoff. 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: