5.6 sec in total
820 ms
4.2 sec
524 ms
Welcome to yumekoobou.com homepage info - get ready to check Yumekoobou best content for Japan right away, or after learning these important things about yumekoobou.com
京都新門前にある古美術と骨董のお店です。素晴らしい日本の美術品を幅広く取り揃えております。選りすぐりの煎茶道具も多数ご覧いただけます。
Visit yumekoobou.comWe analyzed Yumekoobou.com page load time and found that the first response time was 820 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.
yumekoobou.com performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value3.7 s
57/100
25%
Value4.5 s
72/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
820 ms
1223 ms
528 ms
53 ms
379 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 44% of them (38 requests) were addressed to the original Yumekoobou.com, 16% (14 requests) were made to Google.com and 15% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Yumekoobou.com.
Page size can be reduced by 721.1 kB (34%)
2.1 MB
1.4 MB
In fact, the total size of Yumekoobou.com main page is 2.1 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 12.3 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 4.6 kB, which is 29% 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 12.3 kB or 76% of the original size.
Potential reduce by 21.2 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. Yumekoobou images are well optimized though.
Potential reduce by 545.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 545.3 kB or 65% of the original size.
Potential reduce by 142.4 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. Yumekoobou.com needs all CSS files to be minified and compressed as it can save up to 142.4 kB or 83% of the original size.
Number of requests can be reduced by 31 (39%)
80
49
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yumekoobou. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
yumekoobou.com
820 ms
bootstrap.min.css
1223 ms
common.css
528 ms
font-awesome.min.css
53 ms
lightbox.css
379 ms
jquery.min.js
97 ms
bootstrap.min.js
591 ms
masonry.pkgd.min.js
56 ms
imagesloaded.js
377 ms
ie10-viewport-bug-workaround.js
394 ms
ie-emulation-modes-warning.js
567 ms
google_analytics.js
554 ms
jquery.infinitescroll.min.js
771 ms
g_fadein.js
700 ms
fadein.js
733 ms
SubFontJS.js
753 ms
masonry.js
790 ms
backto.js
875 ms
analytics.js
78 ms
ZOkF8x2AU7s
720 ms
embed
189 ms
close.png
216 ms
loading.gif
192 ms
prev.png
193 ms
next.png
202 ms
yafuoku.png
205 ms
g_000.jpg
1326 ms
g_147s.jpg
453 ms
g_140s.jpg
630 ms
g_119s.jpg
792 ms
g_146s.jpg
629 ms
g_141s.jpg
658 ms
g_101s.jpg
657 ms
stage3_img1.jpg
1403 ms
stage3_img2.jpg
2280 ms
stage3_img3.jpg
1328 ms
stage4_img1.jpg
850 ms
stage4_img2.jpg
978 ms
stage4_img3.jpg
1050 ms
yafuoku_foot.png
1166 ms
rakuten.png
1254 ms
qr_wechat.png
1352 ms
pagetop.png
1459 ms
glyphicons-halflings-regular.woff
1501 ms
fontawesome-webfont.woff
16 ms
collect
18 ms
js
88 ms
init_embed.js
35 ms
common.js
63 ms
map.js
62 ms
google4.png
88 ms
overlay.js
86 ms
util.js
119 ms
onion.js
114 ms
search_impl.js
118 ms
stats.js
132 ms
openhand_8_8.cur
90 ms
ViewportInfoService.GetViewportInfo
102 ms
ViewportInfoService.GetViewportInfo
78 ms
kh
224 ms
transparent.png
113 ms
controls.js
48 ms
ViewportInfoService.GetViewportInfo
95 ms
css
117 ms
entity11.png
70 ms
vt
151 ms
vt
218 ms
vt
129 ms
vt
153 ms
vt
149 ms
vt
122 ms
vt
197 ms
vt
200 ms
vt
196 ms
vt
230 ms
vt
220 ms
vt
269 ms
vt
248 ms
mapcnt6.png
50 ms
sv5.png
50 ms
tmapctrl.png
90 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
29 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
48 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
49 ms
AuthenticationService.Authenticate
25 ms
yumekoobou.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 [lang] attribute
yumekoobou.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yumekoobou.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yumekoobou.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 Yumekoobou.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.
yumekoobou.com
Open Graph description is not detected on the main page of Yumekoobou. 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: