Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

zyber.io

eCommerce Conversion Specialists | Shopify Experts Auckland - Zyber

Page Load Speed

21.1 sec in total

First Response

432 ms

Resources Loaded

5 sec

Page Rendered

15.7 sec

zyber.io screenshot

About Website

Click here to check amazing Zyber content for Australia. Otherwise, check out these important facts you probably never knew about zyber.io

Auckland based eCommerce Agency. Zyber are NZ's leading Shopify Experts, specialised in Web Design, eCommerce Strategy, and Conversion Optimisation.

Visit zyber.io

Key Findings

We analyzed Zyber.io page load time and found that the first response time was 432 ms and then it took 20.7 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

zyber.io performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value29.1 s

0/100

10%

Network Requests Diagram

zyber.io

432 ms

www.zyber.co.nz

441 ms

css2

84 ms

theme.css

65 ms

z-custom.css

56 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zyber.io, 67% (63 requests) were made to Zyber.co.nz and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Zyber.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 645.2 kB (2%)

Content Size

26.5 MB

After Optimization

25.9 MB

In fact, the total size of Zyber.io main page is 26.5 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. Only a small number of websites need less resources to load. Images take 25.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 150.3 kB

  • Original 188.6 kB
  • After minification 179.0 kB
  • After compression 38.4 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 150.3 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 486.8 kB

  • Original 25.9 MB
  • After minification 25.4 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. Zyber images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.7 kB

  • Original 410.8 kB
  • After minification 410.8 kB
  • After compression 403.2 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

-1%

Potential reduce by 514 B

  • Original 44.7 kB
  • After minification 44.7 kB
  • After compression 44.1 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. Zyber.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (42%)

Requests Now

85

After Optimization

49

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

Accessibility Review

zyber.io accessibility score

90

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

zyber.io 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

Missing source maps for large first-party JavaScript

SEO Factors

zyber.io SEO score

92

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

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 Zyber.io 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 Zyber.io 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 data is detected on the main page of Zyber. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: