Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

wdc2016.taipei

2016 臺北世界設計之都 |

Page Load Speed

16 sec in total

First Response

2.5 sec

Resources Loaded

13.3 sec

Page Rendered

231 ms

wdc2016.taipei screenshot

About Website

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.taipei

Key Findings

We 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.

Performance Metrics

wdc2016.taipei performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value18.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.0 s

0/100

25%

SI (Speed Index)

Value25.8 s

0/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

wdc2016.taipei

2481 ms

styles.css

457 ms

print.css

456 ms

frontend.min.css

907 ms

last_minute_fixes.css

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 Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (58%)

Content Size

4.8 MB

After Optimization

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.

HTML Optimization

-85%

Potential reduce by 101.7 kB

  • Original 119.5 kB
  • After minification 96.0 kB
  • After compression 17.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 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.

Image Optimization

-6%

Potential reduce by 90.2 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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.

JavaScript Optimization

-75%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.3 MB
  • After compression 369.1 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 1.1 MB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 251.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. 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.

Requests Breakdown

Number of requests can be reduced by 54 (68%)

Requests Now

80

After Optimization

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.

Accessibility Review

wdc2016.taipei accessibility score

85

Accessibility Issues

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[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

High

Some elements have a [tabindex] value greater than 0

Best Practices

wdc2016.taipei best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wdc2016.taipei SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    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.

Social Sharing Optimization

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: