Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

my.eway.io

Online Payments Platform | Payment Gateway | Eway Australia

Page Load Speed

6.9 sec in total

First Response

307 ms

Resources Loaded

5.5 sec

Page Rendered

1.1 sec

my.eway.io screenshot

About Website

Click here to check amazing My Eway content for Australia. Otherwise, check out these important facts you probably never knew about my.eway.io

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 my.eway.io

Key Findings

We analyzed My.eway.io page load time and found that the first response time was 307 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

my.eway.io performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value31.1 s

0/100

10%

Network Requests Diagram

my.eway.io

307 ms

my.eway.io

452 ms

www.eway.com.au

366 ms

style.css

734 ms

autoptimize_single_328afdee919ab88a440ae96ce0258a86.css

1308 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original My.eway.io, 87% (74 requests) were made to Eway.com.au and 4% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Eway.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (46%)

Content Size

2.7 MB

After Optimization

1.4 MB

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

HTML Optimization

-80%

Potential reduce by 193.1 kB

  • Original 241.0 kB
  • After minification 241.0 kB
  • After compression 47.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. 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 193.1 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 120.4 kB

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

JavaScript Optimization

-66%

Potential reduce by 347.1 kB

  • Original 528.0 kB
  • After minification 528.0 kB
  • After compression 180.9 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 347.1 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 560.0 kB

  • Original 643.8 kB
  • After minification 643.6 kB
  • After compression 83.8 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. My.eway.io needs all CSS files to be minified and compressed as it can save up to 560.0 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

80

After Optimization

54

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

my.eway.io accessibility score

87

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-hidden="true"] elements contain focusable descendents

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

my.eway.io 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

my.eway.io SEO score

86

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

Links do not have descriptive text

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 My.eway.io 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 My.eway.io 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

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