4.3 sec in total
541 ms
3.2 sec
543 ms
Visit fdna.health now to see the best up-to-date FDNA content for United States and also check out these interesting facts you probably never knew about fdna.health
FDNA Health provides AI technology and services enabling early diagnosis and helping undiagnosed patients and their families.
Visit fdna.healthWe analyzed Fdna.health page load time and found that the first response time was 541 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fdna.health performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value14.1 s
0/100
25%
Value8.2 s
20/100
10%
Value2,450 ms
5/100
30%
Value0.279
43/100
15%
Value17.4 s
4/100
10%
541 ms
59 ms
83 ms
463 ms
521 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 75% of them (74 requests) were addressed to the original Fdna.health, 9% (9 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fdna.health.
Page size can be reduced by 419.5 kB (28%)
1.5 MB
1.1 MB
In fact, the total size of Fdna.health main page is 1.5 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. 70% of websites need less resources to load. Images take 979.0 kB which makes up the majority of the site volume.
Potential reduce by 75.9 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 75.9 kB or 79% of the original size.
Potential reduce by 320.1 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. Obviously, FDNA needs image optimization as it can save up to 320.1 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.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. Fdna.health has all CSS files already compressed.
Number of requests can be reduced by 55 (63%)
87
32
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FDNA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
fdna.health
541 ms
gtm.js
59 ms
optimize.js
83 ms
style.min.css
463 ms
unslider.css
521 ms
slider.css
516 ms
public.css
482 ms
style.css
481 ms
jquery.min.js
545 ms
jquery-migrate.min.js
567 ms
unslider.min.js
595 ms
jquery.event.move.js
580 ms
jquery.event.swipe.js
618 ms
advanced.min.js
624 ms
conditions.min.js
650 ms
index.js
718 ms
js
55 ms
js
111 ms
bootstrap.min.css
769 ms
style.min.css
834 ms
swiper.css
766 ms
dark.css
775 ms
font-icons.css
795 ms
animate.css
846 ms
magnific-popup.css
819 ms
photographer.css
845 ms
radio-checkbox.css
849 ms
glyphicon.css
896 ms
datepicker.css
920 ms
jquery.dataTables.min.css
929 ms
custom.css
939 ms
60352ac84a2f8c0001e02334.js
24 ms
8850865.js
49 ms
stripe-handler-ng.js
824 ms
base.min.js
893 ms
layer.js
952 ms
sticky.js
1014 ms
advanced-ads-pro.min.js
1014 ms
tracking.min.js
1014 ms
delayed.min.js
1013 ms
jquery.js
1064 ms
plugins.carousel.js
1078 ms
plugins.toggles.js
1076 ms
plugins.easing.js
729 ms
plugins.bootstrap.js
744 ms
plugins.fitvids.js
711 ms
plugins.animations.js
783 ms
plugins.tabs.js
795 ms
jquery.validate.min.js
754 ms
datepicker.js
739 ms
plugins.counter.js
719 ms
jquery.dataTables.min.js
790 ms
functions.js
790 ms
analytics.js
118 ms
js
65 ms
js
64 ms
collect
20 ms
collect
38 ms
ga-audiences
37 ms
css2
28 ms
NOVO-LOGO-FDNA-Health.png
422 ms
NOVO-LOGO-FDNA-Health_vertical.png
454 ms
Logo_Charite.svg_.png
455 ms
logo-emory-footer.png
453 ms
tufts-logo-square-e1544208256249.png
532 ms
1200px-The_Hospital_for_Sick_Children_Logo.svg_.png
536 ms
Boston_Childrens_Hospital_logo.svg_.png
573 ms
mountsinai-og-logo.jpg
570 ms
CSG_CW_MCW_CMYK-2020-02.jpg
649 ms
cheo-logo-blk.jpg
593 ms
Childrens-Hospital-of-Philadelphia.jpg
669 ms
Childrens-Logo1.gif
673 ms
CHLA_Butterfly_Logo_No_Tagline_highres.jpg
766 ms
group-8.png
671 ms
Depositphotos_400104572_xl-2015-scaled.jpg
899 ms
Depositphotos_195713676_xl-2015-scaled.jpg
1216 ms
Depositphotos_137214120_xl-2015-scaled.jpg
844 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf
123 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf
141 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf
193 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf
244 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNig.ttf
226 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf
191 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNig.ttf
192 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNig.ttf
192 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNig.ttf
227 ms
morgan-1.jpg
1112 ms
font-icons.woff
1002 ms
time-icon-1.png
723 ms
star-icon-1.png
802 ms
talk-icon-1.png
932 ms
NOVO-LOGO-FDNA-Health_white.png
868 ms
fbevents.js
107 ms
fdna_background-pic-new3.png
1469 ms
background-sec3.png
910 ms
background-puz.png
1024 ms
pling
107 ms
conf.json
20 ms
print.css
100 ms
fdna.health 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fdna.health 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
fdna.health 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fdna.health 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 Fdna.health 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.
fdna.health
Open Graph data is detected on the main page of FDNA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: