Tools & Wizards About Us
global-ebanking.com.tw screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

global-ebanking.com.tw

GEB

Page Load Speed

17.5 sec in total

First Response

1.2 sec

Resources Loaded

16.1 sec

Page Rendered

229 ms

global-ebanking.com.tw screenshot

About Website

Visit global-ebanking.com.tw now to see the best up-to-date Global Ebanking content and also check out these interesting facts you probably never knew about global-ebanking.com.tw

Visit global-ebanking.com.tw

Key Findings

We analyzed Global-ebanking.com.tw page load time and found that the first response time was 1.2 sec and then it took 16.4 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

global-ebanking.com.tw performance score

0

Network Requests Diagram

ebcontent.jsp

1170 ms

common.js

1923 ms

login.faces

317 ms

base_en_US@1450349588000.css

318 ms

dojo.js

2488 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that all of those requests were addressed to Global-ebanking.com.tw and no external sources were called. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Global-ebanking.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.3 kB (74%)

Content Size

686.3 kB

After Optimization

180.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Global-ebanking.com.tw main page is 686.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. Javascripts take 570.8 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 3.9 kB

  • Original 6.3 kB
  • After minification 6.3 kB
  • After compression 2.4 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 3.9 kB or 62% of the original size.

Image Optimization

-0%

Potential reduce by 23 B

  • Original 40.5 kB
  • After minification 40.4 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. Global Ebanking images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 444.2 kB

  • Original 570.8 kB
  • After minification 458.8 kB
  • After compression 126.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 444.2 kB or 78% of the original size.

CSS Optimization

-85%

Potential reduce by 58.1 kB

  • Original 68.6 kB
  • After minification 56.1 kB
  • After compression 10.5 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. Global-ebanking.com.tw needs all CSS files to be minified and compressed as it can save up to 58.1 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ebcontent.jsp

ebcontent.jsp

1170 ms

common.js

common.js

1923 ms

login.faces

login.faces

317 ms

base_en_US@1450349588000.css

base_en_US@1450349588000.css

318 ms

dojo.js

dojo.js

2488 ms

common@1435235113000.js

common@1435235113000.js

1961 ms

GTO011ApplyStep1.js

GTO011ApplyStep1.js

1652 ms

menu@1393332134000.js

menu@1393332134000.js

1608 ms

loading@1300016504000.js

loading@1300016504000.js

1678 ms

login@1438857100000.js

login@1438857100000.js

649 ms

login_btn3.gif

login_btn3.gif

971 ms

login_btn4.gif

login_btn4.gif

1353 ms

login_btn5.gif

login_btn5.gif

1673 ms

login_btn6.gif

login_btn6.gif

1943 ms

ban3.gif

ban3.gif

2076 ms

loadingAnimation@1300016502000.gif

loadingAnimation@1300016502000.gif

2008 ms

slash_bg@1300016504000.gif

slash_bg@1300016504000.gif

1219 ms

hd_bg1@1300016504000.gif

hd_bg1@1300016504000.gif

1216 ms

hd_bg2@1300016504000.jpg

hd_bg2@1300016504000.jpg

1228 ms

login_nav1@1300016504000.gif

login_nav1@1300016504000.gif

1213 ms

login_nav2@1300016504000.gif

login_nav2@1300016504000.gif

1213 ms

login_nav3@1300016504000.gif

login_nav3@1300016504000.gif

1217 ms

tabs_line1@1300016504000.gif

tabs_line1@1300016504000.gif

1219 ms

tabs_current_rt@1300016504000.gif

tabs_current_rt@1300016504000.gif

1220 ms

tabs_current_lt@1300016504000.gif

tabs_current_lt@1300016504000.gif

1223 ms

dt_lt@1300016504000.gif

dt_lt@1300016504000.gif

1220 ms

dt_rt1@1300016504000.gif

dt_rt1@1300016504000.gif

1223 ms

wel_1@1300016504000.gif

wel_1@1300016504000.gif

1230 ms

wel_2@1300016504000.gif

wel_2@1300016504000.gif

1226 ms

tit.gif

tit.gif

1414 ms

wel_3@1300016504000.gif

wel_3@1300016504000.gif

1231 ms

wel_4@1300016504000.gif

wel_4@1300016504000.gif

1229 ms

inner_1@1300016504000.gif

inner_1@1300016504000.gif

1232 ms

inner_2@1300016504000.gif

inner_2@1300016504000.gif

1235 ms

inner_3@1300016502000.gif

inner_3@1300016502000.gif

1239 ms

inner_4@1300016504000.gif

inner_4@1300016504000.gif

1235 ms

btn1@1300016504000.gif

btn1@1300016504000.gif

1238 ms

inner_6@1300016504000.gif

inner_6@1300016504000.gif

1358 ms

inner_7@1300016504000.gif

inner_7@1300016504000.gif

1751 ms

inner_8@1300016504000.gif

inner_8@1300016504000.gif

1584 ms

inner_9@1300016504000.gif

inner_9@1300016504000.gif

1580 ms

post1@1300016504000.gif

post1@1300016504000.gif

1588 ms

post2@1300016504000.gif

post2@1300016504000.gif

1660 ms

post_tit@1300016504000.gif

post_tit@1300016504000.gif

1702 ms

post3@1300016504000.gif

post3@1300016504000.gif

1941 ms

post4@1300016504000.gif

post4@1300016504000.gif

1911 ms

square@1300016502000.gif

square@1300016502000.gif

1910 ms

post6@1300016504000.gif

post6@1300016504000.gif

2107 ms

post7@1300016504000.gif

post7@1300016504000.gif

2193 ms

post8@1300016504000.gif

post8@1300016504000.gif

2231 ms

more@1300016504000.gif

more@1300016504000.gif

3682 ms

post9@1300016502000.gif

post9@1300016502000.gif

2377 ms

OFGE101_2C.faces

OFGE101_2C.faces

1749 ms

wel_6@1300016504000.gif

wel_6@1300016504000.gif

2504 ms

wel_7@1300016504000.gif

wel_7@1300016504000.gif

2498 ms

wel_8@1300016504000.gif

wel_8@1300016504000.gif

2500 ms

wel_9@1300016504000.gif

wel_9@1300016504000.gif

2500 ms

safe1@1300016504000.gif

safe1@1300016504000.gif

2521 ms

safe2@1300016504000.gif

safe2@1300016504000.gif

2797 ms

safe_tit@1300016504000.gif

safe_tit@1300016504000.gif

2813 ms

safe3@1300016504000.gif

safe3@1300016504000.gif

2789 ms

safe4@1300016504000.gif

safe4@1300016504000.gif

2826 ms

arrow@1300016504000.gif

arrow@1300016504000.gif

2802 ms

safe6@1300016504000.gif

safe6@1300016504000.gif

2848 ms

safe7@1300016504000.gif

safe7@1300016504000.gif

3399 ms

safe8@1300016504000.gif

safe8@1300016504000.gif

3394 ms

safe9@1300016504000.gif

safe9@1300016504000.gif

3404 ms

ban_ft@1300016504000.gif

ban_ft@1300016504000.gif

3398 ms

ban1@1300016504000.gif

ban1@1300016504000.gif

3619 ms

ban4@1372157222000.gif

ban4@1372157222000.gif

3403 ms

login_btn6@1406631142000.gif

login_btn6@1406631142000.gif

3990 ms

CustermerService@1300016504000.gif

CustermerService@1300016504000.gif

3755 ms

footer@1300016504000.gif

footer@1300016504000.gif

3711 ms

base.css

base.css

2284 ms

prototype.js

prototype.js

3943 ms

screenmask.js

screenmask.js

2409 ms

base.js

base.js

2455 ms

osib.js

osib.js

2472 ms

common.js

common.js

3274 ms

Bulletin_bgl.gif

Bulletin_bgl.gif

314 ms

slash_bg.gif

slash_bg.gif

308 ms

post1.gif

post1.gif

293 ms

post2.gif

post2.gif

317 ms

Bulletin_tit1.gif

Bulletin_tit1.gif

308 ms

post3.gif

post3.gif

300 ms

post4.gif

post4.gif

589 ms

post6.gif

post6.gif

590 ms

post7.gif

post7.gif

577 ms

post8.gif

post8.gif

587 ms

more.gif

more.gif

609 ms

post9.gif

post9.gif

647 ms

print_en_US@1418294216000.css

print_en_US@1418294216000.css

349 ms

Accessibility Review

global-ebanking.com.tw accessibility score

68

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

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

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

global-ebanking.com.tw best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Uses deprecated APIs

SEO Factors

global-ebanking.com.tw SEO score

55

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Global-ebanking.com.tw can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Global-ebanking.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

global-ebanking.com.tw

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