9.6 sec in total
865 ms
8.3 sec
474 ms
Welcome to 168.motc.gov.tw homepage info - get ready to check 168 Motc best content for Taiwan right away, or after learning these important things about 168.motc.gov.tw
交通安全是你我生活的一部分,不論是最新交通新聞、交通法規、事故數據、主題懶人包等,都可以在168交通安全入口網找到你需要的資訊,提升交通知識並遵守交通規則,一起創造更安全便利的交通環境!
Visit 168.motc.gov.twWe analyzed 168.motc.gov.tw page load time and found that the first response time was 865 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
168.motc.gov.tw performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value39.0 s
0/100
25%
Value17.4 s
0/100
10%
Value5,980 ms
0/100
30%
Value0.075
95/100
15%
Value37.5 s
0/100
10%
865 ms
1766 ms
619 ms
1455 ms
1038 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 69% of them (77 requests) were addressed to the original 168.motc.gov.tw, 18% (20 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to External.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain 168.motc.gov.tw.
Page size can be reduced by 1.2 MB (27%)
4.5 MB
3.2 MB
In fact, the total size of 168.motc.gov.tw main page is 4.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 64.9 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 64.9 kB or 73% of the original size.
Potential reduce by 701.4 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. Obviously, 168 Motc needs image optimization as it can save up to 701.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 218.6 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 218.6 kB or 62% of the original size.
Potential reduce by 231.4 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. 168.motc.gov.tw needs all CSS files to be minified and compressed as it can save up to 231.4 kB or 84% of the original size.
Number of requests can be reduced by 24 (22%)
107
83
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 168 Motc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
168.motc.gov.tw
865 ms
index.aspx
1766 ms
index.css
619 ms
jquery-1.9.1.min.js
1455 ms
jquery.cycle2.min.js
1038 ms
oka_banner_slider_model.js
634 ms
oka.js
426 ms
ga.js
241 ms
headerBg.jpg
4908 ms
Forward.png
265 ms
facebook.gif
266 ms
plurk.gif
265 ms
twitter.gif
265 ms
youtube.png
261 ms
google.gif
500 ms
img01.jpg
897 ms
img02.jpg
1784 ms
img03.jpg
1955 ms
2014070816151675918.gif
3213 ms
2016012111125143592.jpg
1482 ms
2016012618353979182.jpg
1145 ms
2016012618352946681.jpg
1482 ms
2015111820050418092.jpg
1741 ms
2014122216030588529.jpg
1982 ms
2014122215501943010.jpg
2966 ms
2014120412193987903.png
2420 ms
2014052616135129798.png
2824 ms
2014052616052248573.jpg
2197 ms
2013122010155026560.jpg
3453 ms
2013070415003395423.png
3058 ms
2016010809062736505.jpg
3043 ms
2016010810561355818.jpg
3174 ms
2016010810411395775.jpg
3263 ms
2015011917422962958.jpg
3270 ms
2016010810291959907.jpg
3385 ms
2016010810060725238.jpg
3414 ms
2016010808503989341.jpg
3483 ms
2016010808282046373.jpg
3483 ms
2015092110430026764.jpg
3588 ms
2013022015143540351.jpg
3632 ms
2015121509202567340.jpg
3668 ms
2015121509164943860.jpg
3694 ms
2015120308591239327.jpg
3697 ms
NVCaSpGahQI
245 ms
2015120308482696989.jpg
3581 ms
__utm.gif
17 ms
2015102609332597265.jpg
3598 ms
2015102609285677835.jpg
3634 ms
2015102609252853936.jpg
3669 ms
2015102609220120914.jpg
3675 ms
2015081209095230879.jpg
3754 ms
collect
125 ms
www-embed-player-vflfNyN_r.css
69 ms
www-embed-player.js
99 ms
likebox.php
447 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
94 ms
ad_status.js
93 ms
2015081209075610694.jpg
3568 ms
UThj8VI7Xhd.css
180 ms
FL1kvZ1wVUz.css
223 ms
7HwxA8gVs6-.css
266 ms
cuTBFFsHWNo.css
349 ms
ljoX-PyMzJF.css
356 ms
q68gy-v_YMF.js
385 ms
FJmpeSpHpjS.js
407 ms
0wM5s1Khldu.js
304 ms
1bNoFZUdlYZ.js
308 ms
njO1TPvGzoR.js
371 ms
1QuX41zDRrx.js
372 ms
Oagsvfb4VWi.js
437 ms
LTv6ZK-5zxz.js
503 ms
1FCa-btixu2.js
440 ms
2015081209031778202.jpg
3208 ms
2013050910194819897.jpg
2999 ms
12400919_918158968267379_7457209825029796983_n.jpg
303 ms
safe_image.php
300 ms
safe_image.php
278 ms
safe_image.php
277 ms
12313619_896520367097906_1460903417885893940_n.jpg
272 ms
wL6VQj7Ab77.png
269 ms
s7jcwEQH7Sx.png
269 ms
QDwYpIaRyfG.png
267 ms
K00K-UgnsKu.png
266 ms
2015020616500439822.png
2673 ms
2013050910095497451.jpg
2646 ms
I6-MnjEovm5.js
53 ms
pQrUxxo5oQp.js
80 ms
2013050910092020263.jpg
2533 ms
2013050910084228263.jpg
2533 ms
2013050910053765224.jpg
2402 ms
2013050910044133354.jpg
2392 ms
QRCode.aspx
2259 ms
logo.png
2063 ms
icon-s9100fca4d7.png
1698 ms
fontlevel_bg.png
1601 ms
banner_bg.jpg
1549 ms
pix.png
1605 ms
tab_bg.png
1513 ms
line.png
1524 ms
pix03.png
1513 ms
photo_bg.png
1535 ms
left.png
1481 ms
right.png
1483 ms
prepage_btn.png
1487 ms
nextpage_btn.png
1508 ms
footerNavbg.png
1531 ms
footer.jpg
1485 ms
gov.gif
1473 ms
index_37.jpg
1434 ms
getGallery.ashx
1556 ms
pix03_ov.png
1504 ms
168.motc.gov.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.
168.motc.gov.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
168.motc.gov.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 168.motc.gov.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 168.motc.gov.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.
168.motc.gov.tw
Open Graph description is not detected on the main page of 168 Motc. 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: