Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

holkee.com

holkee 隨選隨用、輕鬆創業

Page Load Speed

10.9 sec in total

First Response

452 ms

Resources Loaded

9.7 sec

Page Rendered

770 ms

About Website

Click here to check amazing Holkee content for Taiwan. Otherwise, check out these important facts you probably never knew about holkee.com

3 分鐘架站、不管是電商經營、品牌形象網站產出都比你想得還要快速簡單

Visit holkee.com

Key Findings

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

Performance Metrics

holkee.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

holkee.com

452 ms

www.holkee.com

886 ms

all.min.css

859 ms

flexslider.min.css

645 ms

index.min.css

854 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 24% of them (13 requests) were addressed to the original Holkee.com, 71% (39 requests) were made to Img.holkee.com and 2% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Img.holkee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.9 kB (3%)

Content Size

4.3 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 20.5 kB

  • Original 27.0 kB
  • After minification 20.4 kB
  • After compression 6.5 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 6.6 kB, which is 25% 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 20.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 3.7 kB

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

JavaScript Optimization

-0%

Potential reduce by 26 B

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

CSS Optimization

-78%

Potential reduce by 102.6 kB

  • Original 132.4 kB
  • After minification 132.3 kB
  • After compression 29.8 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. Holkee.com needs all CSS files to be minified and compressed as it can save up to 102.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (12%)

Requests Now

49

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

holkee.com accessibility score

51

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.

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

Links do not have a discernible name

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

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

holkee.com SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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