Tools & Wizards About Us
cureangelman.ca screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

cureangelman.ca

FAST (Foundation for Angelman Syndrome Therapeutics) in Canada

Page Load Speed

688 ms in total

First Response

53 ms

Resources Loaded

505 ms

Page Rendered

130 ms

cureangelman.ca screenshot

About Website

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.ca

Key Findings

We analyzed Cureangelman.ca page load time and found that the first response time was 53 ms and then it took 635 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

cureangelman.ca performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

www.cureangelman.ca

53 ms

hiq6yuq.css

127 ms

style.min.css

18 ms

theme.min.css

44 ms

header-footer.min.css

67 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 66% of them (40 requests) were addressed to the original Cureangelman.ca, 21% (13 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (165 ms) belongs to the original domain Cureangelman.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.0 kB (32%)

Content Size

467.2 kB

After Optimization

316.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Cureangelman.ca main page is 467.2 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. 60% of websites need less resources to load. Javascripts take 266.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.9 kB

  • Original 60.3 kB
  • After minification 58.7 kB
  • After compression 11.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. 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 48.9 kB or 81% of the original size.

JavaScript Optimization

-38%

Potential reduce by 101.2 kB

  • Original 266.6 kB
  • After minification 266.6 kB
  • After compression 165.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 101.2 kB or 38% of the original size.

CSS Optimization

-1%

Potential reduce by 915 B

  • Original 140.3 kB
  • After minification 140.2 kB
  • After compression 139.3 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (93%)

Requests Now

44

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 44 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 21 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.cureangelman.ca

www.cureangelman.ca

53 ms

hiq6yuq.css

hiq6yuq.css

127 ms

style.min.css

style.min.css

18 ms

theme.min.css

theme.min.css

44 ms

header-footer.min.css

header-footer.min.css

67 ms

elementor-icons.min.css

elementor-icons.min.css

31 ms

frontend.min.css

frontend.min.css

34 ms

swiper.min.css

swiper.min.css

44 ms

post-562.css

post-562.css

42 ms

frontend.min.css

frontend.min.css

49 ms

global.css

global.css

69 ms

post-564.css

post-564.css

73 ms

post-581.css

post-581.css

71 ms

post-687.css

post-687.css

74 ms

css

css

81 ms

fontawesome.min.css

fontawesome.min.css

75 ms

solid.min.css

solid.min.css

80 ms

email-decode.min.js

email-decode.min.js

71 ms

icofont.min.css

icofont.min.css

85 ms

font-awesome.min.css

font-awesome.min.css

82 ms

sina-widgets.min.css

sina-widgets.min.css

80 ms

animations.min.css

animations.min.css

83 ms

e-gallery.min.css

e-gallery.min.css

82 ms

jquery.min.js

jquery.min.js

85 ms

jquery-migrate.min.js

jquery-migrate.min.js

86 ms

jquery.sticky.min.js

jquery.sticky.min.js

89 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

92 ms

e-gallery.min.js

e-gallery.min.js

93 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

91 ms

webpack.runtime.min.js

webpack.runtime.min.js

97 ms

frontend-modules.min.js

frontend-modules.min.js

102 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

105 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

106 ms

wp-polyfill.min.js

wp-polyfill.min.js

107 ms

hooks.min.js

hooks.min.js

117 ms

i18n.min.js

i18n.min.js

113 ms

frontend.min.js

frontend.min.js

115 ms

waypoints.min.js

waypoints.min.js

125 ms

core.min.js

core.min.js

125 ms

frontend.min.js

frontend.min.js

110 ms

elements-handlers.min.js

elements-handlers.min.js

107 ms

FAST-CA.svg

FAST-CA.svg

165 ms

scc-c2.min.js

scc-c2.min.js

23 ms

tti.min.js

tti.min.js

16 ms

p.css

p.css

16 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

24 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

30 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

36 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

43 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

45 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

44 ms

d

d

6 ms

d

d

14 ms

d

d

14 ms

rnCs-xNNww_2s0amA9uCt23BafM.ttf

rnCs-xNNww_2s0amA9uCt23BafM.ttf

46 ms

rnCs-xNNww_2s0amA9uetG3BafM.ttf

rnCs-xNNww_2s0amA9uetG3BafM.ttf

45 ms

rnCs-xNNww_2s0amA9vmtm3BafM.ttf

rnCs-xNNww_2s0amA9vmtm3BafM.ttf

44 ms

rnCs-xNNww_2s0amA9vKsW3BafM.ttf

rnCs-xNNww_2s0amA9vKsW3BafM.ttf

50 ms

rnCr-xNNww_2s0amA9M5kn0.ttf

rnCr-xNNww_2s0amA9M5kn0.ttf

51 ms

rnCs-xNNww_2s0amA9uSsG3BafM.ttf

rnCs-xNNww_2s0amA9uSsG3BafM.ttf

52 ms

rnCs-xNNww_2s0amA9v2s23BafM.ttf

rnCs-xNNww_2s0amA9v2s23BafM.ttf

118 ms

Accessibility Review

cureangelman.ca accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

cureangelman.ca best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

cureangelman.ca SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

cureangelman.ca

Open Graph data is detected on the main page of Cure Angelman. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: