5.7 sec in total
433 ms
4.9 sec
386 ms
Visit pretz.jp now to see the best up-to-date Pretz content and also check out these interesting facts you probably never knew about pretz.jp
江崎グリコ プリッツ公式サイトです。プリッツと一緒に楽しい時間をもっと楽しく!
Visit pretz.jpWe analyzed Pretz.jp page load time and found that the first response time was 433 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pretz.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value21.4 s
0/100
25%
Value18.1 s
0/100
10%
Value860 ms
33/100
30%
Value0.269
45/100
15%
Value29.1 s
0/100
10%
433 ms
714 ms
588 ms
440 ms
441 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pretz.jp, 84% (90 requests) were made to Glico.co.jp and 7% (8 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Glico.co.jp.
Page size can be reduced by 351.8 kB (14%)
2.5 MB
2.2 MB
In fact, the total size of Pretz.jp main page is 2.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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 20.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. 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 20.3 kB or 79% of the original size.
Potential reduce by 108.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. Pretz images are well optimized though.
Potential reduce by 178.5 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 178.5 kB or 68% of the original size.
Potential reduce by 44.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. Pretz.jp needs all CSS files to be minified and compressed as it can save up to 44.2 kB or 84% of the original size.
Number of requests can be reduced by 32 (31%)
103
71
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pretz. 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 6 to 1 for CSS and as a result speed up the page load time.
pretz.jp
433 ms
714 ms
common_glonavi.css
588 ms
footer_sitemap.css
440 ms
16base.css
441 ms
16layout.css
479 ms
16top.css
857 ms
jquery-1.7.1.min.js
1016 ms
16_script.js
595 ms
swfobject.js
595 ms
jquery.easing.1.3.js
643 ms
16_top.js
733 ms
header_glonavi.js
736 ms
brandsite_navi.js
585 ms
footer_glonavi.js
654 ms
brandsite_navi.css
298 ms
16_smp_mainv.jpg
1977 ms
16_smp_mainv_copy01.png
326 ms
16_smp_mainv_copy02.png
233 ms
16_smp_mainv_campaign.png
164 ms
spacer.gif
163 ms
16_pkg_salad.jpg
295 ms
16_pkg_roast.jpg
588 ms
16_pkg_tomato.jpg
445 ms
16_pkg_butter.jpg
522 ms
16_bnn_2016cp_stamp.jpg
731 ms
16_bnn_2016cp.jpg
1286 ms
15_share_ttl.png
581 ms
15_share_tw.png
682 ms
15_share_fb.png
725 ms
gtm.js
83 ms
btn_menu_01.png
719 ms
logo_header_01.png
834 ms
btn_social_01.png
862 ms
btn_social_02.png
861 ms
btn_social_03.png
863 ms
spacer.gif
995 ms
16_sp_brand_logo.png
1001 ms
16_hnav01_on.gif
999 ms
16_hnav02_off.gif
1002 ms
16_hnav03_off.gif
1150 ms
16_hnav04_off.gif
1147 ms
16_top_nofla.jpg
2312 ms
16_gnav01_on.gif
1137 ms
16_gnav02_off.gif
1282 ms
16_gnav03_off.gif
1299 ms
16_gnav04_off.gif
1284 ms
bsnav_logo_close.png
1405 ms
clist_pretz.png
1425 ms
clist_cheeza.png
1427 ms
clist_bisco.png
1457 ms
clist_almondpeak.png
1568 ms
clist_asobiglico.png
1572 ms
gtm.js
57 ms
analytics.js
6 ms
collect
23 ms
collect
94 ms
collect
73 ms
collect
72 ms
collect
61 ms
collect
71 ms
collect
92 ms
ss_glico.js
1610 ms
collect
86 ms
collect
21 ms
collect
21 ms
clist_posca.png
1457 ms
bsnav_open.png
1555 ms
collect
18 ms
bsnav_logo_open.png
1492 ms
bslist_pocky.png
1515 ms
bslist_peak.png
1477 ms
bslist_vanhouten.png
1394 ms
bslist_bitte.png
1362 ms
bslist_caplico.png
1409 ms
bslist_gaba.png
1376 ms
bslist_pretz.png
1333 ms
bslist_cheeza.png
1376 ms
bslist_bisco.png
1396 ms
bslist_posca.png
1309 ms
bslist_posca_f.png
1332 ms
bslist_asobiglico.png
1333 ms
bslist_giant.png
1389 ms
bslist_papico.png
1283 ms
bslist_icenomi.png
1296 ms
bslist_panapp.png
1332 ms
bslist_ccice.png
1330 ms
bslist_pucchin.png
1260 ms
bslist_dororich.png
1282 ms
bslist_bifix.png
1308 ms
bslist_ringo-y.png
1201 ms
bslist_y-kenko.png
1185 ms
bslist_caspi.png
1182 ms
bslist_cafeole.png
1257 ms
bslist_youji.png
1172 ms
bslist_almond-kouka.png
1179 ms
bslist_jukucurry.png
1163 ms
bslist_pwr_pro.png
1153 ms
bslist_batondor.png
1041 ms
16_hnav02_on.gif
1144 ms
16_hnav03_on.gif
1121 ms
am_tpc.js
310 ms
16_hnav04_on.gif
1008 ms
16_gnav02_on.gif
1037 ms
16_gnav03_on.gif
1027 ms
16_gnav04_on.gif
977 ms
plog
495 ms
pretz.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
pretz.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pretz.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pretz.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 Pretz.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.
pretz.jp
Open Graph description is not detected on the main page of Pretz. 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: