Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

sakka.org

作家でごはん!

Page Load Speed

3.3 sec in total

First Response

1.1 sec

Resources Loaded

2 sec

Page Rendered

108 ms

sakka.org screenshot

About Website

Welcome to sakka.org homepage info - get ready to check Sakka best content for Japan right away, or after learning these important things about sakka.org

小説家・作家志望者のためのコミュニティ。小説投稿、質問や相談、文学賞の情報、執筆に関する話題など、作家のためのサービスを提供しています。

Visit sakka.org

Key Findings

We analyzed Sakka.org page load time and found that the first response time was 1.1 sec and then it took 2.1 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

sakka.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

sakka.org

1142 ms

base.css

382 ms

style.css

592 ms

show_ads.js

5 ms

analytics.js

36 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 33% of them (10 requests) were addressed to the original Sakka.org, 23% (7 requests) were made to Google.com and 13% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Sakka.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.6 kB (33%)

Content Size

168.2 kB

After Optimization

112.6 kB

In fact, the total size of Sakka.org main page is 168.2 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. 20% of websites need less resources to load. Javascripts take 104.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 12.0 kB

  • Original 17.4 kB
  • After minification 17.2 kB
  • After compression 5.4 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 12.0 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 1.4 kB

  • Original 33.3 kB
  • After minification 31.9 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. Sakka images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 32.3 kB

  • Original 104.6 kB
  • After minification 104.5 kB
  • After compression 72.3 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.3 kB or 31% of the original size.

CSS Optimization

-77%

Potential reduce by 9.9 kB

  • Original 12.8 kB
  • After minification 10.3 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. Sakka.org needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (63%)

Requests Now

27

After Optimization

10

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

Accessibility Review

sakka.org accessibility score

100

Accessibility Issues

Best Practices

sakka.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

sakka.org SEO score

79

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sakka.org 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 Sakka.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

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