Tools & Wizards About Us
onecard.co.nz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onecard.co.nz

CardSmart Fuel Cards | One Fuel Card, NZ Wide Acceptance

Page Load Speed

7.2 sec in total

First Response

602 ms

Resources Loaded

6.3 sec

Page Rendered

290 ms

onecard.co.nz screenshot

About Website

Visit onecard.co.nz now to see the best up-to-date One Card content and also check out these interesting facts you probably never knew about onecard.co.nz

The Only Fuel Card Accepted at all Major Fuel Stations throughout New Zealand. Fuel Cards for Business Fleets with Discounts Available.

Visit onecard.co.nz

Key Findings

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

onecard.co.nz performance score

0

Network Requests Diagram

onecard.co.nz

602 ms

www.cardsmart.co.nz

1260 ms

wp-emoji-release.min.js

608 ms

layerslider.css

608 ms

css

26 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Onecard.co.nz, 65% (39 requests) were made to Cardsmart.co.nz and 22% (13 requests) were made to Apply.cardsmart.co.nz. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Cardsmart.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (63%)

Content Size

2.4 MB

After Optimization

892.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onecard.co.nz 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 121.3 kB

  • Original 147.8 kB
  • After minification 145.9 kB
  • After compression 26.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 121.3 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 6.8 kB

  • Original 445.5 kB
  • After minification 438.8 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. One Card images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 862.5 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 345.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 862.5 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 543.4 kB

  • Original 624.6 kB
  • After minification 523.3 kB
  • After compression 81.2 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. Onecard.co.nz needs all CSS files to be minified and compressed as it can save up to 543.4 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onecard.co.nz

onecard.co.nz

602 ms

www.cardsmart.co.nz

www.cardsmart.co.nz

1260 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

608 ms

layerslider.css

layerslider.css

608 ms

css

css

26 ms

styles.css

styles.css

417 ms

settings.css

settings.css

790 ms

style.css

style.css

1277 ms

font-awesome.css

font-awesome.css

639 ms

animations.css

animations.css

608 ms

media.css

media.css

632 ms

ipad.css

ipad.css

836 ms

greensock.js

greensock.js

1025 ms

jquery.js

jquery.js

1278 ms

jquery-migrate.min.js

jquery-migrate.min.js

854 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

1258 ms

layerslider.transitions.js

layerslider.transitions.js

1039 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1469 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1450 ms

jquery.form.min.js

jquery.form.min.js

1053 ms

scripts.js

scripts.js

926 ms

comment-reply.min.js

comment-reply.min.js

1056 ms

modernizr-min.js

modernizr-min.js

1125 ms

jquery.carouFredSel-6.2.1-min.js

jquery.carouFredSel-6.2.1-min.js

1126 ms

jquery.cycle.js

jquery.cycle.js

1467 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1286 ms

jquery.fitvids-min.js

jquery.fitvids-min.js

1277 ms

main.js

main.js

1916 ms

wp-embed.min.js

wp-embed.min.js

1279 ms

analytics.js

analytics.js

16 ms

ls_bkgd_dark.jpg

ls_bkgd_dark.jpg

1424 ms

cardsmart_logo.png

cardsmart_logo.png

338 ms

transparent.png

transparent.png

354 ms

Black_CardSmart-caps.png

Black_CardSmart-caps.png

1406 ms

oil_co_lockup.png

oil_co_lockup.png

1116 ms

slider-oilco-non-oil1.png

slider-oilco-non-oil1.png

1126 ms

fuel-card-business.png

fuel-card-business.png

1527 ms

apply.cardsmart.co.nz

apply.cardsmart.co.nz

1232 ms

collect

collect

87 ms

bkgd_bw2.jpg

bkgd_bw2.jpg

2352 ms

icomoon.woff

icomoon.woff

1258 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1568 ms

coloredbg.png

coloredbg.png

469 ms

bullet.png

bullet.png

580 ms

cardlink-application.aspx

cardlink-application.aspx

449 ms

analytics.js

analytics.js

30 ms

bat.js

bat.js

337 ms

CardlinkApplicationStyleSheet.css

CardlinkApplicationStyleSheet.css

217 ms

WebResource.axd

WebResource.axd

414 ms

AdapterUtils.js

AdapterUtils.js

596 ms

MenuAdapter.js

MenuAdapter.js

593 ms

WebResource.axd

WebResource.axd

973 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1008 ms

jquery.maskedinput-1.2.2.js

jquery.maskedinput-1.2.2.js

608 ms

collect

collect

3 ms

CardSmart_logo_white.png

CardSmart_logo_white.png

566 ms

icon_ssl_white.png

icon_ssl_white.png

748 ms

apply.cardsmart.co.nz

apply.cardsmart.co.nz

196 ms

cardlink-application.aspx

cardlink-application.aspx

250 ms

collect

collect

10 ms

SEO Factors

onecard.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 Onecard.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 Onecard.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

onecard.co.nz

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