3.8 sec in total
147 ms
2.8 sec
889 ms
Welcome to nfed.org homepage info - get ready to check NFED best content for United States right away, or after learning these important things about nfed.org
We empower and connect those touched by ectodermal dysplasias through education, support and research. Find resources, treatment and people like you.
Visit nfed.orgWe analyzed Nfed.org page load time and found that the first response time was 147 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nfed.org performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value13.6 s
0/100
25%
Value13.2 s
2/100
10%
Value13,140 ms
0/100
30%
Value0.267
46/100
15%
Value20.9 s
2/100
10%
147 ms
358 ms
310 ms
131 ms
166 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 79% of them (58 requests) were addressed to the original Nfed.org, 8% (6 requests) were made to and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nfed.org.
Page size can be reduced by 85.5 kB (10%)
839.4 kB
753.9 kB
In fact, the total size of Nfed.org main page is 839.4 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. 70% of websites need less resources to load. Images take 719.9 kB which makes up the majority of the site volume.
Potential reduce by 77.6 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 77.6 kB or 79% of the original size.
Potential reduce by 7.8 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. NFED images are well optimized though.
Potential reduce by 50 B
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 27 B
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. Nfed.org needs all CSS files to be minified and compressed as it can save up to 27 B or 18% of the original size.
Number of requests can be reduced by 39 (62%)
63
24
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NFED. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
nfed.org
147 ms
nfed.org
358 ms
www.nfed.org
310 ms
js
131 ms
wp-emoji-release.min.js
166 ms
columns.min.css
673 ms
style.min.css
376 ms
autoptimize_single_aad543532afdb3c29f47d43060551f06.css
659 ms
mediaelementplayer-legacy.min.css
681 ms
wp-mediaelement.min.css
373 ms
jquery.fancybox.min.css
369 ms
autoptimize_single_a9c9a62ac1994fe16faab89e7a0140e6.css
378 ms
default.min.css
392 ms
autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css
394 ms
frontend-gtag.min.js
411 ms
jquery.min.js
504 ms
jquery-migrate.min.js
514 ms
jquery.fancybox.min.js
508 ms
underscore.min.js
621 ms
infinite-scroll.pkgd.min.js
609 ms
autoptimize_single_2682de4c62fb93d27044e75cfdf94b6f.js
629 ms
autoptimize_single_8ba2a9fe40de4c394651c7d9dd514385.js
873 ms
meanmenu.min.js
868 ms
doubletaptogo.min.js
871 ms
autoptimize_single_6e7818c95477c9a84c947d478bb9b692.js
869 ms
fonts.css
366 ms
formreset.min.css
868 ms
formsmain.min.css
902 ms
readyclass.min.css
901 ms
browsers.min.css
900 ms
api.min.js
151 ms
comment-reply.min.js
900 ms
regenerator-runtime.min.js
900 ms
wp-polyfill.min.js
899 ms
dom-ready.min.js
957 ms
hooks.min.js
1104 ms
i18n.min.js
954 ms
a11y.min.js
979 ms
jquery.json.min.js
956 ms
gravityforms.min.js
954 ms
js
85 ms
analytics.js
80 ms
collect
45 ms
gtm.js
149 ms
fbevents.js
170 ms
nfed-logo.svg
246 ms
EEC-Guys_transparent-background-e1660236760955.png
466 ms
diagonal-30.svg
366 ms
support-elsa.jpg
399 ms
Boy-hed.jpg
309 ms
XLHED-Clinical-Trial-150x150.png
310 ms
papillomas-leg-goltz-syndrome-150x150.jpeg
560 ms
thank-you-square-150x150.png
533 ms
Nathan-XLHED-300-150x150.jpg
521 ms
smiling-nfed-family-member-221x300.jpg
616 ms
nfed-family-members-221x300.jpg
515 ms
nfed-staff-mary-221x300.jpg
570 ms
Watts-family-laughing-goltz-syndrome-300-300x300.jpg
592 ms
Katherine-watts-car-seat-goltz-syndrome.jpg
618 ms
gavin-kid-syndrome-300-300x300.jpg
805 ms
Jacobi.sebock.hed_.basketball-300x300.jpg
693 ms
Shimchick-Family-300x300.png
806 ms
Adam-viccaro-marathon-medal-hed-300x300.jpg
732 ms
diagonal.svg
761 ms
join-our-family.jpg
618 ms
nfed-mom-daughter.jpg
687 ms
QJsPTuK
27 ms
XZ0EQU3HLqrr6lqzDOk8Efj4uajKFvJA1lbP8OweGeRoIOabtr4CRlRudd56QXko9sfFpmj0mPexmfXu60vLPjr6T6Bd2CO6Y=
27 ms
Ouc9ILyUc2Pi2zh6THvYyPL3da3tnxV1L9BJzWO5Y=
25 ms
w7B4Z5Ggg5pu2vgJGVG513npBeSj2x8WmaPSY97GZ9e7rS8s+OvpPoF3YI7pg==
25 ms
HRU3G0DeShjK2f4fgcE8jQYe03TVwkjKj865z0gvJRzY+LbOHpMe9jI8vd1re2fFXUv0EnNY7lg==
24 ms
Ouc9ILyUc2PinTx6THvYxPL3da3unxV1L9Amw9O4o=
25 ms
251814838646975
85 ms
nfed.org 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
Some elements have a [tabindex] value greater than 0
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
nfed.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
nfed.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nfed.org 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 Nfed.org 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.
nfed.org
Open Graph data is detected on the main page of NFED. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: