Tools & Wizards About Us
glico.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

glico.com

Ezaki Glico USA Corporation

Page Load Speed

1.8 sec in total

First Response

13 ms

Resources Loaded

1.6 sec

Page Rendered

226 ms

glico.com screenshot

About Website

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.com

Key Findings

We analyzed Glico.com page load time and found that the first response time was 13 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

glico.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

glico.com

13 ms

341 ms

glico_global_main.css

50 ms

OtAutoBlock.js

49 ms

otSDKStub.js

71 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 83% of them (40 requests) were addressed to the original Glico.com, 6% (3 requests) were made to Cdn-apac.onetrust.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (633 ms) belongs to the original domain Glico.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.0 kB (11%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Glico.com main page is 1.3 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.5 kB

  • Original 31.2 kB
  • After minification 23.9 kB
  • After compression 5.6 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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.5 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 116.4 kB

  • Original 1.3 MB
  • After minification 1.2 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. Glico images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 57 B

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 11.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 12 (28%)

Requests Now

43

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 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 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

glico.com

glico.com

13 ms

341 ms

glico_global_main.css

glico_global_main.css

50 ms

OtAutoBlock.js

OtAutoBlock.js

49 ms

otSDKStub.js

otSDKStub.js

71 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

28 ms

slick.min.js

slick.min.js

13 ms

jquerymatchHeightmin.js

jquerymatchHeightmin.js

16 ms

glico_global_main.js

glico_global_main.js

18 ms

glico_global_modal.js

glico_global_modal.js

25 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

21 ms

trimming.js

trimming.js

61 ms

glico_global_video.js

glico_global_video.js

176 ms

focus-visible.js

focus-visible.js

184 ms

what-input.min.js

what-input.min.js

192 ms

css

css

33 ms

8a6d778d-1d30-41a8-8993-25eaa9569c15.json

8a6d778d-1d30-41a8-8993-25eaa9569c15.json

35 ms

ico_external_02.png

ico_external_02.png

23 ms

btn_arrow.png

btn_arrow.png

22 ms

btn_menu_02.png

btn_menu_02.png

169 ms

logo_header_global.png

logo_header_global.png

29 ms

btn_search_01.png

btn_search_01.png

28 ms

bg_main_01.png

bg_main_01.png

46 ms

2018%200424%20Santy%20POCKY%20-%202464%20F_1680x945.jpg

2018%200424%20Santy%20POCKY%20-%202464%20F_1680x945.jpg

507 ms

Pretz%20Banner%202B__1.png

Pretz%20Banner%202B__1.png

262 ms

New%20Look%20Same%20Crunchiness__1.png

New%20Look%20Same%20Crunchiness__1.png

292 ms

bg_grid_01.png

bg_grid_01.png

75 ms

bg_grid_02.png

bg_grid_02.png

98 ms

bg_grid_04.png

bg_grid_04.png

99 ms

ico_video.png

ico_video.png

99 ms

41745

41745

577 ms

41561

41561

290 ms

125057

125057

572 ms

117189

117189

437 ms

123053

123053

463 ms

bg_grid_03.png

bg_grid_03.png

303 ms

41861

41861

468 ms

54265

54265

593 ms

50565

50565

633 ms

109701

109701

632 ms

ft_ico_facebook.svg

ft_ico_facebook.svg

514 ms

ft_ico_x.svg

ft_ico_x.svg

523 ms

btn_social_105.png

btn_social_105.png

531 ms

ft_ico_youtube.svg

ft_ico_youtube.svg

537 ms

location

location

41 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

21 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

26 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

29 ms

Accessibility Review

glico.com accessibility score

79

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

glico.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

glico.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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 matches the claimed 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.

Social Sharing Optimization

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: