Tools & Wizards About Us
axess.co.nz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

axess.co.nz

Axess Finance | Property | Business | Personal | Loans

Page Load Speed

7.7 sec in total

First Response

469 ms

Resources Loaded

7 sec

Page Rendered

290 ms

axess.co.nz screenshot

About Website

Click here to check amazing Axess content. Otherwise, check out these important facts you probably never knew about axess.co.nz

New Zealand Home Loan Specialists - Loans for Vehicle, Personal, Property and Business. Based in Christchurch we specialise in fast turn around loans using our extensive network of over 100 lenders. C...

Visit axess.co.nz

Key Findings

We analyzed Axess.co.nz page load time and found that the first response time was 469 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

axess.co.nz performance score

0

Network Requests Diagram

axess.co.nz

469 ms

axess.co.nz

1699 ms

bootstrap.css

2141 ms

css

30 ms

css

39 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 75% of them (41 requests) were addressed to the original Axess.co.nz, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Secure.trust-provider.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Axess.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (54%)

Content Size

2.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Axess.co.nz main page is 2.6 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 50.5 kB

  • Original 58.2 kB
  • After minification 39.2 kB
  • After compression 7.7 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 19.0 kB, which is 33% 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 50.5 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

  • Original 894.6 kB
  • After minification 891.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. Axess images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 846.8 kB

  • Original 1.1 MB
  • After minification 759.9 kB
  • After compression 219.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 846.8 kB or 79% of the original size.

CSS Optimization

-88%

Potential reduce by 491.0 kB

  • Original 558.3 kB
  • After minification 418.8 kB
  • After compression 67.3 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. Axess.co.nz needs all CSS files to be minified and compressed as it can save up to 491.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (60%)

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

axess.co.nz

axess.co.nz

469 ms

axess.co.nz

axess.co.nz

1699 ms

bootstrap.css

bootstrap.css

2141 ms

css

css

30 ms

css

css

39 ms

font-awesome.css

font-awesome.css

1525 ms

entypo.css

entypo.css

1405 ms

animations.css

animations.css

1787 ms

superfish4.css

superfish4.css

1170 ms

settings.css

settings.css

1407 ms

prettyPhoto.css

prettyPhoto.css

1611 ms

style4.css

style4.css

2252 ms

blue.css

blue.css

1634 ms

axessblue4.css

axessblue4.css

1732 ms

theme-responsive4.css

theme-responsive4.css

1834 ms

style.css

style.css

1852 ms

jquery.min.js

jquery.min.js

2984 ms

settings.css

settings.css

2217 ms

getgeotrustsslseal

getgeotrustsslseal

10 ms

jquery-ui.js

jquery-ui.js

2766 ms

bootstrap.js

bootstrap.js

1681 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

1942 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2024 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

1848 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1903 ms

fappear.js

fappear.js

2061 ms

jflickrfeed.js

jflickrfeed.js

2123 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

2150 ms

wow.js

wow.js

2239 ms

custom.js

custom.js

2279 ms

analytics.js

analytics.js

146 ms

slider1a.jpg

slider1a.jpg

1242 ms

slider2a.jpg

slider2a.jpg

2267 ms

slider4a.jpg

slider4a.jpg

2057 ms

slider3a.jpg

slider3a.jpg

2301 ms

pdf.png

pdf.png

1242 ms

axessmain.svg

axessmain.svg

334 ms

spriteipadP.svg

spriteipadP.svg

603 ms

timer.png

timer.png

362 ms

collect

collect

30 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

405 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

179 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

180 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

249 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

321 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

400 ms

flaticon.woff

flaticon.woff

428 ms

trustlogo.js

trustlogo.js

252 ms

positivessl_trust_seal_md_167x42.png

positivessl_trust_seal_md_167x42.png

426 ms

seal_bg.gif

seal_bg.gif

115 ms

warranty_level.gif

warranty_level.gif

418 ms

loader.gif

loader.gif

214 ms

bullet.png

bullet.png

235 ms

large_left.png

large_left.png

227 ms

large_right.png

large_right.png

227 ms

SEO Factors

axess.co.nz SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Axess.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Axess.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

axess.co.nz

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