4.8 sec in total
683 ms
3.4 sec
724 ms
Click here to check amazing Catch content for New Zealand. Otherwise, check out these important facts you probably never knew about catch.co.nz
All your favourite brands for less - right here at Catch New Zealand. The latest tech, big brand fashion, bulk groceries and everything else - delivered straight to your door.
Visit catch.co.nzWe analyzed Catch.co.nz page load time and found that the first response time was 683 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
catch.co.nz performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value17.1 s
0/100
25%
Value18.1 s
0/100
10%
Value5,240 ms
0/100
30%
Value0.151
75/100
15%
Value24.3 s
0/100
10%
683 ms
814 ms
205 ms
232 ms
466 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 54% of them (32 requests) were addressed to the original Catch.co.nz, 27% (16 requests) were made to and 10% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Catch.co.nz.
Page size can be reduced by 100.5 kB (13%)
749.1 kB
648.7 kB
In fact, the total size of Catch.co.nz main page is 749.1 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. 50% of websites need less resources to load. Images take 575.9 kB which makes up the majority of the site volume.
Potential reduce by 14.2 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 14.2 kB or 72% of the original size.
Potential reduce by 0 B
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. Catch images are well optimized though.
Potential reduce by 76.4 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 76.4 kB or 54% of the original size.
Potential reduce by 9.9 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. Catch.co.nz needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 78% of the original size.
Number of requests can be reduced by 8 (22%)
37
29
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
catch.co.nz
683 ms
fonts.css
814 ms
idc3ihq.js
205 ms
styles.css
232 ms
vendorpredom.js
466 ms
vendorpostdom.js
690 ms
all.js
465 ms
catch.co.nz
227 ms
main.css
235 ms
normalize.css
233 ms
01_2degrees@2x.jpg
245 ms
02_Unitec@2x.jpg
243 ms
03_SportNZ@2x.jpg
244 ms
04_HighPerfSportNZ@2x.jpg
243 ms
05_Kiwirail@2x.jpg
469 ms
06_WellingtonRugby@2x.jpg
467 ms
07_Hurricanes@2x.jpg
468 ms
08_ACC@2x.jpg
467 ms
09_LottoNZ@2x.jpg
466 ms
12_NZSevens@2x.jpg
463 ms
img-2degrees.jpg
918 ms
img-2degreesbroadband.jpg
692 ms
img-rio2016.jpg
918 ms
img-2degrees-calculator.jpg
920 ms
img-iPhone.jpg
923 ms
img-unitec.jpg
924 ms
img-hurricanes.jpg
918 ms
img-hpsnz.jpg
1371 ms
img-scotts.jpg
1600 ms
img-sisters.jpg
1373 ms
img-dukes.jpg
1374 ms
img-activr-smart.jpg
1611 ms
our-process-illus2x.png
1153 ms
our-team-illus@2x.png
1386 ms
our-client-illus@2x.png
1597 ms
analytics.js
47 ms
n+08+hOj89J+Qusfj7X
29 ms
M9D7f
29 ms
PSfkLrH4+1w==
28 ms
0c6jOz0+J+UvzPQ+3w==
28 ms
LxI7nMdxzE+Pdt5difHP0r5C19bPi0=
28 ms
wT41
28 ms
AXeCiFSfQ1Yp7Mai+RyA8cCd4IvNwN1CygwWvNy0pL1U5kPDTPLnPdRrH+PRs59mdnP4oxS+P9D45
28 ms
j0bOfZnRz+KMUvb44+MQ==
27 ms
SvkLX1s+LQ==
26 ms
wT41
26 ms
AXeCiFSfQ1Yp7Mai+RyA8cCd4IvNwN1CygwWvNy0pL1U5kPDTPLnPdRrH+PRs59mdnP4oxS+P9D45
26 ms
3yjP55zdy1KzkE8GsT+tmjqcg8JSd8uSP+Ypcoi+dskONL5Z5scwjljl2Sj70epS9uDrs4M3VW8iWy9kEZml6cSbzfynkyQNeHpyQqIX7UVxv1vBZSZaQxRNwHzhrxQl0teJeDKpvERzuuBM8kXm4GyjZwYLX29YpL1U5kPDTPHnIdRjH+PRs59mdHP4oxS9vjj4x
26 ms
5dDkd7hFcEJiVq4H+VH4pZo+EKdkSjHZgq4tZ4V5Az6RnFHxtpvERzuuB88mdnZQMU6Frxed055qaqRiU+K9C7gYSzjwzOeZ3h6eFrKXxDdQSs=
25 ms
A0QSM=
25 ms
5dDkd7hFcEJiVq4H+VH4pZo+EKdkSjHZgq4tZ4V5Az6RnFHxtpvERzuuB88mdnZQMU6Frxed055qaqRiU+K9C7gYSzjwzOeZ3h6eFrKXxDdQSs=
25 ms
A0QSM=
25 ms
vsHljiTUx-oVan3kVJ-qIwRshRx4N5E_nnGzZwxe6i9ff4egggMmeMJ6Mk6f5MS.woff
79 ms
OmaIed-3hka-3DR-Mg_REgpsXUQw0neILzMQAWv-1LSff5WcggMmeMJ6Mk6f5Mb.woff
122 ms
XAvffsOIO_BRPkCW8PIUbcmQ_b8cOS3Vj2RbVt-HzQbff4AgggMmeMJ6Mk6f5Mt.woff
178 ms
hLJcW1QEiiMR5vPSaNpY4U-fPW59AOLtUeD4aixNNGMff4HgggMmeMJ6Mk6f5gI.woff
181 ms
collect
63 ms
collect
83 ms
p.gif
118 ms
catch.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.
ARIA
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.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
catch.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
Browser errors were logged to the console
Page has valid source maps
catch.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catch.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 Catch.co.nz main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
catch.co.nz
Open Graph description is not detected on the main page of Catch. 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: