8.6 sec in total
424 ms
8.1 sec
87 ms
Visit starbucks.co.jp now to see the best up-to-date Starbucks content for Japan and also check out these interesting facts you probably never knew about starbucks.co.jp
スターバックス コーヒー ジャパンの公式ホームページ。新商品・メニュー情報、店舗検索、イベント情報、求人情報、エスプレッソドリンク用語の解説、コーヒー豆の解説、IR情報、CSR情報など。
Visit starbucks.co.jpWe analyzed Starbucks.co.jp page load time and found that the first response time was 424 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
starbucks.co.jp performance score
424 ms
849 ms
208 ms
460 ms
311 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 47% of them (61 requests) were addressed to the original Starbucks.co.jp, 19% (25 requests) were made to Sbcj.s3.amazonaws.com and 19% (25 requests) were made to D3vgbguy0yofad.cloudfront.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Starbucks.co.jp.
Page size can be reduced by 1.8 MB (47%)
3.9 MB
2.1 MB
In fact, the total size of Starbucks.co.jp main page is 3.9 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 37.6 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 37.6 kB or 78% of the original size.
Potential reduce by 548.6 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, Starbucks needs image optimization as it can save up to 548.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 877.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 877.6 kB or 80% of the original size.
Potential reduce by 352.1 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. Starbucks.co.jp needs all CSS files to be minified and compressed as it can save up to 352.1 kB or 86% of the original size.
Number of requests can be reduced by 63 (61%)
103
40
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Starbucks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
starbucks.co.jp
424 ms
www.starbucks.co.jp
849 ms
3144710084.js
208 ms
platform.css
460 ms
element.css
311 ms
component.css
890 ms
colorbox.css
334 ms
overwrite.css
801 ms
skin-welcome.css
327 ms
skin.css
340 ms
top.css
619 ms
html5shiv-printshiv.js
360 ms
jquery-1.11.1.min.js
906 ms
jquery.colorbox.js
645 ms
flipsnap.min.js
494 ms
domain.js
526 ms
common.js
1382 ms
logout.js
697 ms
cart.headercart.js
835 ms
mootools-1.1.2-nc.js
971 ms
GAParams.js
869 ms
ga_mxlib.js
890 ms
asyncga.js
1000 ms
relatedlink.js
1039 ms
component.js
2763 ms
top.js
1944 ms
conversion.js
16 ms
s_retargeting.js
571 ms
analytics.js
7 ms
sp.css
366 ms
collect
3 ms
collect
68 ms
overwrite-sp.css
302 ms
img-logo.png
161 ms
16spr1_coffee_wb.jpg
499 ms
16spr1_tribute_wb.jpg
176 ms
16winter2_wb_Reserve.jpg
330 ms
bg-arrow-news-prev-meganavi.png
331 ms
bg-arrow-news-next-meganavi.png
340 ms
img-icon-close-maganavi.png
346 ms
img-icon-close-maganavi-sp.png
337 ms
16spr1_cafe_wb.jpg
463 ms
16spr1_gift_wb.jpg
3394 ms
img-icon-question-maganavi.png
500 ms
logo.png
993 ms
img-sns-line-sp.png
508 ms
img-sns-tw-sp.png
617 ms
img-sns-fb-sp.png
661 ms
img-sp-icon-close.png
662 ms
16spr1_topkv_cafe.jpg
674 ms
img-arrow-prev-exnav.png
770 ms
img-arrow-next-exnav.png
824 ms
pickup_member.jpg
826 ms
pickup_recruit.jpg
838 ms
img-icon-onlinestore-cart-on.png
923 ms
img-icon-onlinestore-cart-on-sp.png
990 ms
img-icon-onlinestore-cart.png
988 ms
img-icon-onlinestore-cart-sp.png
1003 ms
img-nav-8.png
1080 ms
img-nav-1.png
1151 ms
img-nav-2.png
1152 ms
img-nav-3.png
1154 ms
img-nav-4.png
1172 ms
img-nav-5.png
1233 ms
img-nav-6.png
1315 ms
img-nav-7.png
1316 ms
img-nav-btn-blog-pc.png
1319 ms
img-nav-btn-blog-sp.png
1336 ms
all.js
41 ms
56 ms
img-nav-btn-twitter-pc.png
1379 ms
bg-global-header-pc-160215.jpg
316 ms
bg-meganav-160215-pc.jpg
607 ms
widgets.js
82 ms
bg-icon-gototop.png
174 ms
66 ms
75 ms
xd_arbiter.php
61 ms
xd_arbiter.php
83 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
141 ms
getNickName.php
809 ms
img-nav-btn-twitter-sp.png
1308 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
51 ms
img-nav-btn-facebook-pc.png
1154 ms
img-nav-btn-facebook-sp.png
1158 ms
img-nav-btn-mixi-pc.png
1172 ms
img-nav-btn-mixi-sp.png
1207 ms
img-nav-btn-instagram-pc.png
1302 ms
jot
93 ms
img-nav-btn-instagram-sp.png
1187 ms
img-nav-btn-pinterest-pc.png
1156 ms
img-nav-btn-pinterest-sp.png
1174 ms
img-nav-btn-sumally-pc.png
1191 ms
img-nav-btn-sumally-sp.png
1193 ms
img-nav-8.svg
1151 ms
img-nav-1.svg
1154 ms
16spr1_topkv_cafe.jpg
389 ms
img-nav-2.svg
1069 ms
img-nav-3.svg
1082 ms
pickup_member.jpg
210 ms
img-nav-4.svg
1145 ms
img-nav-5.svg
1149 ms
pickup_recruit.jpg
408 ms
img-nav-6.svg
1058 ms
img-nav-7.svg
1080 ms
img-nav-8.png
174 ms
img-nav-1.png
172 ms
img-nav-2.png
387 ms
img-nav-3.png
354 ms
img-nav-4.png
1674 ms
img-nav-5.png
338 ms
img-nav-6.png
170 ms
img-nav-7.png
323 ms
img-nav-btn-blog-pc.png
328 ms
img-nav-btn-blog-sp.png
359 ms
img-nav-btn-twitter-pc.png
328 ms
img-nav-btn-twitter-sp.png
411 ms
img-nav-btn-facebook-pc.png
329 ms
img-nav-btn-facebook-sp.png
334 ms
img-nav-btn-mixi-pc.png
359 ms
img-nav-btn-mixi-sp.png
339 ms
img-nav-btn-instagram-pc.png
500 ms
img-nav-btn-instagram-sp.png
339 ms
img-nav-btn-pinterest-pc.png
379 ms
img-nav-btn-pinterest-sp.png
382 ms
img-nav-btn-sumally-pc.png
358 ms
img-nav-btn-sumally-sp.png
341 ms
Cart.html
913 ms
share_button.php
65 ms
vpc6VNjRPXV.js
56 ms
LVx-xkvaJ0b.png
100 ms
starbucks.co.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Starbucks.co.jp 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 Starbucks.co.jp 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.
starbucks.co.jp
Open Graph data is detected on the main page of Starbucks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: