2.5 sec in total
154 ms
2 sec
298 ms
Click here to check amazing Cfri content for United States. Otherwise, check out these important facts you probably never knew about cfri.org
Nonprofit organization funding innovative research and offering education, advocacy and psychosocial support to the cystic fibrosis community.
Visit cfri.orgWe analyzed Cfri.org page load time and found that the first response time was 154 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cfri.org performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value38.3 s
0/100
25%
Value35.6 s
0/100
10%
Value14,340 ms
0/100
30%
Value0.028
100/100
15%
Value38.8 s
0/100
10%
154 ms
194 ms
130 ms
322 ms
151 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Cfri.org, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cfri.org.
Page size can be reduced by 262.4 kB (12%)
2.2 MB
2.0 MB
In fact, the total size of Cfri.org main page is 2.2 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. 20% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 16.1 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 16.1 kB or 72% of the original size.
Potential reduce by 185.7 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. Cfri images are well optimized though.
Potential reduce by 59.4 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 59.4 kB or 55% of the original size.
Potential reduce by 1.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. Cfri.org needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 71% of the original size.
We found no issues to fix!
32
32
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cfri. According to our analytics all requests are already optimized.
cfri.org
154 ms
home.shtml
194 ms
mainTest.css
130 ms
jquery.js
322 ms
jquery.cross-slide.min.js
151 ms
ga.js
4 ms
signUpButton_415.gif
66 ms
CFRI_Home.jpg
199 ms
donateButton_415.gif
130 ms
enEspanolButton_415.gif
131 ms
research.jpg
397 ms
masquerade.png
488 ms
hotairballoon.JPG
716 ms
CF%20Community%20Voices%20Logo%20Option%203.jpg
647 ms
sunset.JPG
320 ms
stone-pyramid.png
644 ms
tree.JPG
462 ms
2014summernewsletter.JPG
653 ms
Breathe.jpg
782 ms
charitynavigator4starscfri.jpg
617 ms
greatnonprofits.png
809 ms
Facebook_square_icon.jpg
839 ms
YouTube_logo_square.png
855 ms
PayPal_Donate_Button.jpg
844 ms
footerInformation.jpg
908 ms
__utm.gif
11 ms
mainHeader.jpg
775 ms
mainNavBkgdFade.jpg
739 ms
homeBoxBkgdFade.jpg
767 ms
footerBarBkgdFade.jpg
773 ms
CFRI.Home.jpg
894 ms
bannerresearch.jpg
1076 ms
bannereducation.jpg
1114 ms
bannersupport.jpg
1199 ms
cfri.org 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
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
cfri.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
cfri.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
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 Cfri.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 Cfri.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.
cfri.org
Open Graph description is not detected on the main page of Cfri. 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: