Tools & Wizards About Us

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

waca.net

WACA 你的全通路開店夥伴：網路開店｜零售POS｜預約管理

Page Load Speed

2.2 sec in total

First Response

57 ms

Resources Loaded

1.3 sec

Page Rendered

808 ms

About Website

Welcome to waca.net homepage info - get ready to check WACA best content for Taiwan right away, or after learning these important things about waca.net

簡單上手的線上開店服務，提供完整電商支援，從品牌初創到深度經營、線上下零售到體驗服務預約，為商家開啟多領域全通路銷售事業，不抽成不綁約，免費試用30天！

Visit waca.net

Key Findings

We analyzed Waca.net page load time and found that the first response time was 57 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

waca.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

waca.net

57 ms

www.waca.net

1003 ms

style.css

9 ms

vendor.css

64 ms

all.css

17 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 84% of them (49 requests) were addressed to the original Waca.net, 7% (4 requests) were made to Googletagmanager.com and 3% (2 requests) were made to S.yimg.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Waca.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 88.4 kB (7%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waca.net main page is 1.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. 75% 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 937.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 66.1 kB

  • Original 77.6 kB
  • After minification 47.2 kB
  • After compression 11.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 30.4 kB, which is 39% 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 66.1 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 22.2 kB

  • Original 937.5 kB
  • After minification 915.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. WACA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 72 B

  • Original 183.3 kB
  • After minification 183.3 kB
  • After compression 183.2 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

-0%

Potential reduce by 78 B

  • Original 42.2 kB
  • After minification 42.2 kB
  • After compression 42.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. Waca.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (20%)

Requests Now

55

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WACA. 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 as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

waca.net accessibility score

82

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

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

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

waca.net best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

waca.net SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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