Access puka-puka.net. タオル工場ぷかぷか本店 |

puka-puka.net screenshot

42

Performance

Renders faster than
61% of other websites
62

Accessibility

Visual factors better than
that of 28% of websites
83

Best Practices

More advanced features
available than in
56% of websites
69

SEO

Google-friendlier than
28% of websites

First Response

899 ms

Resources Loaded

6.8 sec

Page Rendered

560 ms

puka-puka.net screenshot

About Website

Welcome to puka-puka.net homepage info - get ready to check Puka best content for Japan right away, or after learning these important things about puka-puka.net

タオル工場ぷかぷか本店は、日本製バスタオル、フェイスタオル、ハンドタオル等の通信販売サイトです。安心清潔な日本製タオルを大阪泉州タオル産地から直営でお届け！「ガッチャンガッチャン！」と音を立てながら、創業から５１年間、２億枚以上のタオルを作り続けてきました。今日もタオル職人が心を込めてタオルを織り上げています。

Visit puka-puka.net

Key Findings

We analyzed Puka-puka.net page load time and found that the first response time was 899 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.383

27/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

puka-puka.net

899 ms

m_sys_common.css

325 ms

import.css

332 ms

script.js

334 ms

index.css

1176 ms

Our browser made a total of 163 requests to load all elements on the main page. We found that 14% of them (23 requests) were addressed to the original Puka-puka.net, 71% (115 requests) were made to Gigaplus.makeshop.jp and 2% (3 requests) were made to Sync.fout.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Gigaplus.makeshop.jp.

Content Size

1.2 MB

After Optimization

1.0 MB

In fact, the total size of Puka-puka.net 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. 55% of websites need less resources to load. Images take 932.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 62.3 kB

Original 77.2 kB
After minification 69.4 kB
After compression 14.9 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 62.3 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 8.4 kB

Original 932.9 kB
After minification 924.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. Puka images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 93.4 kB

Original 146.3 kB
After minification 141.5 kB
After compression 52.9 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 93.4 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 58.2 kB

Original 70.0 kB
After minification 49.7 kB
After compression 11.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. Puka-puka.net needs all CSS files to be minified and compressed as it can save up to 58.2 kB or 83% of the original size.

Requests Now

160

After Optimization

121

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

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

puka-puka.net

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