2 sec in total
61 ms
1.3 sec
597 ms
Visit retinoblastoma.com now to see the best up-to-date Retinoblastoma content and also check out these interesting facts you probably never knew about retinoblastoma.com
Find the latest information on retinoblastoma, and learn how Memorial Sloan Kettering doctors can help.
Visit retinoblastoma.comWe analyzed Retinoblastoma.com page load time and found that the first response time was 61 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
retinoblastoma.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value5.8 s
15/100
25%
Value8.0 s
22/100
10%
Value2,020 ms
7/100
30%
Value0.146
77/100
15%
Value20.6 s
2/100
10%
61 ms
151 ms
98 ms
76 ms
40 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Retinoblastoma.com, 32% (21 requests) were made to Mskcc.org and 9% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (372 ms) relates to the external source Siteimproveanalytics.com.
Page size can be reduced by 166.7 kB (31%)
541.9 kB
375.2 kB
In fact, the total size of Retinoblastoma.com main page is 541.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 231.8 kB which makes up the majority of the site volume.
Potential reduce by 165.4 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 165.4 kB or 71% of the original size.
Potential reduce by 0 B
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. Retinoblastoma images are well optimized though.
Potential reduce by 1.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 259 B
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. Retinoblastoma.com has all CSS files already compressed.
Number of requests can be reduced by 38 (75%)
51
13
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Retinoblastoma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
retinoblastoma.com
61 ms
retinoblastoma
151 ms
gtm.js
98 ms
css_XjnWWuBqln5QlWm8JyVsfaDEnUOPeVFuDn3-SLE62p0.css
76 ms
CoveoFullSearch.min.css
40 ms
css_BGhD1bKRvzNfUmP-vQVoii9HG_Br6oLwcoRnDS_mids.css
39 ms
css_5aOhJwwuGK_dblaLkL-w3AJwgNPlfUtvCzwsDh7J5Gk.css
54 ms
js__SuP8TILI-MeJ6GEDD66gFprrBSFZ02krAfbCOxYsU8.js
77 ms
CoveoJsSearch.Lazy.min.js
78 ms
js_0JQF_seVO10jMuuhCn1Vvq63gu76ezIwMIEL0eunrck.js
77 ms
js_kTnIsBnCm1FKvmucVHjgprnx3zKE0ZwpWn4Q0JTa2XU.js
81 ms
index.min.js
91 ms
js_UNB-gABpuFMB9fhpX95ywDLOPtF-liJmM32FafCiqVQ.js
81 ms
css
95 ms
search-insights.min.js
124 ms
kids_signature_accent_blue.svg
56 ms
retinoblastoma.jpg
55 ms
3x1.svg
52 ms
optimize.js
159 ms
analytics.js
168 ms
bat.js
231 ms
gtm.js
163 ms
gtm.js
291 ms
iframe_api
229 ms
109638412.js
249 ms
GothamSSm-Medium_Web-5e842534.woff
95 ms
GothamSSm-Book_Web-2e34e089.woff
95 ms
GothamSSm-Light_Web-74932b54.woff
95 ms
GothamSSm-Bold_Web-30a3dcee.woff
94 ms
ChronicleSSm-Book_Web-379b2e7c.woff
96 ms
ChronicleSSm-Medium_Web-b8572aae.woff
95 ms
ChronicleSSm-Light_Web-e7351697.woff
207 ms
ChronicleSSm-Bold_Web-feaf2e64.woff
207 ms
MSKBrownWeb-Black-a6a8759f.woff
199 ms
linkid.js
69 ms
publisher:getClientId
233 ms
conversion_async.js
221 ms
activity;xsp=4705862
172 ms
wrapper.js
164 ms
siteanalyze_510.js
372 ms
tv2track.js
214 ms
activityi;src=4385263;type=Pages0;cat=msk_n0;ord=7524744716357;gtm=2wg9q0;auiddc=1713874641.1664457376;u4=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma;~oref=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma
193 ms
activityi;src=10189743;type=hiaction;cat=pagev00;ord=1;num=2417069571838;gtm=2wg9q0;auiddc=1713874641.1664457376;u1=null;~oref=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma
203 ms
www-widgetapi.js
126 ms
cnv
91 ms
js
105 ms
js
104 ms
ppt=11439;g=page_view_high_intent;gid=33208;ord=9509609777014.703;v=120;ip=54.90.89.239;cuidchk=1
283 ms
ppt=11439;g=page_view_general;gid=33209;ord=5480968351475.895;v=120;ip=54.90.89.239;cuidchk=1
242 ms
src=4385263;type=Pages0;cat=msk_n0;ord=7524744716357;gtm=2wg9q0;auiddc=1713874641.1664457376;u4=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma;~oref=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma
180 ms
collect
168 ms
src=10189743;type=hiaction;cat=pagev00;ord=1;num=2417069571838;gtm=2wg9q0;auiddc=1713874641.1664457376;u1=null;~oref=https%3A%2F%2Fwww.mskcc.org%2Fpediatrics%2Fcancer-care%2Ftypes%2Fretinoblastoma
175 ms
38 ms
tv2track.php
31 ms
generic
28 ms
74 ms
generic
9 ms
receive
22 ms
image.aspx
11 ms
40 ms
nr-1216.min.js
44 ms
iFrame.html
25 ms
collect
25 ms
collect
26 ms
NRJS-065615310a3f12eada6
63 ms
retinoblastoma.com 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
retinoblastoma.com 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
Missing source maps for large first-party JavaScript
retinoblastoma.com SEO score
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 Retinoblastoma.com 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 Retinoblastoma.com 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.
retinoblastoma.com
Open Graph data is detected on the main page of Retinoblastoma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: