2.7 sec in total
218 ms
2.3 sec
199 ms
Welcome to ovarian.org homepage info - get ready to check Ovarian best content for United States right away, or after learning these important things about ovarian.org
NOCC leads the fight against ovarian cancer in the US. We support survivors and caregivers, raise awareness and fund research to find a cure.
Visit ovarian.orgWe analyzed Ovarian.org page load time and found that the first response time was 218 ms and then it took 2.5 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.
ovarian.org performance score
name
value
score
weighting
Value17.3 s
0/100
10%
Value43.2 s
0/100
25%
Value31.1 s
0/100
10%
Value2,750 ms
3/100
30%
Value0.056
98/100
15%
Value45.2 s
0/100
10%
218 ms
11 ms
262 ms
140 ms
135 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 51% of them (57 requests) were addressed to the original Ovarian.org, 13% (15 requests) were made to Js-bbapp-www.2dialog.com and 6% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Secure3.2dialog.com.
Page size can be reduced by 1.3 MB (67%)
2.0 MB
655.5 kB
In fact, the total size of Ovarian.org main page is 2.0 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 30.5 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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.5 kB or 81% of the original size.
Potential reduce by 23.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. Ovarian images are well optimized though.
Potential reduce by 901.2 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 901.2 kB or 77% of the original size.
Potential reduce by 378.8 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. Ovarian.org needs all CSS files to be minified and compressed as it can save up to 378.8 kB or 84% of the original size.
Number of requests can be reduced by 69 (69%)
100
31
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ovarian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
ovarian.org
218 ms
jquery.min.js
11 ms
foundation.css
262 ms
app.css
140 ms
style.css
135 ms
mq860.css
134 ms
ipad.css
138 ms
smartphones.css
140 ms
mq767.css
207 ms
modernizr.foundation.js
208 ms
reset.css
203 ms
main.css
332 ms
css
27 ms
abd.js
49 ms
jquery.js
686 ms
jquery.foundation.mediaQueryToggle.js
274 ms
jquery.foundation.forms.js
395 ms
jquery.event.move.js
277 ms
jquery.event.swipe.js
326 ms
jquery.foundation.reveal.js
417 ms
jquery.foundation.orbit.js
396 ms
jquery.foundation.navigation.js
416 ms
jquery.foundation.buttons.js
416 ms
jquery.foundation.tabs.js
417 ms
jquery.foundation.tooltips.js
433 ms
jquery.foundation.accordion.js
468 ms
jquery.placeholder.js
468 ms
jquery.foundation.alerts.js
468 ms
jquery.foundation.topbar.js
486 ms
jquery.foundation.joyride.js
506 ms
jquery.foundation.clearing.js
554 ms
jquery.foundation.magellan.js
576 ms
app.js
553 ms
all-script.js
577 ms
gtm.js
66 ms
logo_resize.jpg
234 ms
banner_tea2.jpg
393 ms
90per.png
383 ms
take_aerly_action.png
383 ms
take_aerly_action_Learn_More.png
382 ms
social_icons.png
385 ms
banner_white_arrow.png
393 ms
110216-Homepage-BG-stars.jpg
393 ms
110216-Homepage-view-our-profile.jpg
393 ms
110216-Homepage-4-stars.jpg
393 ms
TakeAction-Not-Chances.png
397 ms
banner-brca.png
426 ms
feature-img3.jpg
428 ms
footer-logo.png
428 ms
social-f.jpg
427 ms
social-t.jpg
426 ms
social-y.jpg
460 ms
social-p.jpg
470 ms
social-i.jpg
438 ms
4star-logo.gif
440 ms
Een8_qoaFF8
82 ms
footer-img1.png
434 ms
AvenirNextLTW01-Medium.ttf
551 ms
Avenir-Next-LT-W01-Demi.ttf
541 ms
footer-img2.png
477 ms
footer-img3.png
483 ms
analytics.js
11 ms
conversion_async.js
29 ms
collect
20 ms
33 ms
51 ms
collect
90 ms
collect
113 ms
www-embed-player-vfl8xM8me.css
44 ms
www-embed-player.js
79 ms
base.js
110 ms
68 ms
48 ms
ga-audiences
102 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
66 ms
ad_status.js
101 ms
1
1025 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
48 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
print.css
75 ms
prototype.js
72 ms
scriptaculous.js
82 ms
jquery-1.2.6.min.js
89 ms
window.js
91 ms
custom_alert.js
101 ms
reportHelper.js
89 ms
TwodialogDate.js
101 ms
utils.js
106 ms
formval.js
91 ms
clean.css
43 ms
forms.css
45 ms
lightbox2.css
47 ms
builder.js
9 ms
effects.js
9 ms
dragdrop.js
14 ms
controls.js
19 ms
slider.js
20 ms
sound.js
22 ms
gtm.js
56 ms
839
77 ms
analytics.js
27 ms
conversion_async.js
51 ms
collect
15 ms
collect
15 ms
collect
12 ms
collect
21 ms
14 ms
18 ms
ga-audiences
17 ms
17 ms
22 ms
__utm.gif
3 ms
ovarian.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
ovarian.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
Missing source maps for large first-party JavaScript
ovarian.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ovarian.org 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 Ovarian.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.
ovarian.org
Open Graph description is not detected on the main page of Ovarian. 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: