Tools & Wizards About Us
puusan.com screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

puusan.com

WinMiソフトテニスクラブ

Page Load Speed

2.8 sec in total

First Response

535 ms

Resources Loaded

2.1 sec

Page Rendered

148 ms

puusan.com screenshot

About Website

Visit puusan.com now to see the best up-to-date Puusan content for Japan and also check out these interesting facts you probably never knew about puusan.com

Visit puusan.com

Key Findings

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

Performance Metrics

puusan.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

puusan.com

535 ms

hpbparts.css

164 ms

container_9A_2c_right.css

320 ms

main_9A_2c.css

325 ms

user.css

335 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Puusan.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Puusan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.0 kB (28%)

Content Size

391.3 kB

After Optimization

281.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Puusan.com main page is 391.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 344.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 5.8 kB

  • Original 8.3 kB
  • After minification 6.8 kB
  • After compression 2.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 1.5 kB, which is 18% 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 5.8 kB or 69% of the original size.

Image Optimization

-20%

Potential reduce by 70.2 kB

  • Original 344.8 kB
  • After minification 274.6 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. Obviously, Puusan needs image optimization as it can save up to 70.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-89%

Potential reduce by 34.1 kB

  • Original 38.2 kB
  • After minification 24.1 kB
  • After compression 4.1 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. Puusan.com needs all CSS files to be minified and compressed as it can save up to 34.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (16%)

Requests Now

19

After Optimization

16

  • Images
  • CSS

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

Network Requests Diagram

puusan.com

puusan.com

535 ms

hpbparts.css

hpbparts.css

164 ms

container_9A_2c_right.css

container_9A_2c_right.css

320 ms

main_9A_2c.css

main_9A_2c.css

325 ms

user.css

user.css

335 ms

index-news-011.jpg

index-news-011.jpg

500 ms

yubitoma-logo.gif

yubitoma-logo.gif

720 ms

facebook3.jpg

facebook3.jpg

545 ms

twitter2.png

twitter2.png

486 ms

bukun.jpg

bukun.jpg

489 ms

fbg_9A.png

fbg_9A.png

171 ms

logo_9A.png

logo_9A.png

304 ms

top_mainimg_9A_01.png

top_mainimg_9A_01.png

1248 ms

top_indexBg_9A.png

top_indexBg_9A.png

329 ms

pointS_9A.png

pointS_9A.png

334 ms

returnTop_9A.png

returnTop_9A.png

388 ms

menuBg_9A_02.png

menuBg_9A_02.png

458 ms

top_banner_9A_01.png

top_banner_9A_01.png

659 ms

top_banner_9A_02.png

top_banner_9A_02.png

825 ms

top_banner_9A_03.png

top_banner_9A_03.png

560 ms

Accessibility Review

puusan.com accessibility score

59

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

puusan.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

puusan.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

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

puusan.com

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