7.1 sec in total
1.2 sec
5.5 sec
437 ms
Visit charthouse.co.nz now to see the best up-to-date Charthouse content and also check out these interesting facts you probably never knew about charthouse.co.nz
A stunning wedding venue in Tauranga the Charthouse overlooks the marina, with Mount Maunganui & harbour views. Perfect for any occasion our function venue is dedicated to celebratory Tauranga fun...
Visit charthouse.co.nzWe analyzed Charthouse.co.nz page load time and found that the first response time was 1.2 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
charthouse.co.nz performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value19.7 s
0/100
25%
Value18.0 s
0/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
1233 ms
190 ms
1127 ms
1347 ms
376 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 93% of them (39 requests) were addressed to the original Charthouse.co.nz, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Webintelligence.net.nz. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Charthouse.co.nz.
Page size can be reduced by 784.9 kB (35%)
2.2 MB
1.5 MB
In fact, the total size of Charthouse.co.nz main page is 2.2 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. 20% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 13.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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 15% 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 13.8 kB or 78% of the original size.
Potential reduce by 101.4 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. Charthouse images are well optimized though.
Potential reduce by 388.7 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 388.7 kB or 69% of the original size.
Potential reduce by 281.1 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. Charthouse.co.nz needs all CSS files to be minified and compressed as it can save up to 281.1 kB or 86% of the original size.
Number of requests can be reduced by 24 (62%)
39
15
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charthouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.charthouse.co.nz
1233 ms
grid-responsive.css
190 ms
bootstrap.css
1127 ms
master-b275c31aaa7d1090768f34e5b36a9e61.css
1347 ms
mediaqueries.css
376 ms
menu.css
377 ms
rt_spectral-custom.css
375 ms
slideshow.css
377 ms
jquery.min.js
1308 ms
jquery-noconflict.js
560 ms
jquery-migrate.min.js
560 ms
caption.js
561 ms
mootools-core.js
1311 ms
core.js
748 ms
mootools-more.js
1878 ms
chart.js
1123 ms
browser-engines.js
1306 ms
rokmediaqueries.js
1311 ms
rokmediaqueries.js
1491 ms
sidemenu.js
1492 ms
mootools-mobile.js
1494 ms
rokmediaqueries.js
1500 ms
roksprocket.js
1524 ms
moofx.js
1679 ms
features.js
1681 ms
slideshow.js
1680 ms
analytics.js
53 ms
wi-logo.png
569 ms
header-image.jpg
1166 ms
noise.png
196 ms
Logo2.jpg
193 ms
9454c5df18f6fd240b216a032acff5f3_300_1200.JPG
1320 ms
60529a64ce79a035ff5afdfcbf0e2957_300_1200.jpg
1248 ms
b2420e430f298087475e5bfbe316d01e_300_1200.JPG
581 ms
0f15aab607363796b53534012a12f287_300_1200.JPG
1325 ms
290f4c6ca272e19cae6fd568b704238e_300_1200.JPG
1337 ms
FrontPg.JPG
772 ms
image003.jpg
962 ms
logo.png
1153 ms
quicksand-regular-webfont.woff
1344 ms
quicksand-bold-webfont.woff
1360 ms
collect
12 ms
charthouse.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.
charthouse.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
charthouse.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 Charthouse.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 Charthouse.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.
charthouse.co.nz
Open Graph description is not detected on the main page of Charthouse. 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: