14.8 sec in total
4.9 sec
9.7 sec
193 ms
Welcome to inaheart.or.id homepage info - get ready to check Inaheart best content for Indonesia right away, or after learning these important things about inaheart.or.id
Yayasan Jantung Indonesia Home
Visit inaheart.or.idWe analyzed Inaheart.or.id page load time and found that the first response time was 4.9 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
inaheart.or.id performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value7.4 s
4/100
25%
Value9.6 s
11/100
10%
Value350 ms
74/100
30%
Value0.132
81/100
15%
Value7.9 s
44/100
10%
4863 ms
26 ms
38 ms
3127 ms
1559 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 31% of them (22 requests) were addressed to the original Inaheart.or.id, 17% (12 requests) were made to Pbs.twimg.com and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Inaheart.or.id.
Page size can be reduced by 1.4 MB (59%)
2.4 MB
975.5 kB
In fact, the total size of Inaheart.or.id main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 174.2 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 174.2 kB or 79% of the original size.
Potential reduce by 16.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. Inaheart images are well optimized though.
Potential reduce by 832.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 832.5 kB or 69% of the original size.
Potential reduce by 370.4 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. Inaheart.or.id needs all CSS files to be minified and compressed as it can save up to 370.4 kB or 86% of the original size.
Number of requests can be reduced by 29 (44%)
66
37
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inaheart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
inaheart.or.id
4863 ms
css
26 ms
css
38 ms
72b51f7f4deaa7d81564b87149428bb5.css
3127 ms
settings.css
1559 ms
dynamic-captions.css
537 ms
static-captions.css
540 ms
9adf8acb9cc387e23e05ea16492b4492.js
2682 ms
jquery.min.js
7 ms
jquery.themepunch.tools.min.js
1888 ms
jquery.themepunch.revolution.min.js
2151 ms
addthis_widget.js
11 ms
header_box.gif
376 ms
2595-WHF-World-Heart-Day-Web-Banner-ART.jpg
1618 ms
Slider1300x250_home.jpg
822 ms
Slider1300x250_hipertensi.jpg
374 ms
banner210x120_KJS1.jpg
374 ms
banner210x120_GRFW1.jpg
717 ms
banner210x120_KJS2.jpg
757 ms
banner210x120_KJS3.jpg
756 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
82 ms
fontawesome-webfont.woff
592 ms
fontawesome-webfont.woff
960 ms
widgets.js
7 ms
ga.js
92 ms
300lo.json
137 ms
loader.gif
559 ms
large_left.png
577 ms
large_right.png
575 ms
likebox.php
221 ms
sh.8e5f85691f9aaa082472a194.html
143 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
142 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
140 ms
__utm.gif
86 ms
custom-messages.13f2fa2c8d98ff03ac2a.js
78 ms
layers.e5ea973510bf60b3db41.js
77 ms
kyEKgjk51ZE.css
356 ms
xgj7bXhJNEH.css
395 ms
q68gy-v_YMF.js
559 ms
FJmpeSpHpjS.js
637 ms
0wM5s1Khldu.js
579 ms
1bNoFZUdlYZ.js
578 ms
syndication
301 ms
460068238236213248
394 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en-gb.html
226 ms
Lakukan_7_Hal_Sederhana_Berikut_Agar_Jantung_Tetap_Sehat.jpg
1140 ms
proxy.jpg
261 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
9 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
22 ms
logo-YJI-kecil_normal.jpg
240 ms
Mv4fgDci_normal.jpg
234 ms
iJEJzyj5_normal.jpg
236 ms
CagNr3sVAAASQGU.jpg:small
320 ms
CZI4vQcUsAEobLf.jpg:small
305 ms
CYqpzFVUoAAGFda.jpg:small
233 ms
CXYnwygU0AA4LWF.jpg:small
233 ms
CXXWLstUwAArbbh.jpg:small
376 ms
CVl7sgWUAAArGNb.jpg:small
306 ms
CVMGnQZVEAEq4cs.jpg:small
307 ms
CaQ1ZZvUEAAUTtZ.jpg:small
333 ms
CaQ1ZZoUYAAHKu8.jpg:small
579 ms
1507099_10152803737700306_3630001927473137011_n.jpg
226 ms
246549_10151208558855306_1097788299_n.jpg
267 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
77 ms
295.e5ddf1d08150c78558eb.js
10 ms
392.c8c9f7f8f3e1e225bf2e.js
15 ms
jot.html
4 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
81 ms
inaheart.or.id accessibility score
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
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
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
inaheart.or.id 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
inaheart.or.id SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inaheart.or.id can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Inaheart.or.id 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.
inaheart.or.id
Open Graph description is not detected on the main page of Inaheart. 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: