7.4 sec in total
1.7 sec
5.5 sec
201 ms
Click here to check amazing Okgo content for Taiwan. Otherwise, check out these important facts you probably never knew about okgo.tw
玩全台灣旅遊網有豐富的台灣旅遊景點以及齊全的台灣民宿、台灣飯店等台灣住宿,包括日月潭民宿、清境民宿、埔里民宿、墾丁民宿、集集民宿、淡水民宿、綠島民宿、溪頭民宿、九份民宿、宜蘭民宿、花蓮民宿、台東民宿、澎湖民宿、南投民宿、台北民宿
Visit okgo.twWe analyzed Okgo.tw page load time and found that the first response time was 1.7 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
okgo.tw performance score
name
value
score
weighting
Value11.3 s
0/100
10%
Value13.8 s
0/100
25%
Value12.2 s
3/100
10%
Value1,670 ms
11/100
30%
Value0.149
76/100
15%
Value22.1 s
1/100
10%
1693 ms
416 ms
638 ms
34 ms
833 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Okgo.tw, 51% (46 requests) were made to Img3.okgo.tw and 11% (10 requests) were made to Image.okgo.tw. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Img3.okgo.tw.
Page size can be reduced by 874.6 kB (17%)
5.1 MB
4.2 MB
In fact, the total size of Okgo.tw main page is 5.1 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 199.3 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 199.3 kB or 80% of the original size.
Potential reduce by 294.8 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. Okgo images are well optimized though.
Potential reduce by 288.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 288.2 kB or 66% of the original size.
Potential reduce by 92.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. Okgo.tw needs all CSS files to be minified and compressed as it can save up to 92.3 kB or 87% of the original size.
Number of requests can be reduced by 23 (27%)
86
63
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Okgo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
okgo.tw
1693 ms
layout_base.css
416 ms
type_base.css
638 ms
jquery.min.js
34 ms
jquery.easing.1.3.js
833 ms
jquery.floatinglayer.min.js
842 ms
jquery-ui.min.js
55 ms
jquery-ui-tabs-rotate.js
662 ms
tw_cn.js
1127 ms
main.js
416 ms
WebResource.axd
832 ms
gpt.js
23 ms
201512011201490112_D3.jpg
1455 ms
201504291659011784_B3.jpg
1262 ms
201601021429055399_B5.jpg
1674 ms
201511111159516777_B2.jpg
1693 ms
201511111553276241_B1.jpg
1691 ms
201511111546547768_B4.jpg
1496 ms
201511111601363638_C1.jpg
1890 ms
201511111643171856_C3.jpg
2275 ms
201511111608282059_C4.jpg
2137 ms
201511241738425479_C2.jpg
2293 ms
facebook.gif
229 ms
twitter.gif
230 ms
tw_on.jpg
227 ms
cn_off.jpg
229 ms
uploadify-cancel.png
659 ms
searchtitle.png
410 ms
searcha.png
659 ms
201602051709332120_A.jpg
833 ms
201601210914007870_D2.jpg
1322 ms
201601210912053491_D1.jpg
891 ms
b20160224110540.jpg
1230 ms
b20160204163646_9808_0.jpg
2840 ms
b20130614172628_10025_0.jpg
1652 ms
b20160224161838_9639_0.jpg
2294 ms
b20090523140013_000259_0.jpg
1339 ms
b20131220100638_9648_0.jpg
1653 ms
s20141215105707_6507_0.jpg
1549 ms
s20141022123615_5197_0.jpg
1573 ms
s20120924152032_10715_0.jpg
1773 ms
b20150120140745_9322_0.jpg
2029 ms
s20150813155609_8513_0.jpg
1865 ms
s20131011150519_9758_0.jpg
1874 ms
s20140927002024_9261_0.jpg
1998 ms
b20151117145851_9144_0.jpg
2695 ms
s20151225173043_8378_0.jpg
2081 ms
s20150622135712_8712_0.jpg
2222 ms
s20140828002416_10351_0.jpg
2257 ms
bg_header1.jpg
2484 ms
logo.png
2436 ms
menu.png
2474 ms
icon.png
2493 ms
i.png
2656 ms
i-search.png
2697 ms
sales_arrow.png
216 ms
pubads_impl_81.js
27 ms
sales_title.png
2695 ms
sales_arrow.png
2698 ms
morebg.png
2865 ms
analytics.js
59 ms
sdk.js
150 ms
ads
316 ms
container.html
23 ms
collect
24 ms
collect
58 ms
hot_travel_title.png
2685 ms
arrow01.jpg
2711 ms
hot_view_icon.png
2703 ms
132 ms
tbg.jpg
2700 ms
xd_arbiter.php
123 ms
xd_arbiter.php
260 ms
ft1.png
2634 ms
expansion_embed.js
18 ms
css
110 ms
m_js_controller.js
84 ms
favicon
100 ms
abg.js
88 ms
favicon
99 ms
favicon
963 ms
googlelogo_color_112x36dp.png
54 ms
favicon
200 ms
nessie_icon_tiamat_white.png
86 ms
osd.js
34 ms
x_button_blue2.png
79 ms
s
63 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
53 ms
hotview_navbg.jpg
2456 ms
activeview
15 ms
okgo.tw accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
ARIA IDs are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
okgo.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
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
okgo.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Okgo.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Okgo.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.
okgo.tw
Open Graph data is detected on the main page of Okgo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: