Tools & Wizards About Us
ioi.com.tw screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ioi.com.tw

IOI Technology Corporation | PCI Express | SATA | 1394 | USB | Gigabit

Page Load Speed

5.3 sec in total

First Response

604 ms

Resources Loaded

4.5 sec

Page Rendered

138 ms

ioi.com.tw screenshot

About Website

Click here to check amazing IOI content for Russia. Otherwise, check out these important facts you probably never knew about ioi.com.tw

IOI was founded in 1994. Your I/O Solution Provider is IOI's slogan. IOI stands for Input/Output Interfaces. IOI provides high-speed and cost-effective I/O solutions such as the Gigabit to PCIe host c...

Visit ioi.com.tw

Key Findings

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

Performance Metrics

ioi.com.tw performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,720 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.594

11/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

ioi.com.tw

604 ms

ioi.com.tw

1178 ms

stylesheet2008.css

632 ms

setcounter.php

1054 ms

ystat.js

4 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Ioi.com.tw, 9% (5 requests) were made to Toolkit.url.com.tw and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ioi.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.7 kB (50%)

Content Size

212.3 kB

After Optimization

106.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ioi.com.tw main page is 212.3 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. 25% of websites need less resources to load. Images take 94.6 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 79.0 kB

  • Original 84.9 kB
  • After minification 23.0 kB
  • After compression 6.0 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 61.9 kB, which is 73% 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 79.0 kB or 93% of the original size.

Image Optimization

-14%

Potential reduce by 13.4 kB

  • Original 94.6 kB
  • After minification 81.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. Obviously, IOI needs image optimization as it can save up to 13.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 13.3 kB

  • Original 15.6 kB
  • After minification 11.2 kB
  • After compression 2.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. Ioi.com.tw needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ioi.com.tw

ioi.com.tw

604 ms

ioi.com.tw

ioi.com.tw

1178 ms

stylesheet2008.css

stylesheet2008.css

632 ms

setcounter.php

setcounter.php

1054 ms

ystat.js

ystat.js

4 ms

bg3.jpg

bg3.jpg

193 ms

bg_ma3.jpg

bg_ma3.jpg

252 ms

blog.gif

blog.gif

384 ms

rss.gif

rss.gif

503 ms

sitemap.gif

sitemap.gif

576 ms

searchico.gif

searchico.gif

697 ms

index_ad620-200_1.gif

index_ad620-200_1.gif

1222 ms

index_ad620-200_8.gif

index_ad620-200_8.gif

1207 ms

index_ad620-200_2.gif

index_ad620-200_2.gif

1249 ms

index_ad620-200_3.gif

index_ad620-200_3.gif

1234 ms

index_ad620-200_4.gif

index_ad620-200_4.gif

1252 ms

index_ad620-200_5.gif

index_ad620-200_5.gif

1088 ms

index_ad620-200_6.gif

index_ad620-200_6.gif

1533 ms

index_ad620-200_7.gif

index_ad620-200_7.gif

1649 ms

Tab_Img10.gif

Tab_Img10.gif

1413 ms

Tab_Img20.gif

Tab_Img20.gif

1429 ms

Tab_Img30.gif

Tab_Img30.gif

1442 ms

Tab_Img40.gif

Tab_Img40.gif

1445 ms

Tab_Img50.gif

Tab_Img50.gif

1605 ms

Tab_Img60.gif

Tab_Img60.gif

1622 ms

Tab_Img70.gif

Tab_Img70.gif

1635 ms

Tab_Img80.gif

Tab_Img80.gif

1638 ms

site_buttom.gif

site_buttom.gif

1786 ms

pdb_a.jpg

pdb_a.jpg

1879 ms

pdb_b.jpg

pdb_b.jpg

1822 ms

pdb_e.jpg

pdb_e.jpg

1876 ms

pdb_g.jpg

pdb_g.jpg

1842 ms

pdb_h.jpg

pdb_h.jpg

1877 ms

pdb_g2.jpg

pdb_g2.jpg

1986 ms

pdb_d.jpg

pdb_d.jpg

2023 ms

pdb_c.jpg

pdb_c.jpg

2073 ms

pdb_f.jpg

pdb_f.jpg

2076 ms

pdb_i.jpg

pdb_i.jpg

2082 ms

pdb_k.jpg

pdb_k.jpg

2074 ms

pdb_l.jpg

pdb_l.jpg

2226 ms

pdb_j.jpg

pdb_j.jpg

2224 ms

pdb_m.jpg

pdb_m.jpg

2135 ms

pdb_n.jpg

pdb_n.jpg

2077 ms

topbg2.gif

topbg2.gif

1895 ms

Tab_Img11.gif

Tab_Img11.gif

1775 ms

site_buttom-c.gif

site_buttom-c.gif

1882 ms

m-bg.gif

m-bg.gif

1727 ms

7.png

7.png

581 ms

6.png

6.png

583 ms

0.png

0.png

583 ms

2.png

2.png

585 ms

ga.js

ga.js

21 ms

__utm.gif

__utm.gif

13 ms

f-bg.gif

f-bg.gif

1383 ms

Accessibility Review

ioi.com.tw accessibility score

59

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

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

Image elements do not have [alt] attributes

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.

Best Practices

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

ioi.com.tw SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ioi.com.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ioi.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

ioi.com.tw

Open Graph description is not detected on the main page of IOI. 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: