Tools & Wizards About Us
ivideo.com.tw screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ivideo.com.tw

獨家iVideo近150國上網Wifi機!4G高速吃到飽-出國旅遊上網Wifi機、台灣上網Wifi機、挑戰全台最低價

Page Load Speed

7.2 sec in total

First Response

1.3 sec

Resources Loaded

4.4 sec

Page Rendered

1.5 sec

ivideo.com.tw screenshot

About Website

Click here to check amazing Ivideo content for Taiwan. Otherwise, check out these important facts you probably never knew about ivideo.com.tw

iVideo出國旅遊上網Wifi機、海外上網Wifi機、台灣上網Wifi機，4G高速吃到飽不降速Wifi機，機場、超商取件，可接緊急單!

Visit ivideo.com.tw

Key Findings

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

Performance Metrics

ivideo.com.tw performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

ivideo.com.tw

1280 ms

ivideo.css

820 ms

ddmenu.css

408 ms

clickclear.js

409 ms

jquery-1.6.2.min.js

1433 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 81% of them (52 requests) were addressed to the original Ivideo.com.tw, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ivideo.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.7 kB (37%)

Content Size

573.2 kB

After Optimization

362.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 38.0 kB

  • Original 48.8 kB
  • After minification 47.7 kB
  • After compression 10.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.0 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 20.3 kB

  • Original 279.9 kB
  • After minification 259.6 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. Ivideo images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 132.6 kB

  • Original 219.8 kB
  • After minification 213.7 kB
  • After compression 87.3 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 132.6 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 19.8 kB

  • Original 24.8 kB
  • After minification 16.7 kB
  • After compression 5.0 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. Ivideo.com.tw needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ivideo.com.tw

ivideo.com.tw

1280 ms

ivideo.css

ivideo.css

820 ms

ddmenu.css

ddmenu.css

408 ms

clickclear.js

clickclear.js

409 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

1433 ms

ddsmoothmenu.js

ddsmoothmenu.js

828 ms

ddsmoothmenu-v.css

ddsmoothmenu-v.css

432 ms

webstat.js

webstat.js

205 ms

ad_show2.php

ad_show2.php

219 ms

bnr_okinawa.jpg

bnr_okinawa.jpg

909 ms

hh226x1.gif

hh226x1.gif

205 ms

hh226x80.gif

hh226x80.gif

411 ms

house.gif

house.gif

207 ms

BT-bg.gif

BT-bg.gif

384 ms

basket_s.gif

basket_s.gif

408 ms

2016_announce.jpg

2016_announce.jpg

1196 ms

shipping_free_banner_230X92.gif

shipping_free_banner_230X92.gif

638 ms

tpsbanner.gif

tpsbanner.gif

904 ms

cathay8.gif

cathay8.gif

614 ms

banner_230x140.gif

banner_230x140.gif

1190 ms

skl_banner.jpg

skl_banner.jpg

1194 ms

48717_s.jpg

48717_s.jpg

898 ms

48678_s.jpg

48678_s.jpg

1181 ms

48919_s.jpg

48919_s.jpg

1182 ms

48961_s.jpg

48961_s.jpg

1188 ms

48718_s.jpg

48718_s.jpg

1352 ms

48545_s.jpg

48545_s.jpg

1354 ms

48584_s.jpg

48584_s.jpg

1372 ms

48619_s.jpg

48619_s.jpg

1372 ms

48450_s.jpg

48450_s.jpg

1372 ms

48951_s.jpg

48951_s.jpg

1373 ms

47723_s.png

47723_s.png

1531 ms

47699_s.png

47699_s.png

1532 ms

47685_s.jpg

47685_s.jpg

1558 ms

48679_s.jpg

48679_s.jpg

1557 ms

48414_s.png

48414_s.png

1558 ms

46691_s.jpg

46691_s.jpg

1555 ms

46653_s.jpg

46653_s.jpg

1803 ms

46923_s.jpg

46923_s.jpg

1891 ms

48740_s.jpg

48740_s.jpg

1890 ms

Android.jpg

Android.jpg

1890 ms

iOS.jpg

iOS.jpg

1889 ms

mail.gif

mail.gif

1866 ms

Global_Trust_Seal.gif

Global_Trust_Seal.gif

1763 ms

TWtoJP20160201_728x90_2.jpg

TWtoJP20160201_728x90_2.jpg

2042 ms

scroller.php

scroller.php

1226 ms

rightlistbg2.gif

rightlistbg2.gif

1154 ms

trans-shadow.png

trans-shadow.png

1149 ms

all.js

all.js

338 ms

ga.js

ga.js

153 ms

atrk.js

atrk.js

329 ms

right.gif

right.gif

692 ms

__utm.gif

__utm.gif

94 ms

atrk.gif

atrk.gif

279 ms

210 ms

test.png

test.png

43 ms

xd_arbiter.php

xd_arbiter.php

237 ms

xd_arbiter.php

xd_arbiter.php

393 ms

content.css

content.css

216 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

418 ms

featuredcontentglider.css

featuredcontentglider.css

218 ms

featuredcontentglider.js

featuredcontentglider.js

239 ms

__utm.gif

__utm.gif

198 ms

ping

ping

207 ms

Accessibility Review

ivideo.com.tw accessibility score

68

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

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

High

ARIA toggle fields do not have accessible names

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

ivideo.com.tw best practices score

75

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

SEO Factors

ivideo.com.tw SEO score

69

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ivideo.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Ivideo.com.tw main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ivideo.com.tw

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