Tools & Wizards About Us
secure.amp.com.au screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 0

    Best Practices

  • 77

    SEO

    Google-friendlier than
    36% of websites

secure.amp.com.au

Login to My AMP - AMP

Page Load Speed

8.5 sec in total

First Response

1.1 sec

Resources Loaded

7.2 sec

Page Rendered

235 ms

secure.amp.com.au screenshot

About Website

Click here to check amazing Secure AMP content for Australia. Otherwise, check out these important facts you probably never knew about secure.amp.com.au

My Portfolio & Banknet have combined to create My AMP, allowing you to access your banking, investment, insurance and super accounts in one place.

Visit secure.amp.com.au

Key Findings

We analyzed Secure.amp.com.au page load time and found that the first response time was 1.1 sec and then it took 7.4 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

secure.amp.com.au performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

secure.amp.com.au

1092 ms

928 ms

dtagent620_n_1239.js

649 ms

fonts.css

533 ms

css

86 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 18% of them (7 requests) were addressed to the original Secure.amp.com.au, 48% (19 requests) were made to Amp.com.au and 13% (5 requests) were made to . The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Amp.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (71%)

Content Size

2.4 MB

After Optimization

694.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Secure.amp.com.au main page is 2.4 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. 35% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 73.0 kB

  • Original 82.1 kB
  • After minification 43.9 kB
  • After compression 9.1 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 38.2 kB, which is 47% 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 73.0 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 9.3 kB

  • Original 253.7 kB
  • After minification 244.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. Secure AMP images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 720.1 kB

  • Original 902.6 kB
  • After minification 629.9 kB
  • After compression 182.5 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 720.1 kB or 80% of the original size.

CSS Optimization

-78%

Potential reduce by 905.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 258.1 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. Secure.amp.com.au needs all CSS files to be minified and compressed as it can save up to 905.5 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

28

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

secure.amp.com.au

secure.amp.com.au

1092 ms

928 ms

dtagent620_n_1239.js

dtagent620_n_1239.js

649 ms

fonts.css

fonts.css

533 ms

css

css

86 ms

satelliteLib-d5f159321ff51c9afec4e7a8298ad0e14f28e573.js

satelliteLib-d5f159321ff51c9afec4e7a8298ad0e14f28e573.js

287 ms

icons-libs.min.css

icons-libs.min.css

1241 ms

header-libs.min.css

header-libs.min.css

1761 ms

header-1-libs.min.css

header-1-libs.min.css

1519 ms

header-2-libs.min.css

header-2-libs.min.css

1265 ms

jquery.min.js

jquery.min.js

1753 ms

utils.min.js

utils.min.js

1268 ms

granite.min.js

granite.min.js

1480 ms

header-libs.min.js

header-libs.min.js

1507 ms

aem_common.css

aem_common.css

663 ms

login.css

login.css

1133 ms

component-libs.min.css

component-libs.min.css

1508 ms

component-libs.min.js

component-libs.min.js

1720 ms

EFFED685B8BB01EC4.css

EFFED685B8BB01EC4.css

2192 ms

jquery.min.js

jquery.min.js

25 ms

aem-common.js

aem-common.js

218 ms

491 ms

logo-amp.png

logo-amp.png

314 ms

logo-amp-dark.png

logo-amp-dark.png

313 ms

play-btn.png

play-btn.png

312 ms

VID-welcome-to-my-amp.png

VID-welcome-to-my-amp.png

1671 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

201 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

201 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

202 ms

xtreme.woff

xtreme.woff

478 ms

zHk8Ov5fiF7biQs4=

zHk8Ov5fiF7biQs4=

134 ms

lC2g==

lC2g==

127 ms

rnpSvlZzY+KRM75IeVjM+ved5j6eH30v1C1SgQrY=

rnpSvlZzY+KRM75IeVjM+ved5j6eH30v1C1SgQrY=

125 ms

rnpSvlZzY+KRM75IeVjM+ved5j6eH30v1C0RDQrI=

rnpSvlZzY+KRM75IeVjM+ved5j6eH30v1C0RDQrI=

123 ms

ved7j8eH3UvwC15xC1g==

ved7j8eH3UvwC15xC1g==

122 ms

s-code-contents-ed47b6657c481499aa81e60509efc7efb1e275ed.js

s-code-contents-ed47b6657c481499aa81e60509efc7efb1e275ed.js

187 ms

plugins.js

plugins.js

1213 ms

script.js

script.js

730 ms

s71983313506934

s71983313506934

8 ms

plugins.js

plugins.js

733 ms

Accessibility Review

secure.amp.com.au accessibility score

93

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

Links do not have a discernible name

SEO Factors

secure.amp.com.au SEO score

77

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

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Secure.amp.com.au 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), while the claimed language is English. Our system also found out that Secure.amp.com.au 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

secure.amp.com.au

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