10.5 sec in total
481 ms
9.5 sec
509 ms
Visit cp.glico.jp now to see the best up-to-date Cp Glico content for Japan and also check out these interesting facts you probably never knew about cp.glico.jp
ようこそ、江崎グリコ(Glico)のWebサイトへ。企業情報や商品情報、お得なキャンペーン情報、さらには便利で役立つコンテンツなどをご紹介しています。
Visit cp.glico.jpWe analyzed Cp.glico.jp page load time and found that the first response time was 481 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cp.glico.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value17.8 s
0/100
25%
Value19.3 s
0/100
10%
Value2,430 ms
5/100
30%
Value0.358
30/100
15%
Value38.2 s
0/100
10%
481 ms
3051 ms
561 ms
896 ms
556 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cp.glico.jp, 73% (55 requests) were made to Glico.com and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Glico.com.
Page size can be reduced by 445.7 kB (17%)
2.6 MB
2.1 MB
In fact, the total size of Cp.glico.jp main page is 2.6 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. 45% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.3 kB or 82% of the original size.
Potential reduce by 35.4 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. Cp Glico images are well optimized though.
Potential reduce by 152.3 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 152.3 kB or 54% of the original size.
Potential reduce by 202.6 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. Cp.glico.jp needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 34 (47%)
72
38
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cp 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 23 to 1 for JavaScripts and as a result speed up the page load time.
cp.glico.jp
481 ms
3051 ms
main.css
561 ms
jstream-obj.min.js
896 ms
jquery.js
556 ms
slick.min.js
408 ms
jquerymatchHeightmin.js
233 ms
main.js
390 ms
modal.js
472 ms
masonry.pkgd.min.js
797 ms
trimming.js
789 ms
video.js
711 ms
typeahead.bundle.min.js
806 ms
typeahead.jquery.min.js
784 ms
bloodhound.min.js
1109 ms
logo_header_01.png
374 ms
btn_social_01.png
313 ms
btn_social_02.png
297 ms
btn_social_04.png
332 ms
pretz_top_img__1.jpg
787 ms
vanhouten_top2__1.jpg
962 ms
top3%E3%82%AB%E3%83%95%E3%82%A7%E3%82%AA%E3%83%BC%E3%83%AC_a__1.jpg
1069 ms
top4%E3%82%B8%E3%83%A3%E3%82%A4%E3%82%A2%E3%83%B3%E3%83%88%E3%82%B3%E3%83%BC%E3%83%B3%E3%83%90_a__1.jpg
919 ms
top5%E3%83%97%E3%83%AC%E3%83%9F%E3%82%A2%E3%83%A0%E7%86%9F%E3%82%AB%E3%83%AC%E3%83%BC_a__1.jpg
996 ms
smileglicocm2016-1__1.jpg
1309 ms
main__57.jpg
1186 ms
01main__1.jpg
1537 ms
prinyan_cp2016__1.jpg
2027 ms
main__56.JPG
1432 ms
main__53.jpg
1555 ms
%20__2.jpg
1803 ms
gtm.js
154 ms
ico_external_02.png
1565 ms
btn_menu_02.png
1697 ms
btn_search_01.png
1795 ms
bg_main_01.png
1792 ms
bg_grid_01.png
1868 ms
bg_grid_02.png
1991 ms
bg_grid_04.png
2246 ms
ico_video.png
2120 ms
ico_footer_01.png
2082 ms
ico_footer_02.png
2135 ms
btn_jumbotron_01.png
2179 ms
btn_jumbotron_02.png
2134 ms
ga.js
57 ms
analytics.js
88 ms
ss_glico.js
2331 ms
iframe_api
85 ms
recommend
3357 ms
__utm.gif
34 ms
collect
25 ms
collect
29 ms
collect
37 ms
www-widgetapi.js
48 ms
collect
90 ms
QtAYFkE09Ek
66 ms
www-embed-player-vflfNyN_r.css
7 ms
www-embed-player.js
27 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
38 ms
ad_status.js
28 ms
am_tpc.js
633 ms
plog
893 ms
AlZQKF8gRhw
72 ms
17%E3%82%A2%E3%82%A4%E3%82%B9%E3%82%AD%E3%83%BC%E3%83%93%E3%82%B8%E3%83%A5%E3%82%A2%E3%83%AB15%E5%86%AC__1.jpg
637 ms
icenomi356cp_img_1680__1.jpg
784 ms
SS_150916000011__1.jpg
682 ms
main__50.JPG
526 ms
thumb_bifix1000__1.jpg
870 ms
panapp_brand__1.jpg
624 ms
TOP__1.jpg
1351 ms
glicoEast_top__1.png
1256 ms
original_img__1.jpg
1377 ms
SS_150916000033__1.jpg
1313 ms
ico_q.png
1246 ms
nr-892.min.js
52 ms
cp.glico.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
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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cp.glico.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
cp.glico.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cp.glico.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 Cp.glico.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.
cp.glico.jp
Open Graph data is detected on the main page of Cp Glico. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: