6.6 sec in total
412 ms
5.8 sec
363 ms
Welcome to viceroyproperties.in homepage info - get ready to check Viceroy Properties best content right away, or after learning these important things about viceroyproperties.in
Visit viceroyproperties.inWe analyzed Viceroyproperties.in page load time and found that the first response time was 412 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
viceroyproperties.in performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.4 s
0/100
25%
Value13.6 s
2/100
10%
Value1,070 ms
25/100
30%
Value0.002
100/100
15%
Value11.6 s
18/100
10%
412 ms
1063 ms
201 ms
400 ms
800 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 76% of them (47 requests) were addressed to the original Viceroyproperties.in, 15% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Viceroyproperties.in.
Page size can be reduced by 152.4 kB (20%)
757.1 kB
604.7 kB
In fact, the total size of Viceroyproperties.in main page is 757.1 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. 65% of websites need less resources to load. Javascripts take 465.8 kB which makes up the majority of the site volume.
Potential reduce by 145.1 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 145.1 kB or 90% of the original size.
Potential reduce by 2.3 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 4.9 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. Viceroyproperties.in has all CSS files already compressed.
Number of requests can be reduced by 43 (86%)
50
7
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viceroy Properties. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
viceroyproperties.in
412 ms
www.viceroyproperties.in
1063 ms
safe-svg-block-frontend.css
201 ms
styles.css
400 ms
quform.css
800 ms
captcha.min.css
602 ms
css
48 ms
owl.carousel.css
601 ms
sa-owl-theme.css
613 ms
animate.min.css
617 ms
lightgallery.css
623 ms
lightgallery-bundle.min.css
809 ms
pum-site-styles.css
812 ms
choices.min.css
817 ms
style-static.min.css
1243 ms
style.css
831 ms
jquery.min.js
999 ms
jquery-migrate.min.js
1000 ms
captcha.min.js
1000 ms
api.js
60 ms
js
109 ms
et-core-unified-tb-64-26.min.css
1019 ms
et-core-unified-26.min.css
1038 ms
et-core-unified-tb-64-deferred-26.min.css
1197 ms
index.js
1196 ms
index.js
1221 ms
quform.js
1514 ms
scripts.min.js
1598 ms
new-tab.js
1449 ms
owl.carousel.min.js
1449 ms
jquery.mousewheel.min.js
1450 ms
owl.carousel2.thumbs.min.js
1451 ms
lightgallery.min.js
1642 ms
lg-video.min.js
1641 ms
lg-zoom.min.js
1644 ms
lg-autoplay.min.js
1650 ms
player.min.js
1672 ms
core.min.js
1795 ms
pum-site-scripts.js
1802 ms
api.js
77 ms
common.js
1812 ms
wp-polyfill-inert.min.js
1642 ms
regenerator-runtime.min.js
1463 ms
wp-polyfill.min.js
1291 ms
index.js
1402 ms
smush-lazy-load.min.js
1397 ms
css
16 ms
recaptcha__en.js
145 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZFhjQ.ttf
123 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZFhjQ.ttf
139 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZFhjQ.ttf
203 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZFhjQ.ttf
214 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZFhjQ.ttf
212 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZFhjQ.ttf
213 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZFhjQ.ttf
318 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZFhjQ.ttf
237 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZFhjQ.ttf
250 ms
logo.svg
203 ms
icon1.svg
200 ms
icon2.svg
211 ms
icon3.svg
213 ms
icon4.svg
204 ms
viceroyproperties.in 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
viceroyproperties.in 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
viceroyproperties.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Viceroyproperties.in 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 Viceroyproperties.in 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.
viceroyproperties.in
Open Graph description is not detected on the main page of Viceroy Properties. 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: