5.3 sec in total
557 ms
4.1 sec
702 ms
Visit buzz-house.com now to see the best up-to-date Buzz House content for Japan and also check out these interesting facts you probably never knew about buzz-house.com
buzzhouse design/バズハウスデザイン~ハンドメイドレザーケース~
Visit buzz-house.comWe analyzed Buzz-house.com page load time and found that the first response time was 557 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
buzz-house.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value15.9 s
0/100
25%
Value8.4 s
18/100
10%
Value2,560 ms
4/100
30%
Value0.522
15/100
15%
Value22.1 s
1/100
10%
557 ms
172 ms
330 ms
499 ms
330 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 53% of them (62 requests) were addressed to the original Buzz-house.com, 18% (21 requests) were made to Static.xx.fbcdn.net and 5% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Buzz-house.com.
Page size can be reduced by 323.8 kB (3%)
12.0 MB
11.7 MB
In fact, the total size of Buzz-house.com main page is 12.0 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. Only a small number of websites need less resources to load. Images take 11.5 MB which makes up the majority of the site volume.
Potential reduce by 31.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 31.9 kB or 79% of the original size.
Potential reduce by 255.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. Buzz House images are well optimized though.
Potential reduce by 34.3 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 1.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. Buzz-house.com has all CSS files already compressed.
Number of requests can be reduced by 44 (41%)
108
64
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzz House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
buzz-house.com
557 ms
base.css
172 ms
top.css
330 ms
jquery.js
499 ms
script.js
330 ms
common.js
332 ms
jquery.mousewheel-3.0.4.pack.js
339 ms
jquery.fancybox-1.3.4.pack.js
341 ms
jquery.fancybox-1.3.4.css
494 ms
slick.min.js
495 ms
slick.css
497 ms
slick-theme.css
519 ms
platform.js
23 ms
css
30 ms
tag.png
197 ms
logo_org.png
193 ms
outdoor.jpg
1138 ms
main6.png
1754 ms
main7.png
1525 ms
main8.png
1758 ms
main3.png
1600 ms
main4.png
1790 ms
main5.png
1951 ms
main1.png
1626 ms
main2.png
1937 ms
buzzhouse_outdoor.jpg
1794 ms
clothwork.jpg
1929 ms
kodawari1.png
1949 ms
kodawari2.png
2122 ms
kodawari3.png
1983 ms
thum_iphone.png
2100 ms
thum_macbook.png
2105 ms
thum_ipad.png
2123 ms
thum_ipod.png
2123 ms
thum_lavie.png
2156 ms
thum_vaio.png
2270 ms
thum_xeperia.png
2277 ms
thum_mini.png
2299 ms
thum_stationery.png
2294 ms
thum_camp.png
2304 ms
thum_old.png
2328 ms
banner_outlet.png
2437 ms
banner_oversea.png
2443 ms
banner_collabo.jpg
2463 ms
bnt_fb.png
2468 ms
btn_twitter.png
2473 ms
card_jcb.png
2492 ms
card_visa.png
2600 ms
card_master.png
2608 ms
5oq7dBh0agE
192 ms
page.php
254 ms
amex-logomark-img-03.gif
2607 ms
widgets.js
144 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
47 ms
fastbutton
44 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
71 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
70 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
71 ms
slick.woff
2452 ms
postmessageRelay
103 ms
card_diners.png
2436 ms
www-player.css
12 ms
www-embed-player.js
64 ms
base.js
130 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
790 ms
developers.google.com
846 ms
r8xWWK5RS5M.css
50 ms
vGTeM7AQu12.css
61 ms
BZdxwZYnZtY.css
484 ms
Aq3fWRqzWdY.js
497 ms
vxmlpLbAeCj.js
490 ms
o1ndYS2og_B.js
490 ms
_02W6YRik00.js
492 ms
p55HfXW__mM.js
491 ms
k_PjgALRjoR.js
492 ms
qJoe20iyDr0.js
496 ms
CwUW1mXVRXb.js
494 ms
CGo9cU7zbWd.js
566 ms
EcPi7SsydEO.js
493 ms
_iENDDwY6Fe.js
578 ms
ps0npFgHj8z.js
564 ms
kww4kc8mdjt.js
577 ms
HzxD9aAXSyD.js
593 ms
Q-X-GXL_I_5.js
592 ms
3604799710-postmessagerelay.js
454 ms
rpc:shindig_random.js
16 ms
ad_status.js
495 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
437 ms
embed.js
247 ms
239130944_6037798136292727_6463235473882001984_n.jpg
146 ms
300972409_507927601335313_405635191040566500_n.jpg
181 ms
UXtr_j2Fwe-.png
59 ms
cb=gapi.loaded_0
53 ms
OcmMPieTVMv.js
83 ms
CK719qJHOVF.js
88 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
66 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
68 ms
settings
275 ms
Create
231 ms
id
31 ms
card_uc.png
1526 ms
card_saison.png
1244 ms
button.856debeac157d9669cf51e73a08fbc93.js
28 ms
GenerateIT
15 ms
embeds
45 ms
follow_button.2f70fb173b9000da126c79afe2098f02.en.html
43 ms
card_aeon.png
1182 ms
card_nicos.png
1177 ms
card_dc.png
1066 ms
card_ufj.png
1064 ms
card_tokyu.png
1040 ms
paypay_logo.png
1143 ms
main_bg.png
1017 ms
btn_back.png
1035 ms
btn_next.png
1039 ms
ajax-loader.gif
1040 ms
buzz-house.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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.
Definition list items are not wrapped in <dl> elements
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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 [lang] attribute
buzz-house.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
Browser errors were logged to the console
Page has valid source maps
buzz-house.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzz-house.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Buzz-house.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.
buzz-house.com
Open Graph description is not detected on the main page of Buzz House. 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: