13.1 sec in total
429 ms
12.2 sec
478 ms
Visit pocky.jp now to see the best up-to-date Pocky content for Japan and also check out these interesting facts you probably never knew about pocky.jp
江崎グリコ ポッキー公式サイトです。
Visit pocky.jpWe analyzed Pocky.jp page load time and found that the first response time was 429 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pocky.jp performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
429 ms
100 ms
642 ms
551 ms
553 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 90% of them (133 requests) were addressed to the original Pocky.jp, 5% (7 requests) were made to Google-analytics.com and 1% (2 requests) were made to Glico.co.jp. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Pocky.jp.
Page size can be reduced by 648.5 kB (19%)
3.5 MB
2.8 MB
In fact, the total size of Pocky.jp main page is 3.5 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 24.7 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 24.7 kB or 79% of the original size.
Potential reduce by 69.8 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. Pocky images are well optimized though.
Potential reduce by 336.7 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 336.7 kB or 69% of the original size.
Potential reduce by 217.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. Pocky.jp needs all CSS files to be minified and compressed as it can save up to 217.2 kB or 86% of the original size.
Number of requests can be reduced by 31 (22%)
144
113
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pocky.jp
429 ms
www.pocky.jp
100 ms
15style_new.css
642 ms
sharebtn_new.css
551 ms
rollover.js
553 ms
jquery-1.7.2.min.js
450 ms
swfobject.js
455 ms
top_animation.js
466 ms
jquery.crossfade.0.2.min.js
953 ms
menu1.css
921 ms
menu2.css
918 ms
footer_sitemap.css
695 ms
top.js
977 ms
brandsite_navi.js
1128 ms
footer_glonavi.js
1081 ms
common_glonavi.css
554 ms
brandsite_navi.css
383 ms
gtm.js
64 ms
15_img_glico_logo.png
443 ms
15_img_pocky_logo.png
450 ms
15_img_main01.jpg
637 ms
15_img_main02.jpg
503 ms
15_img_main03.jpg
562 ms
15_img_main04.jpg
560 ms
15_img_main05.jpg
992 ms
15_img_main06.jpg
916 ms
15_img_bg_border.jpg
1307 ms
15_img_hnavi01.png
1103 ms
15_img_hnavi02.png
1144 ms
15_img_hnavi03.png
1113 ms
15_img_hnavi04.png
1456 ms
15_img_hnavi05.png
1417 ms
15_img_hnavi06.png
1556 ms
15_img_hnavi07.png
1477 ms
15_img_logo_sp.png
1512 ms
15_img_top_namecp.jpg
1737 ms
15_img_top_navi01.jpg
1804 ms
15_img_top_navi02.jpg
2021 ms
15_img_top_navi01_sp.jpg
1907 ms
15_img_top_navi02_sp.jpg
1884 ms
15_img_top_navi03_sp.jpg
1909 ms
15_img_top_navi04_sp.jpg
2208 ms
15_img_top_namecp_sp.jpg
2250 ms
15_img_sharehappi_logo_sp.png
2319 ms
15_img_whats_new.gif
2506 ms
15_img_whats_new_sp.png
2281 ms
15_img_sharehappi.png
2391 ms
15_img_project_sharehapi.png
2637 ms
15_12_img_pkg01.jpg
2751 ms
15_12_img_pkg02.jpg
2723 ms
15_12_img_pkg03.jpg
2685 ms
15_12_img_pkg04.jpg
2974 ms
15_12_img_pkg05.jpg
2938 ms
16_bnr_jimoto.jpg
3015 ms
gtm.js
59 ms
analytics.js
24 ms
ss_glico.js
465 ms
collect
12 ms
collect
14 ms
collect
20 ms
collect
21 ms
collect
22 ms
collect
12 ms
collect
65 ms
collect
75 ms
bnr_midilemon.jpg
3067 ms
bnr_pockyphoto2_off.jpg
2841 ms
15_img_share_happiness.jpg
2760 ms
am_tpc.js
322 ms
15_img_top_pokitomo.png
2748 ms
15_img_top_twitter.png
2973 ms
Global7.gif
2770 ms
plog
496 ms
15_share_ttl.png
2793 ms
15_share_tw.png
2841 ms
15_share_fb.png
2567 ms
15_img_fnavi01.jpg
2692 ms
15_img_fnavi02.jpg
2804 ms
15_img_fnavi03.jpg
2666 ms
15_img_fnavi04.jpg
2793 ms
15_img_fnavi05.jpg
2700 ms
15_img_fnavi06.jpg
2692 ms
15_img_fnavi07.jpg
2671 ms
pocky_footer_rename.jpg
3231 ms
bsnav_logo_close.png
2711 ms
clist_pocky.png
2893 ms
clist_almondpeak.png
2837 ms
clist_vanhouten.png
2736 ms
clist_bitte.png
2873 ms
clist_caplico.png
2867 ms
clist_gaba.png
2791 ms
bsnav_open.png
2799 ms
bsnav_logo_open.png
2793 ms
bslist_pocky.png
2895 ms
bslist_peak.png
2960 ms
bslist_vanhouten.png
2830 ms
bslist_bitte.png
2930 ms
bslist_caplico.png
2825 ms
bslist_gaba.png
2906 ms
bslist_pretz.png
2891 ms
bslist_cheeza.png
2855 ms
bslist_bisco.png
2810 ms
bslist_kissmint.png
3030 ms
bslist_posca.png
2898 ms
bslist_posca_f.png
2893 ms
bslist_asobiglico.png
2963 ms
bslist_giant.png
2769 ms
bslist_papico.png
2846 ms
bslist_icenomi.png
2979 ms
bslist_panapp.png
2955 ms
bslist_bokujo.png
2898 ms
bslist_ccice.png
2732 ms
bslist_bifix.png
2824 ms
bslist_ringo-y.png
2762 ms
bslist_y-kenko.png
2984 ms
bslist_caspi.png
2952 ms
bslist_pucchin.png
3023 ms
bslist_dororich.png
2885 ms
bslist_cafeole.png
3012 ms
bslist_almond-kouka.png
2867 ms
bslist_youji.png
2744 ms
bslist_jukucurry.png
2759 ms
bslist_dearchef.png
2856 ms
bslist_gochi.png
2760 ms
bslist_batondor.png
3011 ms
bslist_pwr_pro.png
3005 ms
btn_social_01.png
2815 ms
btn_social_02.png
2888 ms
btn_social_03.png
2928 ms
15_img_hnavi01_o.png
542 ms
15_img_hnavi02_o.png
433 ms
15_img_hnavi03_o.png
568 ms
15_img_hnavi04_o.png
440 ms
15_img_hnavi05_o.png
472 ms
15_img_hnavi06_o.png
445 ms
15_img_hnavi07_o.png
796 ms
15_img_top_namecp_o.jpg
874 ms
15_img_top_navi01_o.jpg
815 ms
15_img_top_navi02_o.jpg
860 ms
15_img_top_pokitomo_o.png
1025 ms
15_img_top_twitter_o.png
1006 ms
15_img_fnavi01_o.jpg
1395 ms
15_img_fnavi02_o.jpg
1292 ms
15_img_fnavi03_o.jpg
1411 ms
15_img_fnavi04_o.jpg
1350 ms
15_img_fnavi05_o.jpg
1358 ms
15_img_fnavi06_o.jpg
1430 ms
15_img_fnavi07_o.jpg
1741 ms
pocky.jp accessibility score
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
Document doesn't have a <title> element
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
pocky.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pocky.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocky.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 Pocky.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.
pocky.jp
Open Graph description is not detected on the main page of Pocky. 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: