14.1 sec in total
1.1 sec
12.3 sec
676 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
ようこそ、江崎グリコ(Glico)のWebサイトへ。企業情報や商品情報、お得なキャンペーン情報、さらには便利で役立つコンテンツなどをご紹介しています。
Visit pretz.jpWe analyzed Pretz.jp page load time and found that the first response time was 1.1 sec and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pretz.jp performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value14.4 s
0/100
25%
Value23.6 s
0/100
10%
Value2,580 ms
4/100
30%
Value0.198
62/100
15%
Value33.0 s
0/100
10%
1149 ms
71 ms
101 ms
271 ms
446 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pretz.jp, 2% (3 requests) were made to Cdn-apac.onetrust.com and 1% (1 request) were made to Geolocation.onetrust.com. The less responsive or slowest element that took the longest time to load (8.2 sec) relates to the external source Cp.glico.com.
Page size can be reduced by 360.9 kB (7%)
4.8 MB
4.5 MB
In fact, the total size of Pretz.jp main page is 4.8 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. 65% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 28.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 28.2 kB or 83% of the original size.
Potential reduce by 105.0 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 146.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 146.7 kB or 69% of the original size.
Potential reduce by 80.9 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 80.9 kB or 85% of the original size.
Number of requests can be reduced by 26 (19%)
138
112
The browser has sent 138 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 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
1149 ms
OtAutoBlock.js
71 ms
otSDKStub.js
101 ms
common_glonavi.css
271 ms
slick.css
446 ms
style.css
665 ms
top.css
843 ms
remodal.css
656 ms
remodal-default-theme.css
656 ms
cm.css
703 ms
jquery.js
1247 ms
pretz_navi.js
818 ms
remodal.js
892 ms
cm.js
844 ms
header_glonavi.js
876 ms
slick.min.js
1207 ms
common.js
1003 ms
rellax.min.js
1030 ms
top.js
1050 ms
brandsite_navi.js
1102 ms
footer_glonavi.js
1178 ms
48517763-010e-42e6-99f4-833e9736129a.json
45 ms
location
45 ms
brandsite_navi.css
955 ms
pretz_navi.css
190 ms
logo_pretz.png
773 ms
mv_txt01.png
770 ms
mv_txt02.png
772 ms
mv_txt03.png
771 ms
mv_pkg_01.png
775 ms
mv_pkg.png
775 ms
mv_pkg_02.png
895 ms
mv_pkg_03.png
889 ms
mv_product.png
1178 ms
mv_product.png
969 ms
mv_02_obj_01.png
920 ms
mv_02_obj_02.png
933 ms
mv_02_obj_03.png
1053 ms
mv_02_obj_04.png
1057 ms
mv_02_obj_05.png
1084 ms
mv_02_obj_06.png
1112 ms
mv_02_obj_07.png
1145 ms
mv_02_obj_08.png
1220 ms
mv_02_obj_09.png
1222 ms
mv_02_obj_10.png
1248 ms
mv_02_obj_11.png
1291 ms
img_vegetable01.png
1669 ms
img_vegetable02.png
1786 ms
img_vegetable03.png
1585 ms
img_vegetable04.png
1551 ms
img_vegetable05.png
1787 ms
img_vegetable06.png
1870 ms
img_vegetable01.png
2039 ms
img_vegetable02.png
1914 ms
read_txt.png
1856 ms
product_ttl.png
1995 ms
product01.png
2738 ms
product02.png
2963 ms
product03.png
2890 ms
product05.png
2804 ms
product06.png
2130 ms
secret_ttl.png
1465 ms
secret_bnr.png
2276 ms
campaign_ttl.png
2156 ms
txt_lead.png
2202 ms
txt_share.png
2300 ms
txt_share.png
2295 ms
NotoSansJP-Regular.woff
7722 ms
NotoSansJP-Medium.woff
8246 ms
NotoSansJP-Bold.woff
7927 ms
btn_fb.png
2279 ms
btn_tw.png
2285 ms
btn_line.png
2239 ms
icon_line_l.png
2330 ms
icon_twitter_l.png
2357 ms
pagetop.png
2366 ms
pagetop.png
2409 ms
btn_menu_01.png
2439 ms
logo_header_01.png
2488 ms
btn_social_01.png
2494 ms
btn_social_02.png
2542 ms
btn_social_03.png
2607 ms
spacer.gif
2326 ms
header_menu_bg.gif
2379 ms
pretz_gnav2-01_off.png
2370 ms
pretz_gnav2-02_off.png
2304 ms
pretz_gnav2-04_off.png
2356 ms
mv_img_02.jpg
3002 ms
bg_lead.png
2647 ms
bg.png
2600 ms
arrow_green.png
2697 ms
arrow_red.png
2672 ms
arrow_yellow.png
2641 ms
arrow_green2.png
2163 ms
arrow_red2.png
2220 ms
arrow_white.png
2163 ms
bg_campaign&movie.png
2248 ms
pagetop_o.png
2264 ms
footer_menu_bg.gif
2265 ms
pretz_gnav01_off.png
2358 ms
pretz_gnav02_off.png
2312 ms
pretz_gnav04_off.png
2338 ms
pretz_footer_menu_sns0.gif
2430 ms
pretz_footer_menu_sns4_off.gif
2308 ms
pretz_footer_menu_sns1_off.gif
2333 ms
pretz_footer_menu_sns3_off.gif
2414 ms
bsnav_logo_close.png
2295 ms
clist_pretz.png
2324 ms
clist_bisco.png
2366 ms
clist_cheeza.png
2345 ms
clist_caplico.png
2338 ms
clist_pocky.png
2344 ms
clist_sunao.png
2371 ms
bsnav_open.png
2342 ms
bsnav_logo_open.png
2342 ms
bslist_pocky.png
2388 ms
bslist_gaba.png
2357 ms
bslist_libera.png
2362 ms
bslist_caplico.png
2416 ms
bslist_bisco.png
2364 ms
bslist_pretz.png
2079 ms
bslist_cheeza.png
2198 ms
bslist_papico.png
2022 ms
bslist_giant.png
2065 ms
bslist_icenomi.png
2056 ms
bslist_panapp.png
2050 ms
bslist_bokujo.png
2056 ms
bslist_sunao.png
2076 ms
bslist_17ice.png
2062 ms
bslist_pucchin.png
1999 ms
bslist_bifix.png
2110 ms
bslist_ringo-y.png
2096 ms
bslist_cafeole.png
1985 ms
bslist_youji.png
2139 ms
bslist_icreo.png
2080 ms
bslist_almondkouka.png
2008 ms
bslist_jukucurry.png
2171 ms
bslist_crea.png
2098 ms
bslist_pwr_pro.png
2062 ms
bslist_batondor.png
2157 ms
bsnav_logo_sp.png
2100 ms
bslist_none.png
2089 ms
pretz.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
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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
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
UTF-8
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 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.
pretz.jp
Open Graph data is detected on the main page of Pretz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: