Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

kankai.net

壱岐旅行計画【日本遺産・壱岐】の色・華・風

Page Load Speed

3.8 sec in total

First Response

914 ms

Resources Loaded

2.5 sec

Page Rendered

315 ms

kankai.net screenshot

About Website

Welcome to kankai.net homepage info - get ready to check Kankai best content for Japan right away, or after learning these important things about kankai.net

壱岐旅行計画は壱岐観光情報に特化した壱岐観光ポータルサイトです。日本遺産・壱岐。古代日本ヤマトの興りの島壱岐観光なら、宿、フェリー、レンタカーなどお出かけ前にチェックが必要な情報満載。壱岐においでください。

Visit kankai.net

Key Findings

We analyzed Kankai.net page load time and found that the first response time was 914 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

kankai.net performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

kankai.net

914 ms

top.jpg

844 ms

0.7hi.jpg

697 ms

0.7pair.jpg

753 ms

famiry.jpg

1489 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Kankai.net, 12% (2 requests) were made to Bran.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Bran.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.7 kB (16%)

Content Size

473.0 kB

After Optimization

395.3 kB

In fact, the total size of Kankai.net main page is 473.0 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. 15% of websites need less resources to load. Images take 448.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.2 kB

  • Original 24.2 kB
  • After minification 19.8 kB
  • After compression 4.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 4.4 kB, which is 18% 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 19.2 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 58.4 kB

  • Original 448.8 kB
  • After minification 390.4 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. Obviously, Kankai needs image optimization as it can save up to 58.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

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

Accessibility Review

kankai.net accessibility score

57

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

kankai.net best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

kankai.net SEO score

67

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kankai.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kankai.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 Kankai. 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: