Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 0

    Best Practices

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

6.1 sec in total

First Response

1.4 sec

Resources Loaded

4.1 sec

Page Rendered

607 ms

rakugokasan.seesaa.net screenshot

About Website

Click here to check amazing Rakugokasan Seesaa content for Japan. Otherwise, check out these important facts you probably never knew about rakugokasan.seesaa.net

古典落語・新作落語・江戸落語・上方落語

Visit rakugokasan.seesaa.net

Key Findings

We analyzed Rakugokasan.seesaa.net page load time and found that the first response time was 1.4 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

rakugokasan.seesaa.net performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value21.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value42.6 s

0/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value10,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value49.0 s

0/100

10%

Network Requests Diagram

rakugokasan.seesaa.net

1387 ms

styles-index.css

365 ms

user-common.css

465 ms

ad_plugin.js

575 ms

rakugo.png

643 ms

Our browser made a total of 335 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Rakugokasan.seesaa.net, 23% (78 requests) were made to Lh5.googleusercontent.com and 19% (64 requests) were made to Lh4.googleusercontent.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Rakugokasan.up.seesaa.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.7 kB (20%)

Content Size

2.0 MB

After Optimization

1.6 MB

In fact, the total size of Rakugokasan.seesaa.net main page is 2.0 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 186.6 kB

  • Original 214.1 kB
  • After minification 214.0 kB
  • After compression 27.5 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 186.6 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 160.6 kB

  • Original 1.7 MB
  • After minification 1.5 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. Rakugokasan Seesaa images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

CSS Optimization

-72%

Potential reduce by 7.6 kB

  • Original 10.5 kB
  • After minification 9.0 kB
  • After compression 2.9 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. Rakugokasan.seesaa.net needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (4%)

Requests Now

332

After Optimization

320

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

Accessibility Review

rakugokasan.seesaa.net accessibility score

66

Accessibility Issues

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.

SEO Factors

rakugokasan.seesaa.net SEO score

100

Search Engine Optimization Advices

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 Rakugokasan.seesaa.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 Rakugokasan.seesaa.net 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 Rakugokasan Seesaa. 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: