5.7 sec in total
490 ms
4.8 sec
403 ms
Visit glico.com now to see the best up-to-date Glico content for Japan and also check out these interesting facts you probably never knew about glico.com
The official web site of Ezaki Glico USA Corporation. Explore the corporate philosophy, businesses and our products.
Visit glico.comWe analyzed Glico.com page load time and found that the first response time was 490 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 70% of websites can load faster.
glico.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value8.2 s
2/100
25%
Value14.1 s
1/100
10%
Value1,350 ms
17/100
30%
Value0.061
97/100
15%
Value21.7 s
1/100
10%
490 ms
251 ms
16 ms
538 ms
34 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 65% of them (44 requests) were addressed to the original Glico.com, 7% (5 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Glico.com.
Page size can be reduced by 699.8 kB (12%)
6.0 MB
5.3 MB
In fact, the total size of Glico.com main page is 6.0 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. 30% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 43.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. 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 43.0 kB or 70% of the original size.
Potential reduce by 97.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. Glico images are well optimized though.
Potential reduce by 357.0 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 357.0 kB or 60% of the original size.
Potential reduce by 202.4 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. Glico.com needs all CSS files to be minified and compressed as it can save up to 202.4 kB or 83% of the original size.
Number of requests can be reduced by 25 (42%)
59
34
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
glico.com
490 ms
www.glico.com
251 ms
16 ms
global_main.css
538 ms
jstream-obj.min.js
34 ms
jquery.js
34 ms
slick.min.js
33 ms
jquerymatchHeightmin.js
27 ms
global_main.js
386 ms
modal.js
34 ms
masonry.pkgd.min.js
41 ms
trimming.js
38 ms
video.js
383 ms
addthis_widget.js
48 ms
css
55 ms
global_logo_header_01.png
288 ms
mainvisual__2.jpg
1384 ms
pocky_050_s__2.jpg
1051 ms
global_history__6.png
1083 ms
global_product__7.png
1126 ms
global_product__5.png
1241 ms
global_history__5.png
1360 ms
main__12.jpg
2254 ms
global_message__1.png
1555 ms
14861__1.jpg
1415 ms
global_Philosophy__1.png
2306 ms
glicousa_homepage_slider__1.png
2324 ms
pic_map_02_s_global__1.png
1675 ms
main__19.jpg
1700 ms
00_main-2__3.jpg
2144 ms
01%E3%83%A1%E3%82%A4%E3%83%B3__4.jpg
2287 ms
IMG_9729__5.jpg
2276 ms
01%E3%83%A1%E3%82%A4%E3%83%B3__6.jpg
2957 ms
00_santa3a__2.jpg
2900 ms
main__33.JPG
3194 ms
__303.jpg
2760 ms
gtm.js
125 ms
btn_menu_01.png
2306 ms
btn_menu_02.png
2577 ms
bg_main_01.png
2555 ms
bg_grid_01.png
2559 ms
bg_grid_02.png
2563 ms
bg_grid_04.png
2568 ms
ico_video.png
2574 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
125 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
145 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
157 ms
iframe_api
106 ms
btn_jumbotron_01.png
2887 ms
btn_jumbotron_02.png
2821 ms
ga.js
84 ms
analytics.js
68 ms
ss_glico.js
2630 ms
www-widgetapi.js
63 ms
collect
23 ms
collect
40 ms
collect
41 ms
__utm.gif
24 ms
collect
52 ms
n7bHwGyE6dg
63 ms
www-embed-player-vflZsBgOl.css
24 ms
www-embed-player.js
52 ms
base.js
94 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
27 ms
ad_status.js
72 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
26 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
58 ms
am_tpc.js
625 ms
glico.com 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
glico.com 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
glico.com 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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glico.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 Glico.com 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.
glico.com
Open Graph data is detected on the main page of Glico. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: