Access netpotential.co.nz. Web Design and Web Development Agency in Auckland | Web Design | eCommerce | App Development

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value25.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

netpotential.co.nz

677 ms

www.netpotential.co.nz

2152 ms

default.css

1026 ms

skin.css

530 ms

jquery.fancybox.css

533 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Netpotential.co.nz, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Netpotential.co.nz.

Content Size

1.8 MB

After Optimization

690.2 kB

In fact, the total size of Netpotential.co.nz main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 962.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 41.1 kB

Original 50.6 kB
After minification 40.7 kB
After compression 9.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. This page needs HTML code to be minified as it can gain 9.8 kB, which is 19% 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 41.1 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 15.7 kB

Original 420.7 kB
After minification 404.9 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. Net Potential images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 732.3 kB

Original 962.6 kB
After minification 747.9 kB
After compression 230.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 732.3 kB or 76% of the original size.

CSS Optimization

-86%

Potential reduce by 289.9 kB

Original 335.5 kB
After minification 241.1 kB
After compression 45.6 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. Netpotential.co.nz needs all CSS files to be minified and compressed as it can save up to 289.9 kB or 86% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

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

netpotential.co.nz

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Web Design and Web Development Agency in Auckland | Web Design | eCommerce | App Development | NetPotential!

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

netpotential.co.nz

www.netpotential.co.nz

default.css

skin.css

jquery.fancybox.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

netpotential.co.nz

www.netpotential.co.nz

default.css

skin.css

jquery.fancybox.css

jquery.js

jquery-migrate.js

WebResource.axd

Telerik.Web.UI.WebResource.axd

dnncore.js

jquery.fancybox.pack.js

styles.css

rgs.css

font-awesome.min.css

style.css

responsive.css

orbit.css

modernizr.js

imagesLoaded.min.js

comment-reply.min.js

jplayer.min.js

phill.css

skin.css

jquery.form.min.js

scripts.js

superfish.js

easing.js

respond.js

swipe.min.js

nicescroll.js

sticky.js

prettyPhoto.js

flexslider.min.js

isotope.min.js

carouFredSel.min.js

appear.js

orbit.js

init.js

nectar-love.js

initWidgets.js

ga.js

logo.png

no-video-img.png