Tools & Wizards About Us
eway.asia screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

eway.asia

All-in-one Online Payments Platform | Eway Australia

Page Load Speed

4.4 sec in total

First Response

835 ms

Resources Loaded

3.4 sec

Page Rendered

133 ms

eway.asia screenshot

About Website

Click here to check amazing Eway content. Otherwise, check out these important facts you probably never knew about eway.asia

Eway's secure and reliable online payment gateway makes it easy for you to accept credit card payments from anyone, anywhere, from any device.

Visit eway.asia

Key Findings

We analyzed Eway.asia page load time and found that the first response time was 835 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

eway.asia performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

eway.io

835 ms

style.css

207 ms

style.css

412 ms

genericons.css

803 ms

font-awesome.min.css

604 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Eway.asia, 9% (4 requests) were made to App-sn03.marketo.com and 7% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Eway.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.6 kB (9%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eway.asia main page is 1.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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 39.8 kB

  • Original 52.6 kB
  • After minification 45.3 kB
  • After compression 12.8 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 7.3 kB, which is 14% 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 39.8 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 104.4 kB

  • Original 1.3 MB
  • After minification 1.2 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. Eway images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.0 kB

  • Original 181.4 kB
  • After minification 181.4 kB
  • After compression 177.4 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

-3%

Potential reduce by 3.4 kB

  • Original 100.4 kB
  • After minification 100.2 kB
  • After compression 97.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. Eway.asia has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (67%)

Requests Now

45

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eway.io

eway.io

835 ms

style.css

style.css

207 ms

style.css

style.css

412 ms

genericons.css

genericons.css

803 ms

font-awesome.min.css

font-awesome.min.css

604 ms

all.min.css

all.min.css

607 ms

app.min.css

app.min.css

1011 ms

addtoany.min.css

addtoany.min.css

613 ms

page.js

page.js

51 ms

jquery.min.js

jquery.min.js

820 ms

jquery-migrate.min.js

jquery-migrate.min.js

805 ms

addtoany.min.js

addtoany.min.js

806 ms

70be1b9c88.js

70be1b9c88.js

62 ms

forms2.min.js

forms2.min.js

237 ms

frontend_full.js

frontend_full.js

1001 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

1004 ms

popper.min.js

popper.min.js

48 ms

bootstrap.min.js

bootstrap.min.js

41 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

1006 ms

bodymovin.min.js

bodymovin.min.js

1428 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

64 ms

jquery.visible.min.js

jquery.visible.min.js

1081 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1202 ms

app.min.js

app.min.js

1205 ms

custom-utm.js

custom-utm.js

1207 ms

hoverIntent.min.js

hoverIntent.min.js

1208 ms

maxmegamenu.js

maxmegamenu.js

1229 ms

public.js

public.js

1403 ms

gtm.js

gtm.js

114 ms

Happy-Cart.svg

Happy-Cart.svg

366 ms

home-hero.jpeg

home-hero.jpeg

1369 ms

merchant-on-laptop.jpg

merchant-on-laptop.jpg

771 ms

About_-_About_Eway_-_All_In_One_Payments.jpeg

About_-_About_Eway_-_All_In_One_Payments.jpeg

595 ms

Solutions-Enterprise-Solutions-Header-600x600.jpg

Solutions-Enterprise-Solutions-Header-600x600.jpg

764 ms

Winning-omni-channel-strategy-blog.jpg

Winning-omni-channel-strategy-blog.jpg

1364 ms

accept-online-payments-1-600x600-1-600x600-1-600x600.jpeg

accept-online-payments-1-600x600-1-600x600-1-600x600.jpeg

793 ms

curve-footer-top-yellow-white-bgd.svg

curve-footer-top-yellow-white-bgd.svg

801 ms

getForm

getForm

1427 ms

FilsonSoft-Bold.svg

FilsonSoft-Bold.svg

1062 ms

FilsonSoft-Book.svg

FilsonSoft-Book.svg

1114 ms

FilsonSoft-Medium.svg

FilsonSoft-Medium.svg

1114 ms

FilsonSoft-Regular.svg

FilsonSoft-Regular.svg

1115 ms

sm.25.html

sm.25.html

25 ms

eso.D0Uc7kY6.js

eso.D0Uc7kY6.js

38 ms

forms2.css

forms2.css

24 ms

forms2-theme-simple.css

forms2-theme-simple.css

32 ms

Accessibility Review

eway.asia accessibility score

97

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

Links do not have a discernible name

Best Practices

eway.asia 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eway.asia SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Eway.asia 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 Eway.asia 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

eway.asia

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