2.7 sec in total
464 ms
2 sec
296 ms
Visit run4parkinson.org now to see the best up-to-date Run 4 Parkinson content and also check out these interesting facts you probably never knew about run4parkinson.org
Run for Parkinson's Global Event for Parkinson's Community - Corre por el Parkinson, Evento Global de la comunidad de Parkinson - Corri per il Parkinson, evento mondiale
Visit run4parkinson.orgWe analyzed Run4parkinson.org page load time and found that the first response time was 464 ms 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 40% of websites can load faster.
run4parkinson.org performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value4.8 s
31/100
25%
Value7.3 s
29/100
10%
Value1,910 ms
8/100
30%
Value0.037
100/100
15%
Value15.7 s
6/100
10%
464 ms
191 ms
205 ms
213 ms
216 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 75% of them (42 requests) were addressed to the original Run4parkinson.org, 5% (3 requests) were made to Platform.twitter.com and 5% (3 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (619 ms) belongs to the original domain Run4parkinson.org.
Page size can be reduced by 942.8 kB (52%)
1.8 MB
868.1 kB
In fact, the total size of Run4parkinson.org main page is 1.8 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. 65% of websites need less resources to load. CSS take 617.5 kB which makes up the majority of the site volume.
Potential reduce by 19.9 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.6 kB, which is 14% 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 19.9 kB or 79% of the original size.
Potential reduce by 6.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. Run 4 Parkinson images are well optimized though.
Potential reduce by 392.3 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 392.3 kB or 66% of the original size.
Potential reduce by 524.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. Run4parkinson.org needs all CSS files to be minified and compressed as it can save up to 524.3 kB or 85% of the original size.
Number of requests can be reduced by 34 (63%)
54
20
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run 4 Parkinson. 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 15 to 1 for CSS and as a result speed up the page load time.
464 ms
template.css
191 ms
bootstrap.min.css
205 ms
bootstrap-responsive.css
213 ms
font-awesome.css
216 ms
favsocial.css
216 ms
template.css
223 ms
favslider.css
285 ms
mootools-core.js
310 ms
core.js
333 ms
behaviour.js
334 ms
silverlight.js
332 ms
wmvplayer.js
335 ms
ac_quicktime.js
381 ms
jwplayer.js
419 ms
jquery.min.js
519 ms
jquery-noconflict.js
413 ms
jquery-migrate.min.js
418 ms
caption.js
446 ms
bootstrap.min.js
475 ms
jquery.flexslider.js
516 ms
jquery.mousewheel.js
520 ms
font-awesome.css
520 ms
k2style.css
557 ms
joomla.css
570 ms
template.css
618 ms
style1.css
617 ms
css
25 ms
css
35 ms
backtop.js
619 ms
AC_QuickTime.js
248 ms
ga.js
17 ms
wood_pattern.png
244 ms
1.jpg
233 ms
2.jpg
244 ms
3.jpg
232 ms
4.jpg
338 ms
5.jpg
243 ms
6.jpg
293 ms
7.jpg
335 ms
8.jpg
337 ms
9.jpg
437 ms
R4PSignatureSmall.jpg
338 ms
widgets.js
176 ms
__utm.gif
17 ms
wPffs8CXY8I
84 ms
B36lestIh5g
180 ms
e3gR3k4hjRc
190 ms
fontawesome-webfont.woff
422 ms
fontawesome-webfont.woff
461 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
44 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
54 ms
ad_status.js
47 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
144 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
48 ms
run4parkinson.org 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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
run4parkinson.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
run4parkinson.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Run4parkinson.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 Run4parkinson.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.
run4parkinson.org
Open Graph description is not detected on the main page of Run 4 Parkinson. 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: