Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

konest.com

韓国旅行「コネスト」

Page Load Speed

4.5 sec in total

First Response

597 ms

Resources Loaded

3.5 sec

Page Rendered

390 ms

About Website

Welcome to konest.com homepage info - get ready to check Konest best content for Japan right away, or after learning these important things about konest.com

韓国旅行情報の専門サイト。ソウル・釜山などのホテル、エステ、現地ツアー、日韓航空券の格安予約。グルメ・ショッピング・観光スポットのおすすめ情報。割引クーポンや口コミも満載。

Visit konest.com

Key Findings

We analyzed Konest.com page load time and found that the first response time was 597 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

konest.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

konest.com

597 ms

www.konest.com

1013 ms

jquery-latest.min.js

32 ms

konest.min.js

26 ms

wpp_common.min.js

24 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 81% of them (101 requests) were addressed to the original Konest.com, 4% (5 requests) were made to Tpc.googlesyndication.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Konest.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 489.7 kB (23%)

Content Size

2.2 MB

After Optimization

1.7 MB

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

HTML Optimization

-81%

Potential reduce by 98.9 kB

  • Original 122.3 kB
  • After minification 117.1 kB
  • After compression 23.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 98.9 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 9.3 kB

  • Original 1.3 MB
  • After minification 1.3 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. Konest images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 279.8 kB

  • Original 632.5 kB
  • After minification 632.5 kB
  • After compression 352.7 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 279.8 kB or 44% of the original size.

CSS Optimization

-81%

Potential reduce by 101.7 kB

  • Original 125.8 kB
  • After minification 109.5 kB
  • After compression 24.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. Konest.com needs all CSS files to be minified and compressed as it can save up to 101.7 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

121

After Optimization

73

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

Accessibility Review

konest.com accessibility score

59

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

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

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

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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.

High

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

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

konest.com 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

konest.com SEO score

77

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