12.2 sec in total
606 ms
11.2 sec
414 ms
Visit selke.co.nz now to see the best up-to-date Selke content and also check out these interesting facts you probably never knew about selke.co.nz
Visit selke.co.nzWe analyzed Selke.co.nz page load time and found that the first response time was 606 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
selke.co.nz performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value20.9 s
0/100
25%
Value22.1 s
0/100
10%
Value6,710 ms
0/100
30%
Value0.058
98/100
15%
Value30.0 s
0/100
10%
606 ms
5027 ms
602 ms
602 ms
603 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 65% of them (96 requests) were addressed to the original Selke.co.nz, 14% (21 requests) were made to Fonts.gstatic.com and 6% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Selke.co.nz.
Page size can be reduced by 387.6 kB (14%)
2.9 MB
2.5 MB
In fact, the total size of Selke.co.nz main page is 2.9 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 356.7 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 356.7 kB or 83% of the original size.
Potential reduce by 8.2 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. Selke images are well optimized though.
Potential reduce by 11.9 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.
Potential reduce by 10.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. Selke.co.nz has all CSS files already compressed.
Number of requests can be reduced by 93 (77%)
121
28
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Selke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
selke.co.nz
606 ms
selke.co.nz
5027 ms
style-maintenance.css
602 ms
sbi-styles.min.css
602 ms
wc-blocks-vendors-style.css
603 ms
wc-blocks-style.css
819 ms
settings.css
621 ms
webmad.css
620 ms
woocommerce-layout.css
618 ms
woocommerce.css
810 ms
styles.min.css
830 ms
pagenavi-css.css
830 ms
colorbox.css
829 ms
prettyPhoto.css
1003 ms
jquery.selectBox.css
1019 ms
style.css
1020 ms
font-awesome.min.css
1021 ms
css
47 ms
icomoon.css
221 ms
cache.skin.css
405 ms
newsletter.css
416 ms
photoswipe.min.css
415 ms
default-skin.min.css
416 ms
select2.css
418 ms
style.css
608 ms
footer.css
615 ms
header.css
616 ms
blog.css
617 ms
home.css
617 ms
woocommerce.css
792 ms
jquery.min.js
811 ms
jquery-migrate.min.js
825 ms
jquery.themepunch.tools.min.js
1018 ms
jquery.themepunch.revolution.min.js
829 ms
js
76 ms
mailchimp.js
827 ms
js
121 ms
basic.min.css
603 ms
theme-ie11.min.css
623 ms
theme.min.css
624 ms
frontend.js
626 ms
jquery.blockUI.min.js
862 ms
add-to-cart.min.js
860 ms
js.cookie.min.js
861 ms
woocommerce.min.js
861 ms
cart-fragments.min.js
860 ms
regenerator-runtime.min.js
859 ms
wp-polyfill.min.js
1112 ms
hooks.min.js
1118 ms
i18n.min.js
1119 ms
wc-blocks-google-analytics.js
1119 ms
woocompare.min.js
1118 ms
jquery.colorbox-min.js
1117 ms
jquery.prettyPhoto.min.js
1409 ms
jquery.selectBox.min.js
1408 ms
api.js
82 ms
jquery.yith-wcwl.js
1392 ms
mailchimp-woocommerce-public.min.js
1388 ms
scripts.min.js
1543 ms
smoothscroll.js
1392 ms
jquery.fitvids.js
1451 ms
afterpay-1.x.js
59 ms
jquery.mobile.js
1277 ms
frontend.js
1262 ms
newsletter-subscribe.js
1255 ms
common.js
1255 ms
jquery.flexslider.min.js
1446 ms
photoswipe.min.js
1449 ms
photoswipe-ui-default.min.js
1258 ms
single-product.min.js
1240 ms
country-select.min.js
1236 ms
address-i18n.min.js
1324 ms
checkout.min.js
1421 ms
select2.full.min.js
1261 ms
selectWoo.full.min.js
1249 ms
dom-ready.min.js
1238 ms
a11y.min.js
1238 ms
jquery.json.min.js
1285 ms
0bef27807a16a787c1a5b8408.js
177 ms
gtm.js
175 ms
K8a-NyWpT7Q
281 ms
gravityforms.min.js
1544 ms
S6uyw4BMUTPHjxAwWw.ttf
130 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
145 ms
S6u8w4BMUTPHh30AUi-v.ttf
150 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
199 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
199 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
199 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
149 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
175 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
201 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
201 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
200 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
200 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
200 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
200 ms
placeholders.jquery.min.js
1200 ms
frontend.min.js
1201 ms
modules.ttf
1496 ms
logo-high-res-cropped-delke.png
1659 ms
fur-cap-hero.jpg
1661 ms
hero-2-guys-optimized.jpg
1874 ms
ec2d98c5b6717f26e8a469182.js
403 ms
S6u8w4BMUTPHjxsAUi-v.ttf
110 ms
S6u_w4BMUTPHjxsI9w2_FQfo.ttf
108 ms
S6u-w4BMUTPHjxsIPx-mPCc.ttf
109 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
107 ms
S6u_w4BMUTPHjxsI3wi_FQfo.ttf
109 ms
www-player.css
25 ms
www-embed-player.js
77 ms
base.js
144 ms
hero-thermos-1.jpg
1618 ms
the-bowlers-hat.jpg
1400 ms
bush-hat.jpg
1400 ms
selke-original.jpg
1617 ms
fishermans-ghillie.jpg
1617 ms
ad_status.js
172 ms
DSC_0767-Copy-300x300.jpg
1431 ms
aDz_T_gaBrysQcZbaYaX8h92PYnkBHHJotKz2yKPZZ4.js
82 ms
embed.js
37 ms
DSC_0204-300x300.jpg
1329 ms
DSC_0438-300x300.jpg
1665 ms
DSC_0263-300x300.jpg
1449 ms
cleangreennz.jpg
2046 ms
nz-made-e1659490633221.png
1428 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
31 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
30 ms
id
27 ms
Create
192 ms
payment-online-3cards.png
1389 ms
recaptcha__en.js
26 ms
GenerateIT
14 ms
afterpay_logo_small-c21f624e13e513b83e729c61fa161b4d75643a4e62d4dcd3df62e1c5d3ed7326.svg
50 ms
polyfill.min.js
1057 ms
selke.co.nz
2779 ms
qoe
8 ms
log_event
0 ms
K8a-NyWpT7Q
118 ms
ad_status.js
55 ms
Create
71 ms
id
24 ms
GenerateIT
21 ms
webcomponents-bundle.js
70 ms
webcomponents-bundle.js
20 ms
log_event
16 ms
woocommerce-smallscreen.css
202 ms
style.min.css
204 ms
style.min.css
204 ms
selke.co.nz accessibility score
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
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
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.
selke.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
selke.co.nz SEO score
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 Selke.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 Selke.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.
selke.co.nz
Open Graph description is not detected on the main page of Selke. 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: