Tools & Wizards About Us
ezymigrate.co.nz screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ezymigrate.co.nz

Ezy Migrate | Client Management Software for NZ Immigration Advisers

Page Load Speed

26.9 sec in total

First Response

1.1 sec

Resources Loaded

25.2 sec

Page Rendered

553 ms

ezymigrate.co.nz screenshot

About Website

Visit ezymigrate.co.nz now to see the best up-to-date Ezy Migrate content for New Zealand and also check out these interesting facts you probably never knew about ezymigrate.co.nz

Ezymigrate can cut the time you spend on client administration by as much as 70%. Start making your business more efficient today - Ezymigrate is the future of Immigration Business in New Zealand. Boo...

Visit ezymigrate.co.nz

Key Findings

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

Performance Metrics

ezymigrate.co.nz performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value26.5 s

0/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

ezymigrate.co.nz

1131 ms

index.html

280 ms

owl.carousel.css

1031 ms

owl.theme.css

1074 ms

flaticon.css

1055 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 83% of them (83 requests) were addressed to the original Ezymigrate.co.nz, 6% (6 requests) were made to Gstatic.com and 5% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (8.4 sec) belongs to the original domain Ezymigrate.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 489.6 kB (12%)

Content Size

4.1 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ezymigrate.co.nz main page is 4.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.4 kB

  • Original 60.1 kB
  • After minification 53.8 kB
  • After compression 11.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 6.3 kB, which is 11% 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 48.4 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 385.8 kB

  • Original 3.6 MB
  • After minification 3.2 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. Obviously, Ezy Migrate needs image optimization as it can save up to 385.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 29.2 kB

  • Original 338.1 kB
  • After minification 338.0 kB
  • After compression 308.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-27%

Potential reduce by 26.1 kB

  • Original 96.3 kB
  • After minification 96.2 kB
  • After compression 70.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. Ezymigrate.co.nz needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 27% of the original size.

Requests Breakdown

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

Requests Now

86

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ezymigrate.co.nz

ezymigrate.co.nz

1131 ms

index.html

index.html

280 ms

owl.carousel.css

owl.carousel.css

1031 ms

owl.theme.css

owl.theme.css

1074 ms

flaticon.css

flaticon.css

1055 ms

font-awesome.min.css

font-awesome.min.css

1043 ms

bootstrap.min.css

bootstrap.min.css

1033 ms

style.css

style.css

1051 ms

jquery.js

jquery.js

2083 ms

api.js

api.js

29 ms

email-decode.min.js

email-decode.min.js

1043 ms

bootstrap.min.js

bootstrap.min.js

2048 ms

smoothscroll.min.js

smoothscroll.min.js

2092 ms

html5lightbox.js

html5lightbox.js

2072 ms

demo.js

demo.js

2097 ms

modernizr.js

modernizr.js

2146 ms

jquery.counterup.min.js

jquery.counterup.min.js

3066 ms

waypoints.min.js

waypoints.min.js

3090 ms

owl.carousel.js

owl.carousel.js

3095 ms

scrollReveal.min.js

scrollReveal.min.js

3111 ms

urip.js

urip.js

3125 ms

common.js

common.js

3157 ms

recaptcha__en.js

recaptcha__en.js

18 ms

trustlogo.js

trustlogo.js

68 ms

loading.gif

loading.gif

1942 ms

logo.png

logo.png

1939 ms

facebook-icon.png

facebook-icon.png

1993 ms

twitter-icon.png

twitter-icon.png

1963 ms

linkedin-icon.png

linkedin-icon.png

1981 ms

features2u.png

features2u.png

2009 ms

iphone.png

iphone.png

2947 ms

iphone2.png

iphone2.png

2966 ms

azure.png

azure.png

2970 ms

xero.jpg

xero.jpg

2995 ms

toi.png

toi.png

2995 ms

massey.png

massey.png

3049 ms

kwd.png

kwd.png

3990 ms

mailchimp.png

mailchimp.png

3981 ms

sendgrid.png

sendgrid.png

3979 ms

icehouse.png

icehouse.png

3997 ms

blog2.jpg

blog2.jpg

4000 ms

blog3.jpg

blog3.jpg

4077 ms

blog4.jpg

blog4.jpg

5004 ms

client1.png

client1.png

4994 ms

timg1.jpg

timg1.jpg

4997 ms

client2.png

client2.png

5029 ms

timg2.jpg

timg2.jpg

5016 ms

client3.png

client3.png

5078 ms

timg3.jpg

timg3.jpg

6009 ms

client4-edit.png

client4-edit.png

6013 ms

timg4.jpg

timg4.jpg

6031 ms

client5.png

client5.png

6069 ms

timg5.jpg

timg5.jpg

6052 ms

client6.png

client6.png

6444 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

6599 ms

FontAwesome.otf

FontAwesome.otf

6116 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

6593 ms

Lato-Bold.ttf

Lato-Bold.ttf

7815 ms

Lato-Light.ttf

Lato-Light.ttf

7863 ms

seal_bg.gif

seal_bg.gif

164 ms

anchor

anchor

32 ms

warranty_level.gif

warranty_level.gif

137 ms

Lato-Medium.ttf

Lato-Medium.ttf

7796 ms

styles__ltr.css

styles__ltr.css

3 ms

recaptcha__en.js

recaptcha__en.js

10 ms

81IjrRH91DAKpIx-VEJHPdpf7wiRaH8tg-uktu3LK4I.js

81IjrRH91DAKpIx-VEJHPdpf7wiRaH8tg-uktu3LK4I.js

68 ms

webworker.js

webworker.js

76 ms

logo_48.png

logo_48.png

58 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

26 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

52 ms

recaptcha__en.js

recaptcha__en.js

28 ms

Lato-Regular.ttf

Lato-Regular.ttf

7646 ms

Flaticon.svg

Flaticon.svg

6813 ms

Flaticon.woff

Flaticon.woff

6567 ms

Satisfy-Regular.ttf

Satisfy-Regular.ttf

7810 ms

timg6.jpg

timg6.jpg

7799 ms

ezy-banner.jpg

ezy-banner.jpg

7794 ms

blue-bk.jpg

blue-bk.jpg

7388 ms

about-bk.png

about-bk.png

7843 ms

whyus-bk.png

whyus-bk.png

8413 ms

blog1-n.jpg

blog1-n.jpg

7809 ms

testimonial-bk.jpg

testimonial-bk.jpg

7813 ms

footer-bk.jpg

footer-bk.jpg

7791 ms

r-arrow.png

r-arrow.png

7350 ms

lightbox-next.png

lightbox-next.png

7846 ms

lightbox-prev.png

lightbox-prev.png

7844 ms

lightbox-close.png

lightbox-close.png

7816 ms

comodo_secure_seal_76x26_transp.png

comodo_secure_seal_76x26_transp.png

6617 ms

bframe

bframe

24 ms

recaptcha__en.js

recaptcha__en.js

6 ms

large-devices(1366-1450).css

large-devices(1366-1450).css

1009 ms

large-devices(1200-1365).css

large-devices(1200-1365).css

1018 ms

medium-devices(992-1199).css

medium-devices(992-1199).css

1018 ms

tablet-devices(768-991).css

tablet-devices(768-991).css

1015 ms

mobile-devices(640-767).css

mobile-devices(640-767).css

1050 ms

andriod-devices(440-639).css

andriod-devices(440-639).css

1048 ms

mini-andriod-devices(350-439).css

mini-andriod-devices(350-439).css

1001 ms

mini-andriod-devices(320-349).css

mini-andriod-devices(320-349).css

1062 ms

mini-andriod-devices(1-319).css

mini-andriod-devices(1-319).css

1011 ms

Accessibility Review

ezymigrate.co.nz accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ezymigrate.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ezymigrate.co.nz SEO score

82

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezymigrate.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 Ezymigrate.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

ezymigrate.co.nz

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