2.3 sec in total
404 ms
1.7 sec
190 ms
Visit queenswaypark.com now to see the best up-to-date Queenswaypark content and also check out these interesting facts you probably never knew about queenswaypark.com
Visit queenswaypark.comWe analyzed Queenswaypark.com page load time and found that the first response time was 404 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.
queenswaypark.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.3 s
42/100
25%
Value4.0 s
80/100
10%
Value400 ms
68/100
30%
Value0.085
93/100
15%
Value6.6 s
57/100
10%
404 ms
25 ms
544 ms
304 ms
508 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 75% of them (33 requests) were addressed to the original Queenswaypark.com, 5% (2 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (544 ms) belongs to the original domain Queenswaypark.com.
Page size can be reduced by 147.7 kB (21%)
713.3 kB
565.6 kB
In fact, the total size of Queenswaypark.com main page is 713.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 491.7 kB which makes up the majority of the site volume.
Potential reduce by 9.9 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.8 kB, which is 20% 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 9.9 kB or 72% of the original size.
Potential reduce by 15.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. Queenswaypark images are well optimized though.
Potential reduce by 104.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 104.1 kB or 56% of the original size.
Potential reduce by 18.3 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. Queenswaypark.com needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 78% of the original size.
Number of requests can be reduced by 16 (44%)
36
20
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Queenswaypark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
queenswaypark.com
404 ms
jquery.min.js
25 ms
flexslider.js
544 ms
style.css
304 ms
jquery.carouFredSel-6.0.4-packed.js
508 ms
jquery.vticker.min.js
304 ms
park.css
417 ms
park-res.css
287 ms
booking.css
383 ms
font-awesome.css
314 ms
jquery.min.js
315 ms
jquery.dd.js
391 ms
jquery.datePicker.js
414 ms
datePicker.css
415 ms
style.css
431 ms
script.js
486 ms
wejs
159 ms
css
24 ms
css
34 ms
analytics.js
17 ms
pattern.jpg
99 ms
logo.png
127 ms
slide2.jpg
304 ms
slide1.jpg
279 ms
slide3.jpg
405 ms
slide4.jpg
506 ms
book-online-now.jpg
196 ms
queensway-park-bengaluru.jpg
279 ms
deluxe-single.jpg
293 ms
deluxe-double.jpg
325 ms
deluxe-suite.jpg
332 ms
conference-room.jpg
390 ms
jazz-restaurant.jpg
405 ms
queensway-park-ad.jpg
426 ms
WidgetEmbed-logoWidget
52 ms
fontawesome-webfont.woff
424 ms
collect
20 ms
cdswidLOGO-v2747565260a.css%20%27%29%3B
1 ms
cdswidgets_m-c-v2102084671a.js
153 ms
cdswidLOGO-v2747565260a.css
156 ms
fontawesome-webfont.ttf
291 ms
badge_64x64_GREEN-14347-2.png
10 ms
slider-control-left.png
100 ms
slider-control-right.png
107 ms
queenswaypark.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
queenswaypark.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
queenswaypark.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 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 Queenswaypark.com 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 Queenswaypark.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.
queenswaypark.com
Open Graph description is not detected on the main page of Queenswaypark. 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: