8.4 sec in total
2 sec
6.2 sec
156 ms
Visit cleaversedge.co.nz now to see the best up-to-date Cleaversedge content and also check out these interesting facts you probably never knew about cleaversedge.co.nz
Visit cleaversedge.co.nzWe analyzed Cleaversedge.co.nz page load time and found that the first response time was 2 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cleaversedge.co.nz performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value13.2 s
0/100
25%
Value22.2 s
0/100
10%
Value2,130 ms
6/100
30%
Value0
100/100
15%
Value23.3 s
1/100
10%
2032 ms
632 ms
402 ms
444 ms
834 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Cleaversedge.co.nz, 4% (2 requests) were made to Facebook.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Cleaversedge.co.nz.
Page size can be reduced by 416.5 kB (39%)
1.1 MB
645.0 kB
In fact, the total size of Cleaversedge.co.nz main page is 1.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. 45% of websites need less resources to load. Images take 547.7 kB which makes up the majority of the site volume.
Potential reduce by 18.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 18.4 kB or 73% of the original size.
Potential reduce by 19.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. Cleaversedge images are well optimized though.
Potential reduce by 212.6 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 212.6 kB or 72% of the original size.
Potential reduce by 165.8 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. Cleaversedge.co.nz needs all CSS files to be minified and compressed as it can save up to 165.8 kB or 85% of the original size.
Number of requests can be reduced by 23 (53%)
43
20
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cleaversedge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.cleaversedge.co.nz
2032 ms
wp-emoji-release.min.js
632 ms
styles.css
402 ms
woocommerce-layout.css
444 ms
woocommerce.css
834 ms
style.css
1114 ms
font-awesome.css
890 ms
jquery.js
1183 ms
jquery-migrate.min.js
649 ms
jquery.flexslider.min.js
942 ms
jquery.touchSwipe.min.js
1125 ms
jquery.theme-main.min.js
1024 ms
flexslider.css
917 ms
public.css
967 ms
jquery.form.min.js
1065 ms
scripts.js
1114 ms
add-to-cart.min.js
1146 ms
jquery.blockUI.min.js
1153 ms
woocommerce.min.js
1155 ms
jquery.cookie.min.js
1204 ms
cart-fragments.min.js
1269 ms
wp-embed.min.js
1349 ms
jquery.flexslider-min.js
1534 ms
Cleavers-Edge-Logo2-e1453366662636.png
322 ms
Lamb-Rack-4-e1453368151881-700x300.jpg
703 ms
Rib-1-e1453368173982-700x300.jpg
1590 ms
Pork-Belly-slices-1-e1453368302808-700x300.jpg
840 ms
Sirloin-1-e1453368326521-700x300.jpg
941 ms
Sausages-1-e1453368347395-700x300.jpg
1162 ms
MeatCleaverMeat-300x199.jpg
701 ms
simple-smile.png
1020 ms
fontawesome-webfont.woff
1099 ms
sdk.js
13 ms
106 ms
xd_arbiter.php
35 ms
xd_arbiter.php
43 ms
www.cleaversedge.co.nz
1032 ms
slide-indicator-active.png
641 ms
slide-indicator-inactive.png
661 ms
gallery-prev.png
738 ms
gallery-next.png
744 ms
like.php
86 ms
qeKvIRsJabD.js
37 ms
LVx-xkvaJ0b.png
22 ms
woocommerce-smallscreen.css
207 ms
cleaversedge.co.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cleaversedge.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cleaversedge.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cleaversedge.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 Cleaversedge.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.
cleaversedge.co.nz
Open Graph description is not detected on the main page of Cleaversedge. 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: