5.3 sec in total
279 ms
4.7 sec
271 ms
Click here to check amazing Heart India content for India. Otherwise, check out these important facts you probably never knew about heartindia.net
Heart India, Official publication of Heart India Charitable Trust,India
Visit heartindia.netWe analyzed Heartindia.net page load time and found that the first response time was 279 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
heartindia.net performance score
name
value
score
weighting
Value23.3 s
0/100
10%
Value28.4 s
0/100
25%
Value23.6 s
0/100
10%
Value5,470 ms
0/100
30%
Value0
100/100
15%
Value30.1 s
0/100
10%
279 ms
93 ms
148 ms
382 ms
420 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Heartindia.net, 29% (25 requests) were made to Journals.lww.com and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Journals.lww.com.
Page size can be reduced by 1.0 MB (40%)
2.6 MB
1.5 MB
In fact, the total size of Heartindia.net main page is 2.6 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. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 188.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 188.5 kB or 76% of the original size.
Potential reduce by 0 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. Heart India images are well optimized though.
Potential reduce by 770.0 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 770.0 kB or 39% of the original size.
Potential reduce by 54.7 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. Heartindia.net needs all CSS files to be minified and compressed as it can save up to 54.7 kB or 21% of the original size.
Number of requests can be reduced by 60 (83%)
72
12
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Heart India. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
default.aspx
279 ms
launch-31b54f0dec1c.min.js
93 ms
OtAutoBlock.js
148 ms
otSDKStub.js
382 ms
lww-cookiepro.js
420 ms
css
98 ms
corev15.css
551 ms
bootstrap.min.css
570 ms
font-awesome.min.css
103 ms
bootstrap-overwrites.css
602 ms
tachyons.css
603 ms
base-main-header.css
90 ms
lww-core.css
560 ms
ejp.css
578 ms
jqueryui.css
598 ms
journal.css
576 ms
custom.journal.css
128 ms
initstrings.js
549 ms
init.js
415 ms
theming.js
559 ms
ScriptResource.axd
140 ms
blank.js
416 ms
ScriptResource.axd
548 ms
ScriptResource.axd
595 ms
ScriptResource.axd
595 ms
ScriptResource.axd
598 ms
ScriptResource.axd
596 ms
ScriptResource.axd
1133 ms
ScriptResource.axd
1231 ms
ScriptResource.axd
1188 ms
ScriptResource.axd
1189 ms
ScriptResource.axd
1192 ms
jquery.js
1131 ms
bootstrap.bundle.min.js
598 ms
jqueryui.js
1186 ms
lww-core.js
1191 ms
journal-navigation.min.js
1193 ms
journals_master.min.js
1196 ms
manifest.js
1192 ms
ejp.js
1199 ms
react-redux-vendors.js
1196 ms
client.js
117 ms
moatheader.js
94 ms
WebResource.axd
1190 ms
alerts-subscription.min.js
1195 ms
ImageWrapperControl.js
1224 ms
ArticleNavigator.js
1218 ms
ListContainerControlBase.js
1219 ms
fulltext.js
1218 ms
ArticleDisplayControl.js
1226 ms
ScriptResource.axd
1196 ms
js
1197 ms
WebResource.axd
1197 ms
UserToolbarDropdown.js
1222 ms
EmailToColleague.js
1222 ms
ExportToCitationManager.js
1222 ms
gpt.js
118 ms
ads.js
1221 ms
ee.js
1222 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
120 ms
7537629c-faa0-40ce-a837-f7b14c0d4e70.json
845 ms
location
1091 ms
ejp-print.css
581 ms
favicon.png
674 ms
spcommon.png
671 ms
XLargeThumb.01774853-202311030-00000.CV.jpeg
668 ms
DisplayControlArticleImageSize.01774853-202311030-00002.T1.jpeg
766 ms
DisplayControlArticleImageSize.01774853-202311030-00011.F1.jpeg
763 ms
DisplayControlArticleImageSize.01774853-202311030-00012.F1.jpeg
763 ms
va9B4kDNxMZdWfMOD5VnLK3eRhf_Xl7Glw.ttf
193 ms
va9B4kDNxMZdWfMOD5VnSKzeRhf_Xl7Glw.ttf
330 ms
va9B4kDNxMZdWfMOD5VnZKveRhf_Xl7Glw.ttf
375 ms
va9E4kDNxMZdWfMOD5Vvl4jOazX3dA.ttf
332 ms
va9B4kDNxMZdWfMOD5VnPKreRhf_Xl7Glw.ttf
334 ms
CAPrivacyPolicy.png
97 ms
wk-brand-white.svg
36 ms
bg-header.png
38 ms
menu-down.gif
135 ms
wk-icons.woff
124 ms
print-toc-current.css
170 ms
va9f4kDNxMZdWfMOD5VvkrA6Qif4VFzklULW.ttf
132 ms
va9C4kDNxMZdWfMOD5VvkrjJYTfVdlTO.ttf
134 ms
va9f4kDNxMZdWfMOD5VvkrBiQyf4VFzklULW.ttf
131 ms
va9f4kDNxMZdWfMOD5VvkrAWRSf4VFzklULW.ttf
131 ms
va9f4kDNxMZdWfMOD5VvkrByRCf4VFzklULW.ttf
132 ms
fontawesome-webfont.woff
223 ms
fontawesome-webfont.woff
51 ms
heartindia.net 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
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
heartindia.net 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
heartindia.net 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 Heartindia.net 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 Heartindia.net 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.
heartindia.net
Open Graph description is not detected on the main page of Heart India. 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: