5.4 sec in total
433 ms
4.6 sec
402 ms
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.twWe 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.
webike.tw performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.6 s
1/100
25%
Value8.9 s
15/100
10%
Value680 ms
44/100
30%
Value0
100/100
15%
Value9.8 s
28/100
10%
433 ms
1801 ms
767 ms
586 ms
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 size can be reduced by 1.1 MB (25%)
4.2 MB
3.2 MB
In fact, the total size of Webike.tw main page is 4.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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 362.8 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.
Potential reduce by 23.1 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. Webike images are well optimized though.
Potential reduce by 337.8 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 337.8 kB or 64% of the original size.
Potential reduce by 349.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.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.
Number of requests can be reduced by 42 (47%)
89
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.
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
bootstrap.min.js+jquery.lazyload.min.js+cycle.js.pagespeed.jc.9wBEI6q8dG.js
601 ms
jquery.searcher.js
908 ms
purl.js
936 ms
jquery-ui.css
9 ms
jquery-ui.min.js
11 ms
cycle2.js.pagespeed.jm.tMy2LhmvwI.js
381 ms
gpt.js
20 ms
analytics.js
17 ms
fbevents.js
60 ms
185x49xwebike_shop_logo.png.pagespeed.ic.PS_bHRMdUM.png
195 ms
1.JiBnMqyl6S.gif
201 ms
520x205x2016-02-28RandomVdh58.png.pagespeed.ic.-Lk_8nAlah.png
747 ms
520x205x2016-02-28RandomTjDdi.png.pagespeed.ic.75-gu2-ar0.jpg
609 ms
520x205x2016-02-28Random57DtS.png.pagespeed.ic.2heUQBlbcm.jpg
656 ms
520x205x2016-03-01Randoms4CL5.png.pagespeed.ic.aGsDvm5ZbM.jpg
739 ms
520x205x2016-02-23Randomxno2e.png.pagespeed.ic.aJaGCYkK2E.jpg
610 ms
520x205x2016-02-17RandomQ2aN1.png.pagespeed.ic.gsDhcSQ_MN.jpg
766 ms
pubads_impl_81.js
14 ms
collect
28 ms
ads
54 ms
container.html
14 ms
collect
89 ms
108 ms
12139377250002637379
28 ms
osd.js
11 ms
ga-audiences
40 ms
x2016march-centerlong.png.pagespeed.ic.o0Dsv7MsKk.png
423 ms
xwebike_conf.png.pagespeed.ic.I2jiJgJ_6f.png
413 ms
xmotomarket_conf.png.pagespeed.ic.Ag1cn-B3Js.png
457 ms
arrow.gif.pagespeed.ce.bF7aETgqzn.gif
564 ms
sell_ranking.png.pagespeed.ce.FouQjbKFHF.png
543 ms
xranking1.png.pagespeed.ic.lBAi0dkOKd.jpg
547 ms
xranking2.png.pagespeed.ic.GCM8F6TOr9.jpg
564 ms
xranking3.png.pagespeed.ic.8zRl_VzSCO.jpg
568 ms
sdk.js
78 ms
xbikeNews_title.png.pagespeed.ic.Ad68TG4V5o.png
589 ms
xmore-button.png.pagespeed.ic.j6ngClpWpK.png
654 ms
xbotton-1.png.pagespeed.ic.Cx_qatvKx9.png
668 ms
xwelcome-join-btn.png.pagespeed.ic.iwOgtiQNH8.png
672 ms
ximpression_title.png.pagespeed.ic.JcR0dcgZw2.png
683 ms
xstar.png.pagespeed.ic.ERvMTANFQe.png
700 ms
xnewmotor_title.png.pagespeed.ic.ltBxty5l2k.png
762 ms
xmagazine_title.png.pagespeed.ic.W0Z_xwm7qa.png
835 ms
120x80xP1160960-680x510.jpg.pagespeed.ic.X59sBRToPc.jpg
800 ms
260x104x2016-02-17RandomAPDAF.png.pagespeed.ic.PEqVkZnMRM.jpg
806 ms
260x104x2016-02-03RandomDETto.png.pagespeed.ic.27zGf1lkJ7.png
1007 ms
260x104x2016-01-28RandomYbOv2.png.pagespeed.ic.ktzN7zABUV.png
1030 ms
260x104x2016-01-15Random3wx8v.png.pagespeed.ic.iprW6NvhuD.jpg
909 ms
260x104x2016-01-07Random6pabj.png.pagespeed.ic.UbrXLyhBaM.png
1144 ms
260x104x2015-12-16RandomCwlKu.png.pagespeed.ic.xWf77fvg_Y.png
1170 ms
260x104x2015-12-17RandomkfpeO.png.pagespeed.ic.niYV-2xAsQ.jpg
992 ms
260x104x2015-12-08Random8EISQ.png.pagespeed.ic.eLfie8z37p.jpg
1110 ms
260x104x2015-11-27RandomczhN8.png.pagespeed.ic.InSFmhjJrW.jpg
1181 ms
260x104x2015-10-21RandomPHrkE.png.pagespeed.ic.2TxOYAGXyN.png
1382 ms
220x280xwecome-join.png.pagespeed.ic.CjEz8ZOkWv.png
1222 ms
xmitumori.png.pagespeed.ic.tStaVt8qJF.png
1311 ms
groupbuy.png.pagespeed.ce.vMKtdVniwj.png
1326 ms
ads
295 ms
71 ms
ui-bg_flat_75_ffffff_40x100.png
43 ms
xd_arbiter.php
69 ms
xd_arbiter.php
111 ms
like_box.php
80 ms
KK5J6ESEOVy.css
140 ms
8kIrqK5BWyG.css
160 ms
_rx8naC75Dy.js
191 ms
x5F9OMjKyLw.js
231 ms
ICDbTSzjQEg.js
210 ms
TTCre3391I0.js
209 ms
expansion_embed.js
15 ms
m_js_controller.js
6 ms
favicon
89 ms
abg.js
44 ms
googlelogo_color_112x36dp.png
74 ms
nessie_icon_tiamat_white.png
71 ms
s
50 ms
x_button_blue2.png
17 ms
11182292_287169564740005_5828602394573386700_n.jpg
106 ms
198263_202551609868468_578656417_n.png
123 ms
11215126_932678586819231_9201603558501745957_n.jpg
204 ms
11987168_975996472465127_5911772801554008330_n.jpg
152 ms
12800385_1548812512114332_1055929309871303067_n.jpg
288 ms
10917417_1414317678861545_5571853217340952036_n.jpg
154 ms
wL6VQj7Ab77.png
58 ms
s7jcwEQH7Sx.png
58 ms
activeview
13 ms
I6-MnjEovm5.js
17 ms
vlXaquuXMrr.js
21 ms
webike.tw accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
webike.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
webike.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
ZH
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.
webike.tw
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: