Tools & Wizards About Us
ezyvision.co.nz screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ezyvision.co.nz

How to get FREE contact lenses Watch how this NZ user does!

Page Load Speed

5.2 sec in total

First Response

947 ms

Resources Loaded

3.8 sec

Page Rendered

437 ms

ezyvision.co.nz screenshot

About Website

Click here to check amazing Ezyvision content for New Zealand. Otherwise, check out these important facts you probably never knew about ezyvision.co.nz

Its crazy but yes they offer FREE Contact Lenses! Free trials + Delivery Next Day or theyre Free Guarantee. NZ only tho but worth checking out Low prices too

Visit ezyvision.co.nz

Key Findings

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

Performance Metrics

ezyvision.co.nz performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value11.1 s

5/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

ezyvision.co.nz

947 ms

ezyvision.co.nz

107 ms

style-block.css

29 ms

styles.css

56 ms

font-awesome.min.css

52 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 85% of them (94 requests) were addressed to the original Ezyvision.co.nz, 12% (13 requests) were made to Embed.tawk.to and 3% (3 requests) were made to Static.mailerlite.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ezyvision.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.9 kB (36%)

Content Size

391.3 kB

After Optimization

249.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ezyvision.co.nz main page is 391.3 kB. 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 179.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 118.1 kB

  • Original 152.9 kB
  • After minification 149.4 kB
  • After compression 34.9 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 118.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 122 B

  • Original 58.6 kB
  • After minification 58.5 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. Ezyvision images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 23.7 kB

  • Original 179.4 kB
  • After minification 179.4 kB
  • After compression 155.7 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 23.7 kB or 13% of the original size.

CSS Optimization

-23%

Potential reduce by 88 B

  • Original 376 B
  • After minification 376 B
  • After compression 288 B

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. Ezyvision.co.nz needs all CSS files to be minified and compressed as it can save up to 88 B or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 92 (88%)

Requests Now

104

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ezyvision.co.nz

ezyvision.co.nz

947 ms

ezyvision.co.nz

ezyvision.co.nz

107 ms

style-block.css

style-block.css

29 ms

styles.css

styles.css

56 ms

font-awesome.min.css

font-awesome.min.css

52 ms

bootstrap-front.css

bootstrap-front.css

53 ms

front.css

front.css

76 ms

alertify.min.css

alertify.min.css

77 ms

wlr-main.min.css

wlr-main.min.css

86 ms

wlr-fonts.min.css

wlr-fonts.min.css

102 ms

wlr-fonts.min.css

wlr-fonts.min.css

347 ms

launcher_site_ui.css

launcher_site_ui.css

1036 ms

style_register_widget.css

style_register_widget.css

118 ms

style.css

style.css

112 ms

dashicons.min.css

dashicons.min.css

118 ms

style.css

style.css

152 ms

style.css

style.css

1044 ms

flatsome.css

flatsome.css

169 ms

flatsome-shop.css

flatsome-shop.css

152 ms

style.css

style.css

204 ms

jquery.min.js

jquery.min.js

204 ms

jquery-migrate.min.js

jquery-migrate.min.js

228 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

245 ms

add-to-cart.min.js

add-to-cart.min.js

242 ms

js.cookie.min.js

js.cookie.min.js

283 ms

cart-fragments.min.js

cart-fragments.min.js

291 ms

alertify.min.js

alertify.min.js

299 ms

bundle.js

bundle.js

1441 ms

jquery.validate.min.js

jquery.validate.min.js

345 ms

additional-methods.js

additional-methods.js

347 ms

public.js

public.js

415 ms

wc-blocks.css

wc-blocks.css

385 ms

hooks.min.js

hooks.min.js

394 ms

i18n.min.js

i18n.min.js

444 ms

index.js

index.js

426 ms

index.js

index.js

443 ms

accordion-custom.js

accordion-custom.js

472 ms

accordion.js

accordion.js

458 ms

woocommerce.min.js

woocommerce.min.js

441 ms

react.min.js

react.min.js

484 ms

react-dom.min.js

react-dom.min.js

482 ms

escape-html.min.js

escape-html.min.js

456 ms

element.min.js

element.min.js

522 ms

react-jsx-runtime.min.js

react-jsx-runtime.min.js

495 ms

deprecated.min.js

deprecated.min.js

492 ms

dom.min.js

dom.min.js

511 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

508 ms

keycodes.min.js

keycodes.min.js

538 ms

priority-queue.min.js

priority-queue.min.js

546 ms

compose.min.js

compose.min.js

503 ms

private-apis.min.js

private-apis.min.js

538 ms

redux-routine.min.js

redux-routine.min.js

513 ms

data.min.js

data.min.js

501 ms

url.min.js

url.min.js

524 ms

api-fetch.min.js

api-fetch.min.js

508 ms

wp-polyfill.min.js

wp-polyfill.min.js

504 ms

wc-cart-checkout-base-frontend.js

wc-cart-checkout-base-frontend.js

533 ms

wc-cart-checkout-vendors-frontend.js

wc-cart-checkout-vendors-frontend.js

510 ms

wc-settings.js

wc-settings.js

493 ms

wc-blocks-registry.js

wc-blocks-registry.js

509 ms

wc-types.js

wc-types.js

474 ms

data-controls.min.js

data-controls.min.js

492 ms

html-entities.min.js

html-entities.min.js

498 ms

notices.min.js

notices.min.js

472 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

488 ms

wc-blocks-data.js

wc-blocks-data.js

465 ms

dom-ready.min.js

dom-ready.min.js

468 ms

a11y.min.js

a11y.min.js

472 ms

primitives.min.js

primitives.min.js

470 ms

blocks-components.js

blocks-components.js

454 ms

warning.min.js

warning.min.js

469 ms

blocks-checkout.js

blocks-checkout.js

461 ms

wlr-main.min.js

wlr-main.min.js

1347 ms

reorder.js

reorder.js

1309 ms

flatsome-live-search.js

flatsome-live-search.js

467 ms

sourcebuster.min.js

sourcebuster.min.js

489 ms

order-attribution.min.js

order-attribution.min.js

502 ms

hoverIntent.min.js

hoverIntent.min.js

490 ms

flatsome.js

flatsome.js

490 ms

woocommerce.js

woocommerce.js

538 ms

maxmegamenu.js

maxmegamenu.js

461 ms

universal.js

universal.js

130 ms

Ezyvision_Banner_350x.png

Ezyvision_Banner_350x.png

119 ms

menu.png

menu.png

119 ms

facebook1.png

facebook1.png

118 ms

instagram1.webp

instagram1.webp

118 ms

Truemoist-contact-lenses-368x368.jpg

Truemoist-contact-lenses-368x368.jpg

122 ms

Hypervue3D-30pk_1BT00416_01_720x-1-368x368.webp

Hypervue3D-30pk_1BT00416_01_720x-1-368x368.webp

121 ms

Perception3pk_720x-368x368.webp

Perception3pk_720x-368x368.webp

119 ms

Courierpost1-1200x800.webp

Courierpost1-1200x800.webp

125 ms

Customer_service.webp

Customer_service.webp

151 ms

Kiwi_fern3-1201x800.webp

Kiwi_fern3-1201x800.webp

145 ms

Assistant-Regular.woff

Assistant-Regular.woff

1000 ms

Assistant-Bold.woff

Assistant-Bold.woff

113 ms

wARDj0u

wARDj0u

4 ms

fl-icons.ttf

fl-icons.ttf

1017 ms

universal.css

universal.css

63 ms

default

default

190 ms

o3x6f7v7w8_popups.js

o3x6f7v7w8_popups.js

156 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

140 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

156 ms

twk-event-polyfill.js

twk-event-polyfill.js

163 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

157 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

95 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

167 ms

twk-main.js

twk-main.js

116 ms

twk-vendor.js

twk-vendor.js

130 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

149 ms

twk-chunk-common.js

twk-chunk-common.js

155 ms

twk-runtime.js

twk-runtime.js

168 ms

twk-app.js

twk-app.js

169 ms

Accessibility Review

ezyvision.co.nz accessibility score

89

Accessibility Issues

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

ezyvision.co.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ezyvision.co.nz SEO score

89

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

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 Ezyvision.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 Ezyvision.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

ezyvision.co.nz

Open Graph data is detected on the main page of Ezyvision. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: