Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kting.com.tw

KT墾丁在地通|墾丁包車|全台灣包車旅遊|全台包車|台灣包車旅遊|高雄包車|包車環島旅遊|墾丁~在地通|肯丁在地通|大丁小丁|墾丁租車|墾丁旅遊接駁車|墾丁包車遊覽|高雄租車|高雄旅遊接駁車|高雄包車遊覽|墾丁在地通線上訂位|墾丁遊覽公司|墾丁國家公園|墾丁|墾丁春吶|墾丁旅遊|哈墾丁|墾丁住宿|墾...

Page Load Speed

8.6 sec in total

First Response

1.6 sec

Resources Loaded

6.6 sec

Page Rendered

372 ms

kting.com.tw screenshot

About Website

Click here to check amazing Kting content. Otherwise, check out these important facts you probably never knew about kting.com.tw

跟著我們去旅行 ▲ 接駁車隊 : 【9人座小巴】福斯-T4 ▲ 【9人座小巴】新款福斯-T5 ▲ 大T5褓母車 【9人座小巴】現代 ▲ 【6人座商務車】Toyota ▲ 19人座豪華中巴 ▲ 45人座大巴

Visit kting.com.tw

Key Findings

We analyzed Kting.com.tw page load time and found that the first response time was 1.6 sec and then it took 6.9 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

kting.com.tw performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value360 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.823

4/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

kting.com.tw

1616 ms

kting.com.tw

1115 ms

creatop.css

215 ms

seo.css

418 ms

bootstrap.css

1033 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 83% of them (38 requests) were addressed to the original Kting.com.tw, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Kting.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (39%)

Content Size

4.7 MB

After Optimization

2.9 MB

In fact, the total size of Kting.com.tw main page is 4.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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.4 kB

  • Original 29.5 kB
  • After minification 27.8 kB
  • After compression 7.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 22.4 kB or 76% of the original size.

Image Optimization

-35%

Potential reduce by 1.5 MB

  • Original 4.2 MB
  • After minification 2.7 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. Obviously, Kting needs image optimization as it can save up to 1.5 MB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 130.2 kB

  • Original 228.2 kB
  • After minification 215.1 kB
  • After compression 98.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 130.2 kB or 57% of the original size.

CSS Optimization

-88%

Potential reduce by 221.0 kB

  • Original 250.0 kB
  • After minification 192.6 kB
  • After compression 29.0 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. Kting.com.tw needs all CSS files to be minified and compressed as it can save up to 221.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (34%)

Requests Now

41

After Optimization

27

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

Accessibility Review

kting.com.tw accessibility score

63

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

kting.com.tw best practices score

50

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

High

Browser errors were logged to the console

SEO Factors

kting.com.tw SEO score

82

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kting.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Kting.com.tw 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 description is not detected on the main page of Kting. 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: