1.7 sec in total
168 ms
1.2 sec
351 ms
Welcome to statdx.com homepage info - get ready to check STATdx best content for United States right away, or after learning these important things about statdx.com
STATdx is used to analyze a complex or unusual case, examine a diagnosis in an unfamiliar subspecialty area, teach trainees, and support tumor boards.
Visit statdx.comWe analyzed Statdx.com page load time and found that the first response time was 168 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
statdx.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value7.0 s
6/100
25%
Value4.6 s
70/100
10%
Value620 ms
48/100
30%
Value0.039
100/100
15%
Value11.9 s
16/100
10%
168 ms
191 ms
223 ms
155 ms
25 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 57% of them (28 requests) were addressed to the original Statdx.com, 8% (4 requests) were made to Api.mixpanel.com and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (328 ms) belongs to the original domain Statdx.com.
Page size can be reduced by 262.4 kB (21%)
1.3 MB
1.0 MB
In fact, the total size of Statdx.com main page is 1.3 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. 50% of websites need less resources to load. Images take 869.2 kB which makes up the majority of the site volume.
Potential reduce by 28.8 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 28.8 kB or 70% of the original size.
Potential reduce by 12.6 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. STATdx images are well optimized though.
Potential reduce by 147.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 147.9 kB or 62% of the original size.
Potential reduce by 73.0 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. Statdx.com needs all CSS files to be minified and compressed as it can save up to 73.0 kB or 64% of the original size.
Number of requests can be reduced by 26 (59%)
44
18
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STATdx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
statdx.com
168 ms
wp-emoji-release.min.js
191 ms
dashicons.min.css
223 ms
thickbox.css
155 ms
css
25 ms
style.css
213 ms
css
38 ms
jquery.js
328 ms
jquery-migrate.min.js
190 ms
jquery.scrollTo.min.js
194 ms
jquery.placeholder-1.0.1.js
232 ms
jquery.easing.1.3.js
252 ms
waypoints.min.js
232 ms
thickbox.js
235 ms
navigation.js
240 ms
effect.min.js
250 ms
custom.js
249 ms
wp-embed.min.js
287 ms
jquery.json.js
290 ms
gravityforms.min.js
280 ms
style.css
139 ms
mixpanel-2.0.min.js
12 ms
j.php
10 ms
image-logo-gray.png
167 ms
copy-image-home.jpg
170 ms
skinny-banner-3.jpg
171 ms
non-small-cell-lung-cancer-new.png
265 ms
logo-elsevier.svg
166 ms
logo-relx.svg
164 ms
gtm.js
167 ms
gtm.js
167 ms
bg-bottom-content.jpg
161 ms
image-search-new.png
256 ms
ga.js
121 ms
loadingAnimation.gif
98 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
89 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
91 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
92 ms
71 ms
69 ms
67 ms
65 ms
v.gif
63 ms
conversion_async.js
43 ms
fbevents.js
63 ms
275 ms
24 ms
35 ms
gtm.js
32 ms
statdx.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
statdx.com 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
statdx.com 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
Image elements do not have [alt] attributes
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 Statdx.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 Statdx.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.
statdx.com
Open Graph description is not detected on the main page of STATdx. 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: