Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

otop.tw

經濟部中小及新創企業署OTOP城鄉特色網

Page Load Speed

15.9 sec in total

First Response

823 ms

Resources Loaded

14.8 sec

Page Rendered

341 ms

otop.tw screenshot

About Website

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

Key Findings

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

Performance Metrics

otop.tw performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

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

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

Page size can be reduced by 933.9 kB (35%)

Content Size

2.7 MB

After Optimization

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.

HTML Optimization

-82%

Potential reduce by 52.8 kB

  • Original 64.1 kB
  • After minification 55.9 kB
  • After compression 11.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. 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.

Image Optimization

-7%

Potential reduce by 119.0 kB

  • Original 1.7 MB
  • After minification 1.6 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. Otop images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 288.2 kB

  • Original 355.8 kB
  • After minification 193.4 kB
  • After compression 67.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 288.2 kB or 81% of the original size.

CSS Optimization

-84%

Potential reduce by 473.9 kB

  • Original 564.2 kB
  • After minification 475.3 kB
  • After compression 90.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. 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.

Requests Breakdown

Number of requests can be reduced by 44 (44%)

Requests Now

100

After Optimization

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.

Accessibility Review

otop.tw accessibility score

89

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

otop.tw best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

otop.tw SEO score

58

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: