3.4 sec in total
1.2 sec
2.1 sec
180 ms
Click here to check amazing Cure Angelman content. Otherwise, check out these important facts you probably never knew about cureangelman.ca
Learning that your loved one has Angelman syndrome can be scary and overwhelming, but hope is here. FAST’s sole mission is to cure Angelman syndrome and, with our partners around the world, we are get...
Visit cureangelman.caWe analyzed Cureangelman.ca page load time and found that the first response time was 1.2 sec 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.
cureangelman.ca performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value13.7 s
0/100
25%
Value35.4 s
0/100
10%
Value8,370 ms
0/100
30%
Value0
100/100
15%
Value17.8 s
4/100
10%
1159 ms
83 ms
278 ms
93 ms
26 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 94% of them (29 requests) were addressed to the original Cureangelman.ca, 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cureangelman.ca.
Page size can be reduced by 525.4 kB (25%)
2.1 MB
1.5 MB
In fact, the total size of Cureangelman.ca main page is 2.1 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. Only 10% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 13.2 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 3.8 kB, which is 22% 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 13.2 kB or 77% of the original size.
Potential reduce by 76.3 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. Cure Angelman images are well optimized though.
Potential reduce by 118.6 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 118.6 kB or 71% of the original size.
Potential reduce by 317.4 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. Cureangelman.ca needs all CSS files to be minified and compressed as it can save up to 317.4 kB or 68% of the original size.
Number of requests can be reduced by 12 (43%)
28
16
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cure Angelman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cureangelman.ca
1159 ms
wp-emoji-release.min.js
83 ms
6cdbaaff_ai1ec_parsed_css.css
278 ms
style.css
93 ms
css
26 ms
css
40 ms
editor-style.css
57 ms
style_base.css
78 ms
theme-responsive.css
100 ms
nivo-slider.css
108 ms
jquery.js
233 ms
jquery-migrate.min.js
123 ms
custom.js
142 ms
lightbox.js
167 ms
jquery.nivo.slider.js
195 ms
hook-custom-script.js
169 ms
close.png
55 ms
loading.gif
59 ms
prev.png
55 ms
next.png
52 ms
FASTsite-coverphotoCanada02.jpg
211 ms
OVIDtemp2cover.jpg
344 ms
FASTsite-coverphotoCanada03.jpg
296 ms
main-header-bg.png
103 ms
FASTsite-workphoto-Naama.jpg
218 ms
zoom-icon.png
111 ms
footer-title-bg.png
153 ms
icon_quote.png
438 ms
footer-menu-separator.png
206 ms
slide-nav.png
136 ms
slide-pager.png
140 ms
cureangelman.ca 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.
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
cureangelman.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cureangelman.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Cureangelman.ca 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 Cureangelman.ca 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.
cureangelman.ca
Open Graph description is not detected on the main page of Cure Angelman. 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: