2.2 sec in total
345 ms
1.7 sec
206 ms
Visit guide2.co.nz now to see the best up-to-date Guide 2 content for New Zealand and also check out these interesting facts you probably never knew about guide2.co.nz
discover & share
Visit guide2.co.nzWe analyzed Guide2.co.nz page load time and found that the first response time was 345 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
guide2.co.nz performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.0 s
13/100
25%
Value4.8 s
66/100
10%
Value3,540 ms
1/100
30%
Value0
100/100
15%
Value14.4 s
9/100
10%
345 ms
62 ms
68 ms
81 ms
140 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Guide2.co.nz, 15% (8 requests) were made to C0.wp.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (444 ms) relates to the external source Recommended.nz.
Page size can be reduced by 148.3 kB (8%)
1.9 MB
1.7 MB
In fact, the total size of Guide2.co.nz main page is 1.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 74.8 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 74.8 kB or 86% of the original size.
Potential reduce by 51.5 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. Guide 2 images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 19.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. Guide2.co.nz needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 20% of the original size.
Number of requests can be reduced by 36 (71%)
51
15
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guide 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
recommended.nz
345 ms
mediaelementplayer-legacy.min.css
62 ms
wp-mediaelement.min.css
68 ms
styles.css
81 ms
frontend.min.css
140 ms
flatpickr.min.css
175 ms
select2.min.css
173 ms
style.css
230 ms
style.css
175 ms
css
87 ms
blocks.css
176 ms
elementor-icons.min.css
193 ms
frontend.min.css
285 ms
swiper.min.css
228 ms
post-9259.css
232 ms
font-awesome.min.css
233 ms
global.css
253 ms
css
101 ms
jetpack.css
65 ms
jquery.min.js
64 ms
jquery-migrate.min.js
63 ms
flatpickr.min.js
337 ms
select2.min.js
306 ms
js
138 ms
adsbygoogle.js
155 ms
image-cdn.js
305 ms
index.js
306 ms
index.js
308 ms
frontend.min.js
425 ms
navigation.js
425 ms
skip-link-focus-fix.js
426 ms
menus.js
426 ms
api.js
81 ms
wp-polyfill-inert.min.js
59 ms
regenerator-runtime.min.js
61 ms
wp-polyfill.min.js
70 ms
index.js
425 ms
e-202419.js
69 ms
Recommended-logo-small.png
200 ms
Round-recommended-heart.png
209 ms
how-to-check-yourself-for-skin-cancer.jpg
196 ms
huka-square-0807.jpg
334 ms
bedbugs.jpg
195 ms
tools.jpg
294 ms
how-to-tie-a-windsor-knot.jpg
193 ms
guide-to-the-basic-principles-of-exercise.jpg
195 ms
things-to-do-with-the-kids-for-free-in-wellington.jpg
296 ms
recommended-alcohol-intake.jpg
293 ms
recommended-daily-exercise.jpg
294 ms
recommended-superfoods.png
444 ms
how-to-understand-your-cat.jpg
340 ms
recaptcha__en.js
109 ms
font
39 ms
font
130 ms
genericons-regular-webfont.woff
123 ms
guide2.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
Links do not have a discernible name
guide2.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
guide2.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guide2.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 Guide2.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.
guide2.co.nz
Open Graph data is detected on the main page of Guide 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: