Tools & Wizards About Us
cureatrt.org screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cureatrt.org

Cure ATRT Now

Page Load Speed

6.6 sec in total

First Response

2.1 sec

Resources Loaded

4.4 sec

Page Rendered

80 ms

cureatrt.org screenshot

About Website

Click here to check amazing Cure ATRT content. Otherwise, check out these important facts you probably never knew about cureatrt.org

Leading the fight against ATRT (atypical teratoid rhabdoid tumors)

Visit cureatrt.org

Key Findings

We analyzed Cureatrt.org page load time and found that the first response time was 2.1 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

cureatrt.org performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

www.cureatrt.org

2077 ms

minified.js

33 ms

focus-within-polyfill.js

79 ms

polyfill.min.js

1319 ms

thunderbolt-commons.1fbb1c52.bundle.min.js

63 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cureatrt.org, 37% (16 requests) were made to Static.parastorage.com and 28% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cureatrt.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 739.5 kB (54%)

Content Size

1.4 MB

After Optimization

625.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Cureatrt.org main page is 1.4 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. 40% of websites need less resources to load. HTML takes 595.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 463.7 kB

  • Original 595.6 kB
  • After minification 594.0 kB
  • After compression 132.0 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 463.7 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 5.4 kB

  • Original 251.8 kB
  • After minification 246.4 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 ATRT images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 270.4 kB

  • Original 517.3 kB
  • After minification 517.3 kB
  • After compression 246.9 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 270.4 kB or 52% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cure ATRT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.cureatrt.org

www.cureatrt.org

2077 ms

minified.js

minified.js

33 ms

focus-within-polyfill.js

focus-within-polyfill.js

79 ms

polyfill.min.js

polyfill.min.js

1319 ms

thunderbolt-commons.1fbb1c52.bundle.min.js

thunderbolt-commons.1fbb1c52.bundle.min.js

63 ms

main.80be598a.bundle.min.js

main.80be598a.bundle.min.js

62 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

62 ms

lodash.min.js

lodash.min.js

68 ms

react.production.min.js

react.production.min.js

65 ms

react-dom.production.min.js

react-dom.production.min.js

66 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

63 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

65 ms

676d25_44059ed3ebb7428fa7d4512dec61d7bf.png

676d25_44059ed3ebb7428fa7d4512dec61d7bf.png

261 ms

676d25_1c5477b5642f4402b453accd1d6b9a24.jpg

676d25_1c5477b5642f4402b453accd1d6b9a24.jpg

589 ms

676d25_a2519af5fb7944d183fed1c8cbc35cd9.jpg

676d25_a2519af5fb7944d183fed1c8cbc35cd9.jpg

500 ms

676d25_bcc3717b51e84524b588776dfe30cebe.png

676d25_bcc3717b51e84524b588776dfe30cebe.png

625 ms

676d25_f072577ee62f4037ad59dd244e0aa833.png

676d25_f072577ee62f4037ad59dd244e0aa833.png

464 ms

676d25_a7c77438c0d0493587f2471b2fb43723.png

676d25_a7c77438c0d0493587f2471b2fb43723.png

525 ms

676d25_d0e73e617bbd4482b95b96e4df130bd6~mv2.png

676d25_d0e73e617bbd4482b95b96e4df130bd6~mv2.png

492 ms

676d25_adb89c336eb746de8d916949fe0dc833.jpg

676d25_adb89c336eb746de8d916949fe0dc833.jpg

814 ms

676d25_a0811703783e4fa0a238f248d6d0321b.jpg

676d25_a0811703783e4fa0a238f248d6d0321b.jpg

694 ms

676d25_18f0e02bd9d7466793f3f9c70d2e8ea5.png

676d25_18f0e02bd9d7466793f3f9c70d2e8ea5.png

811 ms

676d25_f97fbc90386e48f9828ae3283a4a8428.jpg

676d25_f97fbc90386e48f9828ae3283a4a8428.jpg

906 ms

bundle.min.js

bundle.min.js

79 ms

116 ms

123 ms

122 ms

120 ms

120 ms

117 ms

144 ms

150 ms

154 ms

146 ms

151 ms

145 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

26 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

18 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

6 ms

Accessibility Review

cureatrt.org accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

cureatrt.org 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

cureatrt.org SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

cureatrt.org

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