8.4 sec in total
840 ms
5.8 sec
1.7 sec
Welcome to swastikproperties.in homepage info - get ready to check Swastik Properties best content right away, or after learning these important things about swastikproperties.in
Visit swastikproperties.inWe analyzed Swastikproperties.in page load time and found that the first response time was 840 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
swastikproperties.in performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value18.5 s
0/100
25%
Value17.2 s
0/100
10%
Value450 ms
63/100
30%
Value0.001
100/100
15%
Value18.7 s
3/100
10%
840 ms
45 ms
242 ms
142 ms
945 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 75% of them (52 requests) were addressed to the original Swastikproperties.in, 20% (14 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 (3.6 sec) belongs to the original domain Swastikproperties.in.
Page size can be reduced by 1.2 MB (48%)
2.5 MB
1.3 MB
In fact, the total size of Swastikproperties.in main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 35.5 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 35.5 kB or 80% of the original size.
Potential reduce by 17 B
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. Swastik Properties images are well optimized though.
Potential reduce by 760.5 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 760.5 kB or 74% of the original size.
Potential reduce by 418.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. Swastikproperties.in needs all CSS files to be minified and compressed as it can save up to 418.3 kB or 85% of the original size.
Number of requests can be reduced by 37 (71%)
52
15
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Swastik 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 23 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
swastikproperties.in
840 ms
css
45 ms
layerslider.css
242 ms
css
142 ms
styles.css
945 ms
bdc-layout-stylesheet.css
417 ms
style.css
423 ms
stylesheet.min.css
817 ms
style_dynamic.php
1456 ms
font-awesome.min.css
442 ms
style.min.css
625 ms
responsive.min.css
641 ms
style_dynamic_responsive.php
1745 ms
js_composer_front.css
911 ms
custom_css.php
1895 ms
mac_stylesheet.css
1032 ms
webkit_stylesheet.css
1035 ms
jquery.js
1518 ms
jquery-migrate.min.js
1248 ms
layerslider.kreaturamedia.jquery.js
1240 ms
greensock.js
1446 ms
layerslider.transitions.js
1460 ms
scripts.js
1658 ms
qode-like.js
1668 ms
plugins.js
2659 ms
jquery.carouFredSel-6.2.1.js
1732 ms
lemmon-slider.js
2629 ms
jquery.mousewheel.min.js
2656 ms
jquery.touchSwipe.min.js
2657 ms
isotope.pkgd.min.js
2646 ms
default_dynamic.php
3551 ms
default.min.js
2646 ms
custom_js.php
3552 ms
SmoothScroll.js
2646 ms
js
148 ms
ajax.min.js
2647 ms
js_composer_front.js
2641 ms
wp-embed.min.js
2631 ms
bdwp_cf7.js
2679 ms
wp-emoji-release.min.js
2587 ms
close_side_menu.png
356 ms
logo-swastik-home.png
354 ms
logo-swastik-white.png
575 ms
bg8.png
577 ms
Home_Page_Banner23.jpg
1211 ms
Design2-600x600.jpg
575 ms
Design21-600x600.jpg
1210 ms
Design20-600x600.jpg
1190 ms
Design13-600x600.jpg
1197 ms
Design18-600x600.jpg
1195 ms
Samar-300-x-225.jpg
1370 ms
about-bg-2.png
1395 ms
KFOmCnqEu92Fr1Mu7GxM.woff
23 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
24 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
26 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
25 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
24 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
23 ms
ElegantIcons.woff
613 ms
fontawesome-webfont.woff
616 ms
logo.png
221 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoqF2mg.woff
30 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-PgFoqF2mg.woff
130 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-BQCoqF2mg.woff
110 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0CoqF2mg.woff
107 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJPkqs.woff
106 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuxJPkqs.woff
84 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvBJPkqs.woff
108 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJPkqs.woff
107 ms
swastikproperties.in accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
swastikproperties.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
Page has valid source maps
swastikproperties.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
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 Swastikproperties.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 Swastikproperties.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.
swastikproperties.in
Open Graph description is not detected on the main page of Swastik 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: