22.9 sec in total
691 ms
22.1 sec
137 ms
Click here to check amazing Aarogyasri content for India. Otherwise, check out these important facts you probably never knew about aarogyasri.gov.in
Visit aarogyasri.gov.inWe analyzed Aarogyasri.gov.in page load time and found that the first response time was 691 ms and then it took 22.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
aarogyasri.gov.in performance score
691 ms
3375 ms
1699 ms
427 ms
432 ms
Our browser made a total of 258 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Aarogyasri.gov.in, 100% (257 requests) were made to Aarogyasri.telangana.gov.in. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Aarogyasri.telangana.gov.in.
Page size can be reduced by 3.9 MB (72%)
5.4 MB
1.5 MB
In fact, the total size of Aarogyasri.gov.in main page is 5.4 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. 35% of websites need less resources to load. Javascripts take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 71.4 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 71.4 kB or 77% of the original size.
Potential reduce by 89.9 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. Aarogyasri images are well optimized though.
Potential reduce by 2.9 MB
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 2.9 MB or 88% of the original size.
Potential reduce by 851.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. Aarogyasri.gov.in needs all CSS files to be minified and compressed as it can save up to 851.3 kB or 84% of the original size.
Number of requests can be reduced by 236 (93%)
254
18
The browser has sent 254 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aarogyasri. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 120 to 1 for JavaScripts and from 102 to 1 for CSS and as a result speed up the page load time.
aarogyasri.gov.in
691 ms
www.aarogyasri.telangana.gov.in
3375 ms
aui.css
1699 ms
main.css
427 ms
main.css
432 ms
main.css
651 ms
main.css
443 ms
main.css
639 ms
aui.js
3724 ms
aui-base-html5-shiv.js
665 ms
browser_selectors.js
1103 ms
modules.js
1122 ms
aui_sandbox.js
885 ms
arraylist-add.js
1103 ms
arraylist-filter.js
1107 ms
arraylist.js
1565 ms
array-extras.js
1584 ms
array-invoke.js
1328 ms
attribute-base.js
1593 ms
attribute-complex.js
1549 ms
attribute-core.js
2253 ms
attribute-observable.js
2028 ms
attribute-extras.js
2063 ms
base-base.js
2065 ms
base-pluginhost.js
1905 ms
classnamemanager.js
2117 ms
datatype-xml-format.js
2241 ms
datatype-xml-parse.js
2285 ms
dom-base.js
2749 ms
dom-core.js
2576 ms
dom-screen.js
2705 ms
dom-style.js
2729 ms
event-base.js
2986 ms
event-custom-base.js
3635 ms
event-custom-complex.js
3131 ms
event-delegate.js
3209 ms
event-focus.js
3435 ms
main.css
2790 ms
aui_deprecated.css
3347 ms
portal_1.css
2995 ms
portal_2.css
2801 ms
taglib_1.css
3010 ms
taglib_2.css
2997 ms
accessibility.css
2782 ms
event-hover.js
2970 ms
event-key.js
3056 ms
event-mouseenter.js
3034 ms
event-mousewheel.js
2771 ms
event-outside.js
3087 ms
event-resize.js
2662 ms
event-simulate.js
2765 ms
event-synthetic.js
2999 ms
intl.js
2868 ms
io-base.js
3246 ms
io-form.js
2932 ms
io-queue.js
2732 ms
io-upload-iframe.js
2755 ms
io-xdr.js
2851 ms
json-parse.js
2716 ms
json-stringify.js
2997 ms
node-base.js
3043 ms
node-core.js
3253 ms
node-event-delegate.js
2955 ms
node-event-simulate.js
2741 ms
node-focusmanager.js
2882 ms
node-pluginhost.js
2863 ms
node-screen.js
2950 ms
node-style.js
2516 ms
oop.js
2668 ms
plugin.js
2762 ms
pluginhost-base.js
2783 ms
add_content.css
2619 ms
asset_category_selector.css
2382 ms
asset_column.css
2476 ms
auto_row.css
2387 ms
device_preview.css
2641 ms
edit_layout.css
2469 ms
flyout.css
2532 ms
forms.css
2494 ms
generic_portal.css
2731 ms
generic_portlet.css
2418 ms
header_row.css
2466 ms
javascript_template.css
2422 ms
notifications.css
2297 ms
openid.css
2329 ms
page_settings.css
2316 ms
panel_component.css
2240 ms
panel_page.css
2176 ms
pagination.css
2087 ms
panel_pagination.css
2066 ms
portlet_css_editor.css
2094 ms
portlet_item.css
1963 ms
position_helper.css
1984 ms
preview.css
2258 ms
rich_editor.css
1953 ms
search_combobox.css
1799 ms
separator.css
1711 ms
tag_selector.css
1681 ms
toolbar.css
1660 ms
translation_manager.css
1583 ms
tree.css
1622 ms
undo_manager.css
1584 ms
uploader.css
1852 ms
app_view_common.css
1739 ms
app_view_entry.css
1501 ms
app_view_navigation_item.css
1496 ms
app_view_search_entry.css
1427 ms
app_view_toolbar.css
1424 ms
asset_categories_summary.css
1528 ms
asset_links.css
1509 ms
button.css
1502 ms
calendar.css
1493 ms
captcha.css
1462 ms
categorization_filter.css
1455 ms
ddm_template.css
1469 ms
diff.css
1453 ms
diff_html.css
1430 ms
discussion.css
1694 ms
flags.css
1436 ms
form_navigator.css
1408 ms
header.css
1449 ms
icon.css
1446 ms
icon_help.css
1432 ms
icon_list.css
1454 ms
icon_menu.css
1468 ms
input_localized.css
1473 ms
input_move_boxes.css
1456 ms
input_repeat.css
1454 ms
language.css
1528 ms
logo_selector.css
1458 ms
navbar.css
1427 ms
preview.css
1440 ms
ratings.css
1438 ms
rss_settings.css
1434 ms
search_container.css
1420 ms
search_iterator.css
1451 ms
search_toggle.css
1435 ms
sites_directory.css
1435 ms
social_activities.css
1319 ms
social_bookmarks.css
1312 ms
tags_summary.css
1377 ms
trash_common.css
1373 ms
user_display.css
1345 ms
webdav.css
1382 ms
workflow_status.css
1318 ms
pluginhost-config.js
1554 ms
querystring-stringify-simple.js
1375 ms
queue-promote.js
1371 ms
selector-css2.js
1611 ms
selector-css3.js
1632 ms
selector-native.js
1574 ms
selector.js
1393 ms
widget-base.js
1708 ms
widget-htmlparser.js
1686 ms
widget-skin.js
1469 ms
widget-uievents.js
1790 ms
yui-throttle.js
1552 ms
aui-base-core.js
1809 ms
aui-base-lang.js
1744 ms
aui-classnamemanager.js
1599 ms
aui-component.js
1876 ms
aui-debounce.js
1595 ms
aui-delayed-task-deprecated.js
2002 ms
aui-event-base.js
2029 ms
aui-event-input.js
1942 ms
aui-form-validator.js
1944 ms
aui-node-base.js
1952 ms
aui-node-html5.js
2036 ms
aui-selector.js
2266 ms
aui-timer.js
2297 ms
dependency.js
1943 ms
events.js
1938 ms
language.js
1943 ms
liferay.js
2252 ms
util.js
2515 ms
portal.js
2330 ms
portlet.js
2249 ms
portlet_sharing.js
2122 ms
workflow.js
2147 ms
form.js
2470 ms
form_placeholders.js
2476 ms
icon.js
2223 ms
menu.js
2437 ms
notice.js
2345 ms
poller.js
2477 ms
jquery-1.9.1.min.js
2817 ms
bootstrap.min.js
2647 ms
bootbox.js
2540 ms
main.js
2284 ms
main.js
2565 ms
base.css
241 ms
application.css
486 ms
layout.css
454 ms
dockbar.css
710 ms
navigation.css
545 ms
portlet.css
934 ms
extras.css
942 ms
custom.css
929 ms
custom_common.css
435 ms
common.css
425 ms
dark.css
219 ms
light.css
216 ms
custom_responsive.css
446 ms
bigfontA.png
483 ms
normalA.png
431 ms
smallfontA.png
423 ms
screen%20readW.png
434 ms
printW.png
215 ms
bookmarkW.png
442 ms
signinW.png
679 ms
ban_tgg.png
1095 ms
search.png
897 ms
animated-new.png
917 ms
882842de-8929-4f35-9c5d-17b500f34a7d
905 ms
fc81f424-b45a-4f60-a4d0-a8665ad23520
1465 ms
3f915510-3bb8-447d-b9d8-a7099c0ae09b
2196 ms
c20fea47-374e-4d7f-b8f1-0432e078e70b
2437 ms
99f457d9-188e-4365-b179-4178b65f04c9
1597 ms
d6658f39-4e27-4f02-b0f3-0ed9dbc71ee0
1593 ms
6cf6ff77-6b0c-46c8-b86d-95b12c14b870
1538 ms
67bfd3f6-814a-43e0-952b-e1832eeca346
1960 ms
fa85a6a1-2e6c-4354-97bf-bb05a782f2a2
1805 ms
51c164b8-815e-45f3-8184-4d018d62cd40
1889 ms
4b48f81a-aa8b-4b45-8c5e-d6e2cd104dfe
1899 ms
289ffa55-98b5-4498-bdbe-3f3a009f295d
2070 ms
ce0260ad-df7d-4104-9564-d37827ca1728
2172 ms
e23d7541-b274-475f-bc34-d2b8cb289271
2209 ms
NeedHelp3.png
2880 ms
fb_ico_act.gif
2530 ms
t_ico_act.gif
2644 ms
national%20emblem.png
2867 ms
menuhoverbg.jpg
2672 ms
fontawesome-alloy.woff
3957 ms
loading.gif
4162 ms
8ca770cf-ccf2-48a0-b391-ba6b8bf8dd8b
2886 ms
11f4391d-8d48-457d-82a0-6e643b180093
2912 ms
arrow_white.png
3274 ms
widget-base.css
3031 ms
widget-stack.css
3091 ms
color-base.js
443 ms
base-core.js
518 ms
base-observable.js
563 ms
base-build.js
726 ms
widget-position.js
884 ms
widget-stack.js
998 ms
widget-position-align.js
1037 ms
widget-position-constrain.js
1189 ms
widget-stdmod.js
1584 ms
aui-widget-cssclass.js
1374 ms
aui-widget-toggle.js
1218 ms
aui-overlay-base-deprecated.js
1254 ms
async-queue.js
1660 ms
aui-parse-content.js
1703 ms
querystring-stringify.js
1729 ms
aui-io-request.js
1744 ms
aui-overlay-mask-deprecated.js
1839 ms
aui-loading-mask-deprecated.js
2281 ms
aui-io-plugin-deprecated.js
2123 ms
aarogyasri.gov.in SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aarogyasri.gov.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 Aarogyasri.gov.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.
aarogyasri.gov.in
Open Graph description is not detected on the main page of Aarogyasri. 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: