Access pocky.jp. ポッキー【Pocky】江崎グリコ公式サイト

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

pocky.jp

513 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Pocky.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (513 ms) belongs to the original domain Pocky.jp.

Content Size

3.4 MB

After Optimization

2.8 MB

In fact, the total size of Pocky.jp main page is 3.4 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-17%

Potential reduce by 15 B

Original 87 B
After minification 86 B
After compression 72 B

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 15 B or 17% of the original size.

Image Optimization

-3%

Potential reduce by 69.8 kB

Original 2.7 MB
After minification 2.6 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. Pocky images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 304.8 kB

Original 454.0 kB
After minification 452.7 kB
After compression 149.2 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 304.8 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 217.2 kB

Original 252.7 kB
After minification 232.2 kB
After compression 35.5 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. Pocky.jp needs all CSS files to be minified and compressed as it can save up to 217.2 kB or 86% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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.

High

Document doesn't have a <title> element

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Document doesn't have a <title> element

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocky.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pocky.jp main page’s claimed encoding is . 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Pocky. 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: