Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

kitene.jp

キテネブログ|最新のニュースやトレンドをわかりやすくお届けします。

Page Load Speed

18.8 sec in total

First Response

684 ms

Resources Loaded

17.8 sec

Page Rendered

340 ms

kitene.jp screenshot

About Website

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

最新のニュースやトレンド情報を発信しているサイトです。芸能・流行・雑学に興味のある方、最新情報をゲットして時代の波に乗り遅れないように!

Visit kitene.jp

Key Findings

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

Performance Metrics

kitene.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

kitene.jp

684 ms

kitene.jp

5992 ms

reset.css

767 ms

pushy.css

798 ms

jquery-2.1.3.min.js

1935 ms

Our browser made a total of 204 requests to load all elements on the main page. We found that 85% of them (173 requests) were addressed to the original Kitene.jp, 7% (14 requests) were made to Kitene.blob.core.windows.net and 3% (7 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source 444-events.olark.com.

Page Optimization Overview & Recommendations

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

Content Size

2.7 MB

After Optimization

2.2 MB

In fact, the total size of Kitene.jp main page is 2.7 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. 45% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 199.0 kB

  • Original 219.9 kB
  • After minification 131.1 kB
  • After compression 20.9 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 88.7 kB, which is 40% 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 199.0 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 115.4 kB

  • Original 2.2 MB
  • After minification 2.1 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. Kitene images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 143.8 kB

  • Original 211.7 kB
  • After minification 168.0 kB
  • After compression 67.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 143.8 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 80.9 kB

  • Original 96.3 kB
  • After minification 72.3 kB
  • After compression 15.5 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. Kitene.jp needs all CSS files to be minified and compressed as it can save up to 80.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 108 (54%)

Requests Now

201

After Optimization

93

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

Accessibility Review

kitene.jp accessibility score

60

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

Best Practices

kitene.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kitene.jp SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Kitene.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 Kitene.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 Kitene. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: