Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

myonecard.co.nz

Grab your Countdown Onecard in-store | Now partnered with AA Smartfuel

Page Load Speed

11.3 sec in total

First Response

659 ms

Resources Loaded

10.5 sec

Page Rendered

154 ms

myonecard.co.nz screenshot

About Website

Welcome to myonecard.co.nz homepage info - get ready to check My Onecard best content right away, or after learning these important things about myonecard.co.nz

Grab your Countdown Onecard in-store and start swiping at the checkout to access exclusive Onecard Club Price on loads of every day products. You can also swipe your Onecard at AA Smartfuel partners B...

Visit myonecard.co.nz

Key Findings

We analyzed Myonecard.co.nz page load time and found that the first response time was 659 ms and then it took 10.6 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

myonecard.co.nz performance score

0

Network Requests Diagram

myonecard.co.nz

659 ms

www.myonecard.co.nz

2196 ms

onecard

2347 ms

jquery.fancybox-1.2.6.min.css

408 ms

sIFR-screen.min.css

427 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Myonecard.co.nz, 89% (112 requests) were made to Countdown.co.nz and 6% (8 requests) were made to Ct.eid.co.nz. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Countdown.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 928.7 kB (68%)

Content Size

1.4 MB

After Optimization

442.3 kB

In fact, the total size of Myonecard.co.nz main page is 1.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. 40% of websites need less resources to load. Javascripts take 590.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 48.2 kB

  • Original 56.7 kB
  • After minification 52.7 kB
  • After compression 8.5 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 48.2 kB or 85% of the original size.

Image Optimization

-54%

Potential reduce by 279.1 kB

  • Original 513.7 kB
  • After minification 234.7 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. Obviously, My Onecard needs image optimization as it can save up to 279.1 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 434.0 kB

  • Original 590.2 kB
  • After minification 518.5 kB
  • After compression 156.1 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 434.0 kB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 167.5 kB

  • Original 210.4 kB
  • After minification 210.2 kB
  • After compression 43.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. Myonecard.co.nz needs all CSS files to be minified and compressed as it can save up to 167.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (52%)

Requests Now

113

After Optimization

54

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

SEO Factors

myonecard.co.nz SEO score

0

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 Myonecard.co.nz 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 Myonecard.co.nz 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 description is not detected on the main page of My Onecard. 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: