11.7 sec in total
327 ms
10.7 sec
746 ms
Welcome to empiresquare.in homepage info - get ready to check Empire Square best content right away, or after learning these important things about empiresquare.in
Build an impressive website with the best-rated top-seller WordPress theme
Visit empiresquare.inWe analyzed Empiresquare.in page load time and found that the first response time was 327 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
empiresquare.in performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value13.5 s
0/100
25%
Value9.8 s
10/100
10%
Value1,360 ms
17/100
30%
Value0
100/100
15%
Value11.3 s
19/100
10%
327 ms
1139 ms
84 ms
789 ms
2194 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Empiresquare.in, 91% (58 requests) were made to Dpgvclkvnnsee.cloudfront.net and 2% (1 request) were made to Anarock-digital.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Dpgvclkvnnsee.cloudfront.net.
Page size can be reduced by 714.3 kB (16%)
4.5 MB
3.8 MB
In fact, the total size of Empiresquare.in main page is 4.5 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. 45% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 101.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 101.1 kB or 82% of the original size.
Potential reduce by 543.2 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. Obviously, Empire Square needs image optimization as it can save up to 543.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 66.8 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 66.8 kB or 28% of the original size.
Potential reduce by 3.2 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. Empiresquare.in has all CSS files already compressed.
Number of requests can be reduced by 15 (26%)
58
43
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Empire Square. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
empiresquare.in
327 ms
embed.js
1139 ms
gtm.js
84 ms
jquery.min.js
789 ms
plugins.js
2194 ms
app88a6.js
1575 ms
style_v12.css
1580 ms
mobile-desktop.css
802 ms
bootstrap.min.css
1995 ms
font-awesome.min.css
41 ms
jquery.fancybox.min-v1.js
802 ms
intlTelInput.js
1778 ms
jquery.validate.js
1822 ms
form_validation.js
2365 ms
form.css
2348 ms
intlTelInput.css
2783 ms
jquery.fancybox.min.css
2739 ms
submit.js
778 ms
NjhiMGIwZWItOWUxNy00YjJlLTgwZWMtNGQwYjIwZjJmNTc4
27 ms
logo.png
772 ms
phone.png
771 ms
desktopv2.jpg
876 ms
element.png
871 ms
apt.png
1252 ms
doorway.png
1300 ms
configurationjan22.jpg
1526 ms
1.png
1514 ms
2.png
1645 ms
3.png
1669 ms
4.png
2009 ms
5.png
2072 ms
6.png
2276 ms
7.png
2301 ms
8.png
2418 ms
9.png
2434 ms
10.png
2798 ms
11.png
2836 ms
backresi.jpg
3090 ms
gallery_img.jpg
3064 ms
gallery_img2.jpg
3175 ms
gallery_img3.jpg
3214 ms
gallery_img4.jpg
3570 ms
gallery_img5.jpg
3599 ms
gallery_img6.jpg
3851 ms
gallery_img7.jpg
3863 ms
gallery_img8.jpg
3948 ms
gallery_img10.jpg
3985 ms
flp_1.png
4348 ms
flp_2.png
4367 ms
flp_3.png
4617 ms
flp_4.png
4645 ms
devinne%20txt%20bt.ttf
4638 ms
PLAYFAIRDISPLAY-REGULAR.ttf
3872 ms
opensans-regular.ttf
4286 ms
flp_5.png
4571 ms
expert.png
4419 ms
visit.png
4653 ms
brochure.png
4543 ms
map.png
4638 ms
qrcode.jpg
4275 ms
mail.png
4616 ms
thanksyou.jpg
4416 ms
flags.png
4649 ms
utils.js
759 ms
empiresquare.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
empiresquare.in 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
empiresquare.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Empiresquare.in 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 Empiresquare.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.
empiresquare.in
Open Graph description is not detected on the main page of Empire Square. 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: