Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

Page Load Speed

7.1 sec in total

First Response

471 ms

Resources Loaded

6.4 sec

Page Rendered

148 ms

janki.jp screenshot

About Website

Click here to check amazing Janki content for Japan. Otherwise, check out these important facts you probably never knew about janki.jp

Visit janki.jp

Key Findings

We analyzed Janki.jp page load time and found that the first response time was 471 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

janki.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value8.7 s

17/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

janki.jp

471 ms

janki.jp

973 ms

common.css

379 ms

layout.css

721 ms

jquery-1.11.2.min.js

1094 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 17% of them (14 requests) were addressed to the original Janki.jp, 11% (9 requests) were made to Plugins.mixi.jp and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Plugins.mixi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 594.3 kB (56%)

Content Size

1.1 MB

After Optimization

458.8 kB

In fact, the total size of Janki.jp main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 732.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 16.6 kB

  • Original 23.5 kB
  • After minification 22.3 kB
  • After compression 6.8 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 16.6 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 10.1 kB

  • Original 207.1 kB
  • After minification 196.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. Janki images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 490.2 kB

  • Original 732.2 kB
  • After minification 701.8 kB
  • After compression 242.0 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 490.2 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 77.4 kB

  • Original 90.5 kB
  • After minification 60.1 kB
  • After compression 13.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. Janki.jp needs all CSS files to be minified and compressed as it can save up to 77.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

77

After Optimization

29

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

Accessibility Review

janki.jp accessibility score

39

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

janki.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

janki.jp SEO score

86

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Janki.jp 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 Janki.jp 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 data is detected on the main page of Janki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: