6.4 sec in total
532 ms
5.7 sec
172 ms
Click here to check amazing Fujiya Peko content for Japan. Otherwise, check out these important facts you probably never knew about fujiya-peko.co.jp
株式会社不二家のウェブサイト。季節のケーキやギフト商品のスイーツ、ルック・ミルキー・カントリーマアムなどのお菓子の紹介、不二家の安心・安全の取り組み、会社・IR情報、キャンペーン情報、店舗検索、ペコちゃん・ポコちゃんの情報など。
Visit fujiya-peko.co.jpWe analyzed Fujiya-peko.co.jp page load time and found that the first response time was 532 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fujiya-peko.co.jp performance score
532 ms
164 ms
483 ms
319 ms
322 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 96% of them (129 requests) were addressed to the original Fujiya-peko.co.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fujiya-peko.co.jp.
Page size can be reduced by 681.6 kB (30%)
2.3 MB
1.6 MB
In fact, the total size of Fujiya-peko.co.jp main page is 2.3 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 21.0 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 7.1 kB, which is 27% 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 21.0 kB or 80% of the original size.
Potential reduce by 201.5 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, Fujiya Peko needs image optimization as it can save up to 201.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 180.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 180.6 kB or 67% of the original size.
Potential reduce by 278.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. Fujiya-peko.co.jp needs all CSS files to be minified and compressed as it can save up to 278.5 kB or 86% of the original size.
Number of requests can be reduced by 66 (50%)
133
67
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fujiya Peko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
fujiya-peko.co.jp
532 ms
common.css
164 ms
prototype.js
483 ms
event.js
319 ms
rollover.js
322 ms
common.js
335 ms
news.js
337 ms
newsdata.js
407 ms
formcheck.js
478 ms
jquery.js
824 ms
gallary.js
502 ms
urchin.js
21 ms
conversion.js
17 ms
base.css
352 ms
contents.css
429 ms
nectar.css
487 ms
news.css
485 ms
form.css
512 ms
top.css
521 ms
sweets.css
612 ms
cake.css
649 ms
detail.css
653 ms
company.css
685 ms
other.css
696 ms
vision.css
790 ms
sitenavi.css
807 ms
fujiya.css
807 ms
contact.css
822 ms
shop.css
852 ms
applepie.css
927 ms
halloween.css
972 ms
97th.css
967 ms
peko-book.css
968 ms
a_s.css
983 ms
eco.css
1018 ms
christmas.css
1096 ms
98th.css
1124 ms
suggest.css
1126 ms
head_bt002.gif
1077 ms
information.html
285 ms
page_bg001.gif
910 ms
page_bg002.gif
174 ms
head_logo.gif
163 ms
head_bt003.gif
169 ms
head_bt004.gif
162 ms
head_bt001.gif
322 ms
head_bg003.gif
323 ms
head_bg002.gif
336 ms
head_ic001.gif
344 ms
head_menu001.gif
382 ms
head_menu002.gif
479 ms
head_menu003.gif
483 ms
head_menu004.gif
503 ms
head_menu005.gif
514 ms
top_bg01.gif
544 ms
top_ph132.jpg
955 ms
top_ph130.jpg
1442 ms
top_ph129.jpg
1541 ms
top_ph127.jpg
1193 ms
top_ph131.jpg
1827 ms
top_ph128.jpg
1304 ms
top_ph119.jpg
1433 ms
top_ph120.jpg
1539 ms
top_ph105.jpg
1639 ms
top_ph121.jpg
1754 ms
top_ph126.jpg
1923 ms
top_tx132.gif
1711 ms
top_tx130.gif
1708 ms
top_tx129.gif
1821 ms
top_tx127.gif
1877 ms
top_tx131.gif
1882 ms
top_tx128.gif
1915 ms
top_tx119.gif
2003 ms
top_tx120.gif
1987 ms
suggest.js
1259 ms
top_tx105.gif
2036 ms
top_tx121.gif
1896 ms
top_tx126.gif
1918 ms
top_ic02.gif
1919 ms
top_ic01.gif
1982 ms
top_ex01.png
1908 ms
index_bg003.gif
1895 ms
index_bg004.gif
1907 ms
index_search006.gif
1904 ms
index_search002.gif
1903 ms
index_search001.gif
1935 ms
index_search003.gif
1894 ms
index_search004.gif
1901 ms
index_search005.gif
1897 ms
index_ba001.gif
1883 ms
index_ba038.jpg
1861 ms
index_ba032.jpg
1570 ms
index_ba028.jpg
1598 ms
index_ba033.jpg
1356 ms
__utm.gif
30 ms
48 ms
index_ba036.jpg
1252 ms
39 ms
index_ba037.jpg
1135 ms
index_tx032.gif
1124 ms
index_bt003.gif
1101 ms
index_tx001.gif
1179 ms
index_line001.gif
1102 ms
index_ph240.jpg
1011 ms
index_tx240.gif
1015 ms
index_ph237.jpg
987 ms
index_tx237.gif
978 ms
index_ph242.jpg
1061 ms
index_tx242.gif
1001 ms
index_tx005.gif
1004 ms
index_qr.gif
996 ms
index_info.gif
1001 ms
index_info_bt.gif
974 ms
foot_bt001.gif
1033 ms
foot_bt002.gif
1001 ms
foot_bt003.gif
1002 ms
foot_bt004.gif
1008 ms
foot_bt005.gif
1024 ms
ba_getflash.jpg
973 ms
foot_tx001.gif
1009 ms
foot_tx002.gif
994 ms
foot_tx003.gif
1000 ms
index_ic005.gif
1020 ms
index_arrow002.gif
1049 ms
link_ic003.gif
973 ms
index_ic002.gif
985 ms
index_ic004.gif
986 ms
link_ic004.gif
997 ms
index_tx031.gif
1030 ms
print.css
162 ms
head_menu001on.gif
164 ms
head_menu002on.gif
186 ms
head_menu003on.gif
174 ms
head_menu004on.gif
162 ms
head_menu005on.gif
172 ms
fujiya-peko.co.jp SEO score
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fujiya-peko.co.jp 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 Fujiya-peko.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fujiya-peko.co.jp
Open Graph description is not detected on the main page of Fujiya Peko. 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: