16 sec in total
2.5 sec
13.3 sec
231 ms
Visit wdc2016.taipei now to see the best up-to-date Wdc 2016 content for Taiwan and also check out these interesting facts you probably never knew about wdc2016.taipei
Adaptive City 不斷提昇的城市是臺北市申辦2016世界設計之都的核心訴求:如何運用創新的設計思考,促進城市治理的求新求變,為市民創造生活的福祉,帶來更好的宜居生活品質,打造一座具有設計遠見的前瞻城市,是臺北市不斷思考與尋求進步的目標與方向
Visit wdc2016.taipeiWe analyzed Wdc2016.taipei page load time and found that the first response time was 2.5 sec and then it took 13.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wdc2016.taipei performance score
name
value
score
weighting
Value18.6 s
0/100
10%
Value26.0 s
0/100
25%
Value25.8 s
0/100
10%
Value880 ms
32/100
30%
Value0
100/100
15%
Value24.3 s
0/100
10%
2481 ms
457 ms
456 ms
907 ms
451 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 85% of them (72 requests) were addressed to the original Wdc2016.taipei, 5% (4 requests) were made to Graph.facebook.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Wdc2016.taipei.
Page size can be reduced by 2.8 MB (58%)
4.8 MB
2.0 MB
In fact, the total size of Wdc2016.taipei main page is 4.8 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. 45% of websites need less resources to load. CSS take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 101.7 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 23.5 kB, which is 20% 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 101.7 kB or 85% of the original size.
Potential reduce by 90.2 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. Wdc 2016 images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 75% of the original size.
Potential reduce by 1.5 MB
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. Wdc2016.taipei needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 86% of the original size.
Number of requests can be reduced by 54 (68%)
80
26
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wdc 2016. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wdc2016.taipei
2481 ms
styles.css
457 ms
print.css
456 ms
frontend.min.css
907 ms
last_minute_fixes.css
451 ms
ultimate.min.css
873 ms
Defaults.css
692 ms
custom.css
942 ms
other.css
1094 ms
responsive.css
470 ms
main.css
1573 ms
jquery.js
1118 ms
jquery-migrate.min.js
877 ms
bootstrap.min.js
897 ms
bootstrap-select.js
916 ms
jquery.ui.core.min.js
1097 ms
jquery.ui.widget.min.js
1094 ms
jquery.ui.accordion.min.js
1122 ms
jquery.ui.mouse.min.js
1131 ms
jquery.ui.slider.min.js
1310 ms
jquery.ui.resizable.min.js
1318 ms
jquery.ui.draggable.min.js
1339 ms
jquery.ui.button.min.js
1348 ms
jquery.ui.position.min.js
1344 ms
jquery.ui.dialog.min.js
1523 ms
jquery.ui.tabs.min.js
1536 ms
jquery.ui.sortable.min.js
1557 ms
jquery.ui.droppable.min.js
1560 ms
jquery.ui.datepicker.min.js
1571 ms
jquery.ui.menu.min.js
1737 ms
jquery.ui.autocomplete.min.js
1758 ms
frontend.min.js
2011 ms
ultimate.min.js
2217 ms
ie_alert_style.css
1800 ms
ts-visual-composer-extend-animations.min.css
2166 ms
ts-visual-composer-extend-front.min.css
1977 ms
jquery.form.min.js
1778 ms
scripts.js
1798 ms
imgload.js
2004 ms
main.js
1984 ms
other.js
2076 ms
waypoints.min.js
1705 ms
ts-visual-composer-extend-front.min.js
1931 ms
js_composer_front.js
1708 ms
style.css
890 ms
icon_401.png
263 ms
icon_80-11.png
259 ms
logo31.png
261 ms
facebook2.png
260 ms
aplus.jpg
262 ms
wdc-icon-15.png
406 ms
%E8%87%BA%E5%8C%97%E5%B8%82%E9%95%B7%E6%9F%AF%E6%96%87%E5%93%B2%E5%8F%B32%E3%80%81%E6%96%87%E5%8C%96%E5%B1%80%E9%95%B7%E8%AC%9D%E4%BD%A9%E9%9C%93%E5%8F%B33%E3%80%81%E5%B0%8E%E6%BC%94%E6%A5%8A%E5%8A%9B%E5%B7%9E%E5%B7%A62%E3%80%81%E5%9F%BA%E9%87%91%E6%9C%83%E7%A7%98%E6%9B%B8%E9%95%B7%E6%9E%97%E5%A4%A9%E4%BE%86%E5%B7%A61%E5%8F%83%E8%A7%80%E6%9B%B8%E5%B1%95%E8%A8%AD%E8%A8%88%E4%B9%8B%E9%83%BD%E5%B1%95%E5%8D%80%EF%BC%8C%E8%88%87%E7%AD%96%E5%B1%95%E4%BA%BA%E9%BB%83%E5%AF%B6%E7%90%B4%E5%8F%B31%E5%90%88%E5%BD%B1.jpg
1491 ms
share-icon-18.png
459 ms
WDCVI-3.jpg
1101 ms
WDCVISUAL.jpg
1356 ms
AKIBO2.jpg
4212 ms
icsid-logo.png
536 ms
tpi-logo.png
667 ms
dca-logo.png
755 ms
tdc-logo.png
881 ms
rado-logo.png
974 ms
wdc-patten-011.png
1302 ms
wdc-taipeilogo.png
1170 ms
wdc-icon-13.png
1292 ms
wdc-icon-14.png
1394 ms
wdc-icon-15.png
1511 ms
icomoon.woff
1943 ms
fontello.woff
1563 ms
analytics.js
47 ms
gtm.js
199 ms
collect
27 ms
collect
73 ms
conversion_async.js
30 ms
collect
12 ms
collect
75 ms
36 ms
35 ms
fql
149 ms
fql
203 ms
fql
245 ms
fql
248 ms
%E8%87%BA%E5%8C%97%E5%B8%82%E9%95%B7%E6%9F%AF%E6%96%87%E5%93%B2%E5%8F%B32%E3%80%81%E6%96%87%E5%8C%96%E5%B1%80%E9%95%B7%E8%AC%9D%E4%BD%A9%E9%9C%93%E5%8F%B33%E3%80%81%E5%B0%8E%E6%BC%94%E6%A5%8A%E5%8A%9B%E5%B7%9E%E5%B7%A62%E3%80%81%E5%9F%BA%E9%87%91%E6%9C%83%E7%A7%98%E6%9B%B8%E9%95%B7%E6%9E%97%E5%A4%A9%E4%BE%86%E5%B7%A61%E5%8F%83%E8%A7%80%E6%9B%B8%E5%B1%95%E8%A8%AD%E8%A8%88%E4%B9%8B%E9%83%BD%E5%B1%95%E5%8D%80%EF%BC%8C%E8%88%87%E7%AD%96%E5%B1%95%E4%BA%BA%E9%BB%83%E5%AF%B6%E7%90%B4%E5%8F%B31%E5%90%88%E5%BD%B1.jpg
1771 ms
WDCVI-3.jpg
1079 ms
WDCVISUAL.jpg
1499 ms
AKIBO2.jpg
3892 ms
wdc2016.taipei 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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
wdc2016.taipei 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wdc2016.taipei 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
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wdc2016.taipei 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 Wdc2016.taipei 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.
wdc2016.taipei
Open Graph description is not detected on the main page of Wdc 2016. 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: