7.1 sec in total
1.1 sec
5.8 sec
249 ms
Click here to check amazing IAMD content. Otherwise, check out these important facts you probably never knew about iamd.in
IAMD - Indian Association of Muscular Dystrophy
Visit iamd.inWe analyzed Iamd.in page load time and found that the first response time was 1.1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
iamd.in performance score
name
value
score
weighting
Value14.0 s
0/100
10%
Value20.3 s
0/100
25%
Value20.3 s
0/100
10%
Value760 ms
38/100
30%
Value0.652
9/100
15%
Value19.7 s
2/100
10%
1118 ms
155 ms
304 ms
156 ms
165 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 49% of them (41 requests) were addressed to the original Iamd.in, 26% (22 requests) were made to Static.xx.fbcdn.net and 23% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Facebook.com.
Page size can be reduced by 158.1 kB (32%)
498.3 kB
340.2 kB
In fact, the total size of Iamd.in main page is 498.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 320.0 kB which makes up the majority of the site volume.
Potential reduce by 20.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 20.4 kB or 79% of the original size.
Potential reduce by 24.6 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. IAMD images are well optimized though.
Potential reduce by 75.9 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 75.9 kB or 71% of the original size.
Potential reduce by 37.2 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. Iamd.in needs all CSS files to be minified and compressed as it can save up to 37.2 kB or 83% of the original size.
Number of requests can be reduced by 43 (52%)
83
40
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IAMD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
iamd.in
1118 ms
modstyle.css
155 ms
mootools.js
304 ms
caption.js
156 ms
slideshow.js
165 ms
rokmoomenu.css
165 ms
template_css.css
297 ms
template_colors.php
392 ms
colorchooser.css
313 ms
mooRainbow.css
315 ms
rokslidestrip.css
317 ms
rokzoom.css
449 ms
rokslidestrip.js
453 ms
rokzoom.js
457 ms
rokie6warn.js
476 ms
rokmoomenu.js
478 ms
mootools.bgiframe.js
552 ms
overlay-abstract.png
304 ms
blank.gif
153 ms
logo.png
155 ms
fb.png
157 ms
blogger.png
154 ms
content-shadow-l.png
156 ms
content-shadow-r.png
304 ms
side-shadow-l.png
305 ms
side-shadow-r.png
305 ms
horiz-menu-bg.png
305 ms
horiz-menu-active.png
378 ms
maincol-bg-bottom.png
453 ms
maincol-bg.png
454 ms
path-arrow.png
455 ms
module-bottom-bg.png
456 ms
module-h3.png
466 ms
comment.png
531 ms
help.gif
603 ms
likebox.php
2554 ms
McLpmVM3wCm.css
168 ms
VH4VPudaxfN.css
210 ms
Czh0gDTFcBt.css
252 ms
hhn-1r1gAPt.css
327 ms
X97l7PURgJ9.css
335 ms
q68gy-v_YMF.js
334 ms
FJmpeSpHpjS.js
370 ms
0wM5s1Khldu.js
289 ms
1bNoFZUdlYZ.js
291 ms
njO1TPvGzoR.js
369 ms
1QuX41zDRrx.js
368 ms
Oagsvfb4VWi.js
404 ms
LTv6ZK-5zxz.js
484 ms
1FCa-btixu2.js
408 ms
11234818_885444928193230_2616311963400014120_n.jpg
285 ms
safe_image.php
347 ms
1379797_749688261768898_1652619464342660411_n.jpg
313 ms
10354686_10150004552801856_220367501106153455_n.jpg
355 ms
12310620_140573659642348_1115156800127911407_n.jpg
463 ms
12631389_676473345828774_2783277999959948515_n.jpg
437 ms
12717203_1024726764261405_4605743228904395487_n.jpg
422 ms
11896096_985235978206925_891951698203372588_n.jpg
448 ms
11069295_1384211495234402_1214021218514751183_n.jpg
424 ms
11990651_1513854248922642_6234302658563623648_n.jpg
466 ms
12800126_963570873736502_7205878525443371674_n.jpg
462 ms
12799259_1718504011765645_5556707716207296126_n.jpg
497 ms
12219495_118153078549799_3386653668008861866_n.jpg
538 ms
12814767_1705201456430207_8149017766675842280_n.jpg
521 ms
12791126_1009637955773926_6892462810768358693_n.jpg
697 ms
12669681_995858430485212_4598309009939804261_n.jpg
572 ms
12644644_995858520485203_3021756795815859194_n.jpg
578 ms
12661957_995858453818543_8207853480287341009_n.jpg
594 ms
12662628_995858383818550_5910297706412197457_n.jpg
596 ms
12540906_984843674920021_7499967140540648690_n.jpg
650 ms
wL6VQj7Ab77.png
92 ms
s7jcwEQH7Sx.png
93 ms
QDwYpIaRyfG.png
94 ms
bNvHN6v1NeH.png
94 ms
t-wz8gw1xG1.png
91 ms
K00K-UgnsKu.png
92 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
78 ms
blank.png
174 ms
zoom-shadow1.png
154 ms
zoom-shadow3.png
155 ms
zoom-shadow4.png
156 ms
zoom-shadow6.png
161 ms
zoom-shadow8.png
158 ms
iamd.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.
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
Links do not have a discernible name
iamd.in 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
Browser errors were logged to the console
iamd.in 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iamd.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iamd.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.
iamd.in
Open Graph description is not detected on the main page of IAMD. 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: