Report Summary

  • 68

    Performance

    Renders faster than
    81% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

puccho.jp

ぷっちょ【公式】ホームページ ぷっちょワールド - UHA味覚糖

Page Load Speed

9.6 sec in total

First Response

879 ms

Resources Loaded

8.4 sec

Page Rendered

311 ms

puccho.jp screenshot

About Website

Click here to check amazing Puccho content for Japan. Otherwise, check out these important facts you probably never knew about puccho.jp

ようこそ!ぷっちょワールドへ! UHA味覚糖ぷっちょの公式ホームページだよ

Visit puccho.jp

Key Findings

We analyzed Puccho.jp page load time and found that the first response time was 879 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

puccho.jp performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

19/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

puccho.jp

879 ms

styles.css

333 ms

top.css

501 ms

topslide1.css

339 ms

os.js

345 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 90% of them (85 requests) were addressed to the original Puccho.jp, 4% (4 requests) were made to Google-analytics.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Puccho.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.8 kB (5%)

Content Size

1.2 MB

After Optimization

1.2 MB

In fact, the total size of Puccho.jp main page is 1.2 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 16.3 kB

  • Original 21.0 kB
  • After minification 20.1 kB
  • After compression 4.7 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 16.3 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 29.9 kB

  • Original 1.1 MB
  • After minification 1.1 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. Puccho images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 5.6 kB

  • Original 47.3 kB
  • After minification 44.6 kB
  • After compression 41.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 5.6 kB or 12% of the original size.

CSS Optimization

-74%

Potential reduce by 8.0 kB

  • Original 10.8 kB
  • After minification 8.4 kB
  • After compression 2.8 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. Puccho.jp needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (27%)

Requests Now

92

After Optimization

67

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puccho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

puccho.jp accessibility score

100

Accessibility Issues

Best Practices

puccho.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

puccho.jp SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puccho.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 Puccho.jp main page’s claimed encoding is shift_jis. 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 Puccho. 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: