Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    46% of websites

  • 91

    SEO

    Google-friendlier than
    76% of websites

webike.tw

Webike台灣 | 重機、機車改裝零件騎士用品・車輛買賣・業界新聞,摩托車資訊滿載

Page Load Speed

5.4 sec in total

First Response

433 ms

Resources Loaded

4.6 sec

Page Rendered

402 ms

webike.tw screenshot

About Website

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

超過一百萬項以上的改裝零件、人身部品以及原廠零件,摩托車新聞、新車中古車買賣每天更新。歡迎來到台灣最大摩托車入口網站,讓Webike滿足您的摩托人生!

Visit webike.tw

Key Findings

We analyzed Webike.tw page load time and found that the first response time was 433 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

webike.tw performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

1/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

webike.tw

433 ms

www.webike.tw

1801 ms

A.old_webikeStyle.css.pagespeed.cf.IIgngNVc8E.css

767 ms

A.editor_new.css.pagespeed.cf.iBW8l8sVA6.css

586 ms

jquery.min.js

23 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 47% of them (44 requests) were addressed to the original Webike.tw, 11% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Webike.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (26%)

Content Size

4.3 MB

After Optimization

3.2 MB

In fact, the total size of Webike.tw 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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 362.8 kB

  • Original 441.2 kB
  • After minification 310.0 kB
  • After compression 78.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. This page needs HTML code to be minified as it can gain 131.2 kB, which is 30% 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 362.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 23.1 kB

  • Original 2.9 MB
  • After minification 2.8 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. Webike images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 375.9 kB

  • Original 585.8 kB
  • After minification 565.4 kB
  • After compression 209.9 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 375.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 349.3 kB

  • Original 419.9 kB
  • After minification 417.6 kB
  • After compression 70.6 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. Webike.tw needs all CSS files to be minified and compressed as it can save up to 349.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (47%)

Requests Now

89

After Optimization

47

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

Accessibility Review

webike.tw accessibility score

85

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

Heading elements are not in a sequentially-descending order

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

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

webike.tw best practices score

69

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

webike.tw SEO score

91

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

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