7 sec in total
535 ms
6.1 sec
354 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 535 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
buzz-house.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.3 s
5/100
25%
Value7.8 s
24/100
10%
Value1,160 ms
22/100
30%
Value0.474
18/100
15%
Value16.7 s
5/100
10%
535 ms
173 ms
314 ms
334 ms
356 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 70% of them (82 requests) were addressed to the original Buzz-house.com, 9% (10 requests) were made to Apis.google.com and 4% (5 requests) were made to Sync5-res.digitalstage.jp. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Buzz-house.com.
Page size can be reduced by 793.6 kB (22%)
3.6 MB
2.8 MB
In fact, the total size of Buzz-house.com main page is 3.6 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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 45.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 45.9 kB or 81% of the original size.
Potential reduce by 126.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. Buzz House images are well optimized though.
Potential reduce by 311.6 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 311.6 kB or 72% of the original size.
Potential reduce by 310.2 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 needs all CSS files to be minified and compressed as it can save up to 310.2 kB or 88% of the original size.
Number of requests can be reduced by 65 (57%)
114
49
The browser has sent 114 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 30 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
buzz-house.com
535 ms
style.css
173 ms
_else.css
314 ms
style.css
334 ms
index.css
356 ms
script.js
361 ms
common.css
191 ms
pagelayout.css
453 ms
printlayout.css
326 ms
blockskin.css
557 ms
wp_style.css
192 ms
overwrite.css
207 ms
style.css
194 ms
theme.css
171 ms
_else.css
175 ms
_else.css
163 ms
jquery-1.8.3.min.js
364 ms
jquery.easing.1.3.js
169 ms
head.load.min.js
184 ms
movie.js
181 ms
parts.js
321 ms
fx.js
666 ms
override.js
341 ms
load.js
358 ms
ga.js
6 ms
Cafe_bg_buzz.png
207 ms
_area_header.css
181 ms
_area_billboard.css
203 ms
_area_main.css
191 ms
_area_side_a.css
191 ms
_area_side_b.css
200 ms
_area_footer.css
290 ms
_block_header.css
335 ms
_block_billboard.css
357 ms
_block_main.css
369 ms
_block_side_a.css
377 ms
_block_side_b.css
379 ms
_block_footer.css
455 ms
engine.js
534 ms
sync.css
769 ms
json.js
575 ms
sync.js
1347 ms
__utm.gif
10 ms
buzzhouse20rogo.jpg
673 ms
83r838b837b815b83hiphone6.jpg
1809 ms
83j815b837e83b83gtop.png
2554 ms
83r838b837b815b83hiphone6plusbk.jpg
1092 ms
83r838b837b815b83hiphone6plusblown.jpg
1308 ms
lavie83r838b837b815b83h.jpg
1624 ms
airpro.jpg
1535 ms
ipad.jpg
1272 ms
BB04.jpg
1827 ms
iphone83t83f838b83g.jpg
1672 ms
83t83f838b83gipad.jpg
1886 ms
83t83f838b83g83x837d83z.jpg
2117 ms
BB01.jpg
2045 ms
h4.gif
2242 ms
hr.gif
2045 ms
_English1.gif
2096 ms
macbook12lether.jpg
2206 ms
feltmacbook12.jpg
2281 ms
topsiphone6.jpg
2290 ms
topsiphone6plus.jpg
2313 ms
02.jpg
2384 ms
A_macpro15retina.png
2798 ms
top_macbook.png
2567 ms
Top_03.jpg
2488 ms
Top_02.jpg
2311 ms
03.jpg
2402 ms
83j815b837e83b83g83o83i815b.jpg
2469 ms
83r8389837b83x83g838983b83v.jpg
3614 ms
Top_04.jpg
2737 ms
06.jpg
2666 ms
Down_01.jpg
2481 ms
Down_02.jpg
2508 ms
Down_03.jpg
2804 ms
Down_04.jpg
2616 ms
product20index.png
2600 ms
point_A.png
2615 ms
nivo-slider.css
2529 ms
custom-nivo-slider.css
2110 ms
jquery.nivo.slider.pack.js
1950 ms
information.png
1990 ms
jquery.socialbutton.js
543 ms
jquery.socialbutton.js
570 ms
spinner.gif
142 ms
sdk.js
269 ms
100px.png
1813 ms
118 ms
151 ms
xd_arbiter.php
219 ms
xd_arbiter.php
446 ms
user_timeline.json
56 ms
widgets.js
9 ms
plusone.js
49 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
17 ms
widgets.js
8 ms
plusone.js
68 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
39 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
44 ms
fastbutton
95 ms
like.php
72 ms
postmessageRelay
46 ms
rs=AGLTcCMZnOZwP_q6pCwQUYCN0BCxu9nBPg
12 ms
qeKvIRsJabD.js
486 ms
LVx-xkvaJ0b.png
547 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
28 ms
3193398744-postmessagerelay.js
32 ms
rpc:shindig_random.js
54 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
36 ms
cb=gapi.loaded_0
4 ms
jot.html
2 ms
loading.gif
169 ms
arrows.png
180 ms
bullets.png
170 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
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
JA
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 it matches the claimed language. 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 data is detected on the main page of Buzz House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: