Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

kajika.net

(トップページ)社会派エッセイ | 杜父魚文庫(カジカ文庫)

Page Load Speed

2.6 sec in total

First Response

657 ms

Resources Loaded

1.8 sec

Page Rendered

168 ms

kajika.net screenshot

About Website

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

(トップページ)社会派エッセイ | 杜父魚文庫(カジカ文庫)

Visit kajika.net

Key Findings

We analyzed Kajika.net page load time and found that the first response time was 657 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

kajika.net performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

kajika.net

657 ms

style.css

195 ms

script.js

344 ms

AC_RunActiveContent.js

364 ms

fla.js

386 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 15.8 kB (74%)

Content Size

21.3 kB

After Optimization

5.6 kB

In fact, the total size of Kajika.net main page is 21.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. Javascripts take 9.8 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 4.1 kB

  • Original 6.2 kB
  • After minification 5.9 kB
  • After compression 2.2 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 4.1 kB or 65% of the original size.

JavaScript Optimization

-76%

Potential reduce by 7.4 kB

  • Original 9.8 kB
  • After minification 6.7 kB
  • After compression 2.4 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 7.4 kB or 76% of the original size.

CSS Optimization

-82%

Potential reduce by 4.3 kB

  • Original 5.3 kB
  • After minification 2.7 kB
  • After compression 957 B

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. Kajika.net needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kajika. According to our analytics all requests are already optimized.

Accessibility Review

kajika.net accessibility score

69

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

kajika.net 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

SEO Factors

kajika.net SEO score

58

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

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 Kajika.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 Kajika.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 Kajika. 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: