4.4 sec in total
148 ms
3.8 sec
402 ms
Welcome to aajicare.in homepage info - get ready to check Aaji Care best content right away, or after learning these important things about aajicare.in
You can rest assured that your elderly family will receive the best senior citizen care center. We provide services ranging from dementia care to assisted living.
Visit aajicare.inWe analyzed Aajicare.in page load time and found that the first response time was 148 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aajicare.in performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value8.2 s
2/100
25%
Value18.7 s
0/100
10%
Value3,700 ms
1/100
30%
Value0.001
100/100
15%
Value27.3 s
0/100
10%
148 ms
667 ms
215 ms
225 ms
233 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 65% of them (74 requests) were addressed to the original Aajicare.in, 24% (27 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Aajicare.in.
Page size can be reduced by 218.6 kB (8%)
2.9 MB
2.7 MB
In fact, the total size of Aajicare.in main page is 2.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 100.8 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 100.8 kB or 79% of the original size.
Potential reduce by 4.3 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. Aaji Care images are well optimized though.
Potential reduce by 76.4 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 76.4 kB or 19% of the original size.
Potential reduce by 37.1 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. Aajicare.in needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 18% of the original size.
Number of requests can be reduced by 67 (85%)
79
12
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aaji Care. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
aajicare.in
148 ms
aajicare.in
667 ms
thegem-pagespeed-lazy-items.js
215 ms
layerslider.css
225 ms
thegem-preloader.css
233 ms
thegem-reset.css
228 ms
thegem-grid.css
236 ms
thegem-header.css
217 ms
style.css
422 ms
thegem-widgets.css
428 ms
thegem-new-css.css
433 ms
thegem-perevazka-css.css
432 ms
css
42 ms
custom-LpMiUNIR.css
435 ms
jquery.fancybox.min.css
452 ms
style.min.css
627 ms
styles.css
801 ms
wphindi-frontend.css
634 ms
elementor-icons.min.css
632 ms
frontend-legacy.min.css
622 ms
frontend-lite.min.css
712 ms
post-5.css
821 ms
post-24720.css
843 ms
modern.css
841 ms
css
39 ms
fontawesome.min.css
851 ms
solid.min.css
925 ms
jquery.min.js
1001 ms
jquery-migrate.min.js
1012 ms
js
67 ms
email-decode.min.js
841 ms
css
35 ms
thegem-button.css
1083 ms
thegem-lazy-loading-animations.css
1082 ms
odometer-theme-default.css
1082 ms
thegem-counter.css
1157 ms
animations.min.css
1311 ms
rs6.css
1111 ms
app.js
1330 ms
thegem-form-elements.js
1330 ms
jquery.easing.js
1329 ms
SmoothScroll.js
1328 ms
jquery.dlmenu.js
1282 ms
thegem-menu_init.js
1360 ms
thegem-header.js
1269 ms
functions.js
1355 ms
jquery.mousewheel.pack.js
1350 ms
jquery.fancybox.min.js
1348 ms
jquery.fancybox-init.js
1278 ms
index.js
1267 ms
index.js
1234 ms
rbtools.min.js
1315 ms
rs6.min.js
1325 ms
thegem-lazyLoading.js
1314 ms
odometer.js
1199 ms
thegem-counters.js
1274 ms
isotope.min.js
1286 ms
webpack.runtime.min.js
1325 ms
frontend-modules.min.js
1255 ms
waypoints.min.js
1175 ms
core.min.js
1201 ms
frontend.min.js
1279 ms
gtm.js
72 ms
gtm.js
98 ms
logo_c0a3a0f1c19d70198fca4fbda8bfe15e_1x.jpg
1270 ms
logo_9a44ee5e55b6c62c6658b32d0130dab0_1x.png
1269 ms
dummy.png
1269 ms
preloader-1.gif
1239 ms
js
83 ms
analytics.js
77 ms
pxiEyp8kv8JHgFVrFJM.woff
165 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
224 ms
pxiByp8kv8JHgFVrLDz8V1g.woff
321 ms
pxiByp8kv8JHgFVrLFj_V1g.woff
322 ms
pxiGyp8kv8JHgFVrLPTedA.woff
319 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
322 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
321 ms
pxiByp8kv8JHgFVrLDD4V1g.woff
321 ms
pxiByp8kv8JHgFVrLBT5V1g.woff
470 ms
thegem-socials.woff
1198 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
393 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
393 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
393 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
472 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
472 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
473 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
473 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
474 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
475 ms
thegem-icons.woff
1241 ms
js
206 ms
Prasad-pldbmblwqojsyh22azyxl1kypfhe17vd3l8957mr1s.jpg
1204 ms
d74e6d68-8557-4b39-9272-bb45842534cf.js
732 ms
fbevents.js
389 ms
collect
207 ms
aarambh--scaled-pl66is8ulctk9fkyzcavwdrczzz613mdjuu9xffcfs.jpg
1036 ms
pt-care3-1-piplp6i7dxk0bbi9cy1uqnodmcr5t83aogzmv4z7aw.jpg
1224 ms
20210403_113345-1-scaled-pl66k62ankprcrklwfu42j6shf5md245epf0d3dha0.jpg
1265 ms
pic-1.png
1170 ms
pxiGyp8kv8JHgFVrJJLedA.woff
258 ms
pxiDyp8kv8JHgFVrJJLmg1hlEw.woff
258 ms
pxiDyp8kv8JHgFVrJJLm21llEw.woff
256 ms
pxiDyp8kv8JHgFVrJJLmv1plEw.woff
258 ms
pxiAyp8kv8JHgFVrJJLmE3tG.woff
258 ms
pxiDyp8kv8JHgFVrJJLmr19lEw.woff
260 ms
pxiDyp8kv8JHgFVrJJLmy15lEw.woff
259 ms
pxiDyp8kv8JHgFVrJJLm111lEw.woff
260 ms
pxiDyp8kv8JHgFVrJJLm81xlEw.woff
261 ms
fa-solid-900.woff
1330 ms
eicons.woff
1062 ms
icons-material.css
453 ms
icons-material.css
626 ms
materialdesignicons.woff
202 ms
aajicare.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.
aajicare.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
aajicare.in 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
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 Aajicare.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 Aajicare.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.
aajicare.in
Open Graph data is detected on the main page of Aaji Care. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: