Tools & Wizards About Us
oo.com.tw screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

oo.com.tw

網站設計達人｜網頁設計只要$6000，超值網站製作與架設服務

Page Load Speed

7.9 sec in total

First Response

573 ms

Resources Loaded

6.8 sec

Page Rendered

492 ms

oo.com.tw screenshot

About Website

Welcome to oo.com.tw homepage info - get ready to check Oo best content for Taiwan right away, or after learning these important things about oo.com.tw

高 CP 網頁設計、網站架設選擇。免費升級響應式網站設計，提供完整教育訓練，最佳服務品質！成立於台中，全台網站製作服務，網頁設計公司最佳選擇。

Visit oo.com.tw

Key Findings

We analyzed Oo.com.tw page load time and found that the first response time was 573 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

oo.com.tw performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.337

33/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

oo.com.tw

573 ms

oo.com.tw

1211 ms

init.js

145 ms

bundle.css

1597 ms

bundle.min.js

1197 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 84% of them (68 requests) were addressed to the original Oo.com.tw, 4% (3 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Oo.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.8 kB (33%)

Content Size

654.9 kB

After Optimization

439.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oo.com.tw main page is 654.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 286.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 101.5 kB

  • Original 123.3 kB
  • After minification 80.4 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 43.0 kB, which is 35% 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.5 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 6.4 kB

  • Original 118.1 kB
  • After minification 111.7 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. Oo images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 53.8 kB

  • Original 286.2 kB
  • After minification 286.2 kB
  • After compression 232.5 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 53.8 kB or 19% of the original size.

CSS Optimization

-43%

Potential reduce by 54.2 kB

  • Original 127.3 kB
  • After minification 127.3 kB
  • After compression 73.1 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. Oo.com.tw needs all CSS files to be minified and compressed as it can save up to 54.2 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (26%)

Requests Now

74

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

oo.com.tw

oo.com.tw

573 ms

oo.com.tw

oo.com.tw

1211 ms

init.js

init.js

145 ms

bundle.css

bundle.css

1597 ms

bundle.min.js

bundle.min.js

1197 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

861 ms

js

js

56 ms

js

js

89 ms

sdk.js

sdk.js

14 ms

bundle_footer.min.js

bundle_footer.min.js

1073 ms

counter.js

counter.js

37 ms

WebResource.axd

WebResource.axd

833 ms

bundle.js

bundle.js

13 ms

b2.webp

b2.webp

602 ms

b1.webp

b1.webp

287 ms

b3.webp

b3.webp

663 ms

cus_pic.webp

cus_pic.webp

463 ms

templatesimg.webp

templatesimg.webp

461 ms

ezcs.webp

ezcs.webp

462 ms

DisplayWan.ashx

DisplayWan.ashx

788 ms

DisplayWan.ashx

DisplayWan.ashx

799 ms

DisplayWan.ashx

DisplayWan.ashx

990 ms

DisplayWan.ashx

DisplayWan.ashx

886 ms

DisplayWan.ashx

DisplayWan.ashx

1175 ms

DisplayWan.ashx

DisplayWan.ashx

992 ms

DisplayWan.ashx

DisplayWan.ashx

1115 ms

DisplayWan.ashx

DisplayWan.ashx

1149 ms

DisplayWan.ashx

DisplayWan.ashx

1168 ms

DisplayWan.ashx

DisplayWan.ashx

1303 ms

DisplayWan.ashx

DisplayWan.ashx

1311 ms

DisplayWan.ashx

DisplayWan.ashx

1397 ms

DisplayWan.ashx

DisplayWan.ashx

1454 ms

DisplayWan.ashx

DisplayWan.ashx

1492 ms

DisplayWan.ashx

DisplayWan.ashx

1501 ms

DisplayWan.ashx

DisplayWan.ashx

1557 ms

faq.webp

faq.webp

1522 ms

DisplayWan.ashx

DisplayWan.ashx

1631 ms

DisplayWan.ashx

DisplayWan.ashx

1752 ms

DisplayWan.ashx

DisplayWan.ashx

1763 ms

noimg.jpg

noimg.jpg

2627 ms

logo2.webp

logo2.webp

1684 ms

hover.png

hover.png

1722 ms

phone.png

phone.png

1779 ms

js

js

55 ms

analytics.js

analytics.js

52 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1833 ms

programbg.png

programbg.png

1833 ms

programbg2.png

programbg2.png

1854 ms

titlebg.png

titlebg.png

1855 ms

program.svg

program.svg

1902 ms

icon_sec_01.png

icon_sec_01.png

2903 ms

collect

collect

96 ms

arrow.svg

arrow.svg

1840 ms

sdk.js

sdk.js

88 ms

sdk.js

sdk.js

87 ms

fa-solid-900.woff

fa-solid-900.woff

2767 ms

fa-regular-400.woff

fa-regular-400.woff

1710 ms

55 ms

t.php

t.php

99 ms

slick.woff

slick.woff

1701 ms

cus_bg.webp

cus_bg.webp

1716 ms

triangle_li.png

triangle_li.png

1709 ms

trianglebg.png

trianglebg.png

1610 ms

strength.svg

strength.svg

1712 ms

triangle.png

triangle.png

1694 ms

titlebg2.png

titlebg2.png

1595 ms

plus.svg

plus.svg

1709 ms

tag.svg

tag.svg

1666 ms

round.svg

round.svg

1625 ms

icon_news.png

icon_news.png

1863 ms

links.svg

links.svg

1848 ms

faq2.png

faq2.png

1723 ms

smizeicon3.png

smizeicon3.png

1720 ms

contactbox.svg

contactbox.svg

1825 ms

faqbg_tri.png

faqbg_tri.png

1758 ms

faqbg.png

faqbg.png

1723 ms

top.svg

top.svg

1739 ms

contacticon.svg

contacticon.svg

1716 ms

social_white.svg

social_white.svg

1841 ms

gallery_btn.png

gallery_btn.png

1772 ms

ajax-loader.gif

ajax-loader.gif

1701 ms

Accessibility Review

oo.com.tw accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

oo.com.tw best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

oo.com.tw SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

oo.com.tw

Open Graph data is detected on the main page of Oo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: