15.9 sec in total
823 ms
14.8 sec
341 ms
Welcome to otop.tw homepage info - get ready to check Otop best content for Taiwan right away, or after learning these important things about otop.tw
依據行政院頒布之前瞻基礎建設計畫,經濟部發展城鄉特色產業,導入循環經濟、體驗經濟與數位經濟三大概念,規劃設置城鄉特色產業園區,輔導中小企業城鄉創生轉型,建立區域產業生態鏈,帶動產業升級轉型。
Visit otop.twWe analyzed Otop.tw page load time and found that the first response time was 823 ms and then it took 15.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
otop.tw performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
823 ms
911 ms
852 ms
632 ms
1063 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Otop.tw, 7% (7 requests) were made to Google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Otop.tw.
Page size can be reduced by 933.9 kB (35%)
2.7 MB
1.7 MB
In fact, the total size of Otop.tw main page is 2.7 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 52.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 8.3 kB, which is 13% 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 52.8 kB or 82% of the original size.
Potential reduce by 119.0 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. Otop 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 81% of the original size.
Potential reduce by 473.9 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. Otop.tw needs all CSS files to be minified and compressed as it can save up to 473.9 kB or 84% of the original size.
Number of requests can be reduced by 44 (44%)
100
56
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.otop.tw
823 ms
www.otop.tw
911 ms
jquery.min.js
852 ms
bootstrap.min.js
632 ms
product_banner.css
1063 ms
run_style.css
641 ms
pcmenu.css
651 ms
megamenu.css
651 ms
megamenu.js
1260 ms
m_bootstrap.css
1269 ms
m_menu.css
1284 ms
m_menu_2.css
1295 ms
slidebars.css
1489 ms
main.js
1698 ms
modernizr.js
2112 ms
slidebars.js
1902 ms
owl.carousel.css
1894 ms
owl.theme.css
1933 ms
owl.carousel.js
2147 ms
bootstrap.css
2564 ms
bootstrap-theme.css
2524 ms
jquery.goup.min.js
2528 ms
main.js
2576 ms
index_tab.css
2744 ms
style.css
2768 ms
all.js
3157 ms
sweetalert.css
3170 ms
sweetalert-dev.js
3595 ms
bootstrap-datepicker3.css
3220 ms
bootstrap-datepicker.js
3605 ms
otop_index.js
3458 ms
jsapi
54 ms
t13n
71 ms
brand
51 ms
animate.min.css
3812 ms
main.css
3801 ms
banner_style.css
3869 ms
nav.css
4087 ms
custom.js
4219 ms
selectnav.js
4218 ms
brand
64 ms
t13n
55 ms
css
58 ms
analytics.js
57 ms
slider.js
892 ms
collect
24 ms
slidebars-logo2x.png
478 ms
menu_icon.png
237 ms
user_icon.png
237 ms
slidebars-logo-white2x.png
622 ms
m_icon_1.png
639 ms
m_icon_2.png
641 ms
m_icon_3.png
834 ms
m_icon_4.png
867 ms
m_icon_5.png
1249 ms
u_fb.png
1270 ms
u_login.png
1271 ms
u_car.png
1293 ms
u_en.png
1465 ms
securimage_img
1585 ms
refresh.gif
1891 ms
audio_icon.png
1887 ms
logo.png
2132 ms
facebook_icon.jpg
1922 ms
google_icon.jpg
2108 ms
twitter_icon.jpg
2225 ms
login_icon.jpg
2521 ms
en_icon.jpg
2533 ms
order_icon.jpg
2543 ms
search_icon.jpg
2752 ms
%E5%8E%9F%E7%9C%9F%E8%87%BA%E7%81%A3VypP.jpg
3463 ms
%E5%89%B5%E6%96%B0%E8%A8%AD%E8%A8%887gxH.jpg
3671 ms
%E7%B6%BB%E6%94%BE%E5%9C%A8%E5%9C%B0%E7%89%B9%E8%89%B2gSiX.jpg
3786 ms
IMG_7119qM6G.JPG
3844 ms
123G3xT.jpg
3837 ms
2A3Yw.jpg
4057 ms
%E6%9C%AA%E5%91%BD%E5%90%8D-1iAUKiQ.jpg
4668 ms
%E4%B8%BB%E5%9C%96ac3yPy.jpg
4703 ms
1xFYstB.jpg
4676 ms
6%E8%8A%B1%E9%B3%A5%E9%A2%A8%E6%9C%88-%E6%A9%AB2Hndwzq.JPG
5092 ms
1BfeAZg.jpg
4999 ms
49 ms
641CbwBaY.jpg
5124 ms
transliteration.css
5 ms
transliteration.I.js
12 ms
44 ms
%E5%BA%95%E9%83%A8_%E5%84%AA%E8%B3%AA%E4%BC%81%E6%A5%AD%E7%8D%8E_bannerjNDB.jpg
5065 ms
inputtools.js
10 ms
glyphicons-halflings-regular.woff
5313 ms
%E5%BA%95%E9%83%A8_%E7%94%A2%E5%93%81%E8%A8%AD%E8%A8%88%E7%8D%8EVUxk.jpg
5068 ms
%E5%BA%95%E9%83%A8_%E7%94%A2%E5%93%81%E7%99%BB%E9%8C%84InS6.jpg
5239 ms
%E5%BA%95%E9%83%A8_%E5%B1%95%E5%94%AE%E6%9C%83%E5%A0%B1%E5%90%8D%E7%B6%B2n6AT.jpg
5081 ms
banner-275X183XmB7.jpg
5315 ms
f_link_1.jpg
5098 ms
f_link_2.jpg
5322 ms
f_link_3.jpg
4949 ms
f_link_4.jpg
5091 ms
foot_logo.png
5208 ms
aaa.png
5286 ms
gov.png
5133 ms
%E9%A6%96%E9%A0%81_2014%E7%94%A2%E5%93%81%E8%A8%AD%E8%A8%88%E7%8D%8E01S6PG.jpg
6263 ms
%E9%A6%96%E9%A0%81_2014%E7%94%A2%E5%93%81%E8%A8%AD%E8%A8%88%E7%8D%8E02WJ5p.jpg
5837 ms
bg1zXji.jpg
5978 ms
gototop.png
5189 ms
otop.tw accessibility score
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
otop.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
otop.tw SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otop.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Otop.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.
otop.tw
Open Graph description is not detected on the main page of Otop. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: