9.7 sec in total
724 ms
7.4 sec
1.6 sec
Visit supcentre.co.nz now to see the best up-to-date SUPcentre content for New Zealand and also check out these interesting facts you probably never knew about supcentre.co.nz
Browse our quality range of stand up paddle board, surf and wing foil gear. Huge range of brands to choose from in-store and online at great prices. Shop with us!
Visit supcentre.co.nzWe analyzed Supcentre.co.nz page load time and found that the first response time was 724 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
supcentre.co.nz performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value10.3 s
0/100
25%
Value11.7 s
4/100
10%
Value11,610 ms
0/100
30%
Value0.547
13/100
15%
Value19.5 s
2/100
10%
724 ms
1385 ms
37 ms
660 ms
986 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 31% of them (18 requests) were addressed to the original Supcentre.co.nz, 22% (13 requests) were made to Cdn.n2erp.co.nz and 15% (9 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Cdn.n2erp.co.nz.
Page size can be reduced by 463.6 kB (10%)
4.8 MB
4.3 MB
In fact, the total size of Supcentre.co.nz main page is 4.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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 153.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. This page needs HTML code to be minified as it can gain 57.6 kB, which is 33% 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 153.4 kB or 88% of the original size.
Potential reduce by 302.1 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. SUPcentre images are well optimized though.
Potential reduce by 8.1 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 8.1 kB or 24% of the original size.
Potential reduce by 0 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. Supcentre.co.nz has all CSS files already compressed.
Number of requests can be reduced by 13 (27%)
49
36
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SUPcentre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
supcentre.co.nz
724 ms
www.supcentre.co.nz
1385 ms
css
37 ms
site
660 ms
modernizr
986 ms
lightwidget.js
323 ms
getgeotrustsslseal
6 ms
first
2035 ms
gtm.js
808 ms
analytics.js
792 ms
fbevents.js
864 ms
loader.js
929 ms
embed
753 ms
ensismbsept22_ofyrwuzl.tht.png
4249 ms
NZ.png
641 ms
leaves_lhs_resized.png
1157 ms
leaves_rhs_resized.png
1155 ms
logo.png
2151 ms
hot.png
1284 ms
instagram.jpg
1284 ms
facebook.png
1670 ms
visa.png
1670 ms
mastercard.png
1668 ms
qcard.png
1669 ms
debit.png
1669 ms
redpaddlecobanner_0smu1aoh.r5v.png
4163 ms
critical-slide_wibogoda.mth.png
3662 ms
untitleddesign29_nmg3r0vc.mxq.png
1998 ms
untitleddesign1_avfum0yu.0zo.png
2125 ms
untitleddesign27rbhr_sby5ngmr.moo.png
1998 ms
untitleddesign28_iob3l5sm.xbo.png
2138 ms
103343_x1n3unew.5hp.png
2138 ms
100138_636431576105388613.jpg
2728 ms
untitleddesign_cb0qisxq.nxn.png
2421 ms
sidewinder-blue_op0siphr.itt.png
2420 ms
untitleddesign28_naadzqlo.nlu.png
2728 ms
untitleddesign27rbhr_f14h1fdm.z4r.png
2727 ms
9ff50f8095d65466aa3b227d465ada06.html
422 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
295 ms
fontawesome-webfont.woff
1807 ms
collect
119 ms
515190451985187
168 ms
app.js
73 ms
collect
92 ms
js
464 ms
4816-756-10-9054.js
179 ms
ga-audiences
424 ms
c
380 ms
application2.js
369 ms
gen_204
429 ms
init_embed.js
457 ms
storage.html
46 ms
storage.js
21 ms
visits
236 ms
theme.css
96 ms
log.png
333 ms
favicon.png
290 ms
noto-sans-v11-latin-regular.woff
21 ms
noto-sans-v11-latin-700.woff
57 ms
supcentre.co.nz accessibility score
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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
supcentre.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
supcentre.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Supcentre.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Supcentre.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.
supcentre.co.nz
Open Graph description is not detected on the main page of SUPcentre. 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: