10.8 sec in total
652 ms
9.6 sec
505 ms
Visit petit-pochi.com now to see the best up-to-date Petit Pochi content and also check out these interesting facts you probably never knew about petit-pochi.com
Search on topics your interested. Read great personalised news.
Visit petit-pochi.comWe analyzed Petit-pochi.com page load time and found that the first response time was 652 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
petit-pochi.com performance score
652 ms
529 ms
335 ms
356 ms
310 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 18% of them (19 requests) were addressed to the original Petit-pochi.com, 59% (61 requests) were made to Gigaplus.makeshop.jp and 3% (3 requests) were made to Sync.fout.jp. The less responsive or slowest element that took the longest time to load (6.5 sec) relates to the external source Gigaplus.makeshop.jp.
Page size can be reduced by 1.6 MB (48%)
3.4 MB
1.8 MB
In fact, the total size of Petit-pochi.com main page is 3.4 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. 40% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 42.2 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 42.2 kB or 79% of the original size.
Potential reduce by 1.5 MB
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, Petit Pochi needs image optimization as it can save up to 1.5 MB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.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 6.6 kB or 23% of the original size.
Potential reduce by 59.3 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. Petit-pochi.com needs all CSS files to be minified and compressed as it can save up to 59.3 kB or 85% of the original size.
Number of requests can be reduced by 36 (36%)
101
65
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Petit Pochi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
petit-pochi.com
652 ms
m_sys_common.css
529 ms
import.css
335 ms
script.js
356 ms
gotop.js
310 ms
rollover.js
360 ms
check_history.css
308 ms
pager.css
311 ms
shopdetail.css
488 ms
ranking.css
354 ms
basket.css
373 ms
security.css
546 ms
category_menu.css
620 ms
topicpath.css
640 ms
catalog.css
683 ms
ga.js
54 ms
logo_t.png
183 ms
count3.makeshop.jp
312 ms
gnavi1.png
154 ms
gnavi2.png
308 ms
gnavi3.png
317 ms
gnavi4.png
346 ms
gnavi5.png
350 ms
gnavi6.png
360 ms
logo_f.png
543 ms
otoiawase.jpg
1077 ms
chopochi-side.jpg
792 ms
side_bn2.png
675 ms
side_cate1.png
525 ms
side_cate2.png
538 ms
side_cate3.png
1505 ms
side_cate4.png
859 ms
side_info_ti.png
849 ms
side_guide_bn.png
847 ms
side_fb_bn.png
950 ms
side_mailmaga_bn.png
1016 ms
main_bn1.png
3451 ms
chopochi-center.jpg
2557 ms
kisetsugentei.jpg
1895 ms
kisetsugift-center.jpg
2835 ms
cate_gift_bn1_R.jpg
1381 ms
top_ranking_ti.png
1536 ms
top_jitaku_ti.png
2027 ms
top_recommend1.png
3991 ms
top_recommend3.png
4262 ms
top_recommend2.png
6465 ms
top_info_ti.png
2734 ms
top_about_h2.png
2914 ms
logo2.png
2998 ms
to_detail_bt1.png
3092 ms
top_about_bn1.png
4816 ms
top_about_bn2.jpg
4167 ms
pagetop.png
3809 ms
0000000000292.jpg
498 ms
0000000000032.jpg
933 ms
0000000000232.jpg
629 ms
newstitle.gif
336 ms
left_edge.gif
347 ms
right_edge.gif
357 ms
is_show_gmo_header.html
1565 ms
aq_tag_aos.js
127 ms
372 ms
__utm.gif
30 ms
yaji1.png
3844 ms
EM34BYVZ46DUGEQNJE6A
132 ms
h_cart.png
3969 ms
side_season_icon1.png
3869 ms
side_season_icon6.png
3985 ms
side_season_icon7.png
4010 ms
side_season_icon8.png
4008 ms
side_category_icon1.png
4064 ms
gmsync
298 ms
segmentation.js
53 ms
366 ms
cnt
380 ms
side_category_icon2.png
3930 ms
side_category_icon3.png
3994 ms
side_category_icon4.png
3994 ms
side_category_icon5.png
3908 ms
side_category_icon6.png
3817 ms
ranking_bk.png
6199 ms
rank1.png
3867 ms
rank2.png
3879 ms
rank3.png
3810 ms
yaji2.png
3881 ms
beacon.html
45 ms
gnavi1_o.png
181 ms
gnavi2_o.png
462 ms
gnavi3_o.png
542 ms
gnavi4_o.png
524 ms
gnavi5_o.png
473 ms
gnavi6_o.png
879 ms
pixel
19 ms
cs
299 ms
Pug
23 ms
set
301 ms
sd
5 ms
tap.php
7 ms
sync
8 ms
pixel
15 ms
sync
374 ms
mapuser
150 ms
sync
279 ms
sync
310 ms
petit-pochi.com SEO score
EN
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petit-pochi.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Petit-pochi.com main page’s claimed encoding is euc-jp. 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.
petit-pochi.com
Open Graph description is not detected on the main page of Petit Pochi. 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: