Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kingstone.com.tw

金石堂

Page Load Speed

7.2 sec in total

First Response

375 ms

Resources Loaded

6.7 sec

Page Rendered

134 ms

About Website

Visit kingstone.com.tw now to see the best up-to-date Kingstone content for Taiwan and also check out these interesting facts you probably never knew about kingstone.com.tw

金石堂,網路購物網包含各類書籍、英文書購書網、雜誌以及影音商品,百貨涵蓋文具、禮品、服飾配件、生活用品。歡迎您來網路書店買書,天天都有特價優惠活動!

Visit kingstone.com.tw

Key Findings

We analyzed Kingstone.com.tw page load time and found that the first response time was 375 ms and then it took 6.8 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

kingstone.com.tw performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

kingstone.com.tw

375 ms

www.kingstone.com.tw

1094 ms

jquery-3.7.1.min.js

494 ms

264.70f01ea3.css

505 ms

8147.90397c67.css

508 ms

Our browser made a total of 271 requests to load all elements on the main page. We found that 9% of them (25 requests) were addressed to the original Kingstone.com.tw, 82% (221 requests) were made to Cdn1.kingstone.com.tw and 2% (5 requests) were made to Avivid.likr.tw. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Cdn1.kingstone.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.3 kB (28%)

Content Size

1.9 MB

After Optimization

1.4 MB

In fact, the total size of Kingstone.com.tw main page is 1.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 850.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 464.1 kB

  • Original 554.0 kB
  • After minification 490.3 kB
  • After compression 89.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 63.7 kB, which is 11% 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 464.1 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 32.8 kB

  • Original 850.1 kB
  • After minification 817.3 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. Kingstone images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 20.2 kB

  • Original 445.7 kB
  • After minification 445.7 kB
  • After compression 425.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 2.2 kB

  • Original 24.6 kB
  • After minification 24.6 kB
  • After compression 22.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. Kingstone.com.tw has all CSS files already compressed.

Requests Breakdown

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

Requests Now

263

After Optimization

227

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

Accessibility Review

kingstone.com.tw accessibility score

78

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

kingstone.com.tw best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

kingstone.com.tw SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingstone.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Kingstone.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 data is detected on the main page of Kingstone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: