Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

webike.ph

Webike: Motorcycle Parts, Accessories, Gears, OEM parts & Reviews

Page Load Speed

10.3 sec in total

First Response

414 ms

Resources Loaded

9.3 sec

Page Rendered

573 ms

webike.ph screenshot

About Website

Click here to check amazing Webike content for Philippines. Otherwise, check out these important facts you probably never knew about webike.ph

World's largest online store of Motorcycle parts. Huge stock of custom parts, gears and OEM parts with various shipping and payment. Experience over 2mil. items and true Japaense quality & service.

Visit webike.ph

Key Findings

We analyzed Webike.ph page load time and found that the first response time was 414 ms and then it took 9.9 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

webike.ph performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.459

19/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

webike.ph

414 ms

www.webike.ph

386 ms

www.webike.ph

1295 ms

common_v3.css

1083 ms

w3.css

1089 ms

Our browser made a total of 157 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Webike.ph, 92% (144 requests) were made to Img.webike-cdn.net and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Img.webike-cdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.3 kB (9%)

Content Size

2.4 MB

After Optimization

2.2 MB

In fact, the total size of Webike.ph main page is 2.4 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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 150.7 kB

  • Original 184.2 kB
  • After minification 165.6 kB
  • After compression 33.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. 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 150.7 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 42.5 kB

  • Original 2.0 MB
  • After minification 1.9 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

-7%

Potential reduce by 13.7 kB

  • Original 202.9 kB
  • After minification 202.6 kB
  • After compression 189.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

-13%

Potential reduce by 6.4 kB

  • Original 48.7 kB
  • After minification 48.7 kB
  • After compression 42.3 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.ph needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (38%)

Requests Now

154

After Optimization

95

The browser has sent 154 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 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

webike.ph accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

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

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

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.

SEO Factors

webike.ph SEO score

83

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

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 Webike.ph 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 Webike.ph 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: