5.2 sec in total
1.4 sec
3.2 sec
612 ms
Welcome to queenstownnz.com homepage info - get ready to check Queenstownnz best content right away, or after learning these important things about queenstownnz.com
Visit queenstownnz.comWe analyzed Queenstownnz.com page load time and found that the first response time was 1.4 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Queenstownnz.com rating and web reputation
queenstownnz.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.8 s
82/100
25%
Value2.5 s
98/100
10%
Value100 ms
98/100
30%
Value0.029
100/100
15%
Value2.9 s
96/100
10%
1359 ms
17 ms
104 ms
199 ms
124 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Queenstownnz.com, 19% (14 requests) were made to Aff.bstatic.com and 11% (8 requests) were made to Secure.rezserver.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Secure.rezserver.com.
Page size can be reduced by 632.9 kB (54%)
1.2 MB
537.8 kB
In fact, the total size of Queenstownnz.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 693.9 kB which makes up the majority of the site volume.
Potential reduce by 133.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. This page needs HTML code to be minified as it can gain 28.0 kB, which is 18% 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 133.2 kB or 86% of the original size.
Potential reduce by 7.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. Queenstownnz images are well optimized though.
Potential reduce by 447.0 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 447.0 kB or 64% of the original size.
Potential reduce by 45.6 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. Queenstownnz.com needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 78% of the original size.
Number of requests can be reduced by 29 (46%)
63
34
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Queenstownnz. 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 5 to 1 for CSS and as a result speed up the page load time.
7433-800051304
1359 ms
ga.js
17 ms
rs_template_boilerplate.css
104 ms
ref-7433.css
199 ms
jquery-2.0.3.min.js
124 ms
rs_style.css
68 ms
rs_style_resp.css
69 ms
__utm.gif
20 ms
__utm.gif
34 ms
hotel.min.js
262 ms
en-us.js
105 ms
collect
62 ms
gpt.js
123 ms
analytics.js
82 ms
header_logo.png
82 ms
default.jpg
67 ms
footer_logo.png
212 ms
8426774.jpg
318 ms
thumbnail-75-square.jpg
192 ms
hotel_img_na.jpg
183 ms
49461320.jpg
460 ms
33516749.jpg
298 ms
50320047.jpg
303 ms
2559764.jpg
299 ms
50319230.jpg
302 ms
29237034.jpg
460 ms
38433866.jpg
459 ms
29236876.jpg
462 ms
32179677.jpg
460 ms
40418004.jpg
462 ms
19194080.jpg
463 ms
48353474.jpg
459 ms
20563956.jpg
457 ms
thumbnail-150-square.jpg
173 ms
7433-800051304
1362 ms
rs.woff
170 ms
collect
134 ms
collect
131 ms
js
53 ms
loader_wbg.gif
48 ms
pubads_impl_82.js
43 ms
collect
79 ms
collect
74 ms
container.html
49 ms
common.js
25 ms
map.js
25 ms
util.js
28 ms
marker.js
22 ms
onion.js
92 ms
openhand_8_8.cur
48 ms
ViewportInfoService.GetViewportInfo
126 ms
stats.js
28 ms
controls.js
21 ms
infowindow.js
20 ms
transparent.png
42 ms
css
43 ms
google4.png
37 ms
marker_hotel.svg
29 ms
mapcnt6.png
67 ms
sv5.png
67 ms
vt
83 ms
vt
29 ms
vt
78 ms
vt
79 ms
vt
81 ms
vt
82 ms
vt
82 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
22 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
AuthenticationService.Authenticate
35 ms
queenstownnz.com 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.
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
queenstownnz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
queenstownnz.com 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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Queenstownnz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Queenstownnz.com 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.
queenstownnz.com
Open Graph description is not detected on the main page of Queenstownnz. 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: