4.2 sec in total
318 ms
3.6 sec
241 ms
Visit psp.org now to see the best up-to-date Psp content for Germany and also check out these interesting facts you probably never knew about psp.org
CurePSP's mission is to increase awareness, educate, and find a cure for Progressive Supranuclear Palsy (PSP) and related neurodegenerative diseases.
Visit psp.orgWe analyzed Psp.org page load time and found that the first response time was 318 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
psp.org performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.1 s
0/100
25%
Value7.1 s
31/100
10%
Value220 ms
87/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
318 ms
979 ms
14 ms
7 ms
23 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Psp.org, 46% (31 requests) were made to Cdn.firespring.com and 28% (19 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.firespring.com.
Page size can be reduced by 506.9 kB (48%)
1.1 MB
552.9 kB
In fact, the total size of Psp.org main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 433.4 kB which makes up the majority of the site volume.
Potential reduce by 53.3 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 16.2 kB, which is 25% 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 53.3 kB or 81% of the original size.
Potential reduce by 10.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. Psp images are well optimized though.
Potential reduce by 234.6 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 234.6 kB or 54% of the original size.
Potential reduce by 208.7 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. Psp.org needs all CSS files to be minified and compressed as it can save up to 208.7 kB or 82% of the original size.
Number of requests can be reduced by 29 (56%)
52
23
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Psp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
psp.org
318 ms
www.psp.org
979 ms
core.1458334902.css
14 ms
stylesheet.css
7 ms
jquery-1.10.2.min.js
23 ms
jquery-migrate-1.2.1.min.js
9 ms
modernizr-2.5.3.js
8 ms
element.js
1436 ms
jquery.cycle.all.min.js
7 ms
site.js
7 ms
jquery.dropdownPlain.js
20 ms
core.1458334902.js
1442 ms
bg_body.gif
12 ms
CurePSP_logo.jpg
12 ms
f9f737fa-b473-4329-a533-47cea3f12482.png
132 ms
f24e6e25-2dbd-4790-9459-57c5a5bc6fe1.jpg
859 ms
985c2c8b-7a9b-4e3f-b0c0-491ec57f5c61.jpg
132 ms
26da4b03-643a-47c3-ae67-3cf22efba737.jpg
130 ms
dad65b4a-ccb3-4390-9a7d-311fbab8b926.png
128 ms
583b4a03-e834-4527-ad49-ca0702f93d8d.jpg
132 ms
mailinglist.jpg
128 ms
adaa4e49-d20f-407a-8260-e5772c6dc41c.jpg
195 ms
e64483d1-da92-456c-9ea9-710ec07944df.png
289 ms
eadd3ea9-9f66-4a44-8042-6f88bf4dc260.jpg
276 ms
99e6d802-5af8-416f-a03d-bd8ff78919bc.jpg
295 ms
93306963-3250-4675-aef3-2a4d8e7c8b4e.jpg
380 ms
ac271736-4b67-4a81-81dd-7ae66969a9eb.png
422 ms
88bc8932-0d12-4024-a571-e5d350cff2a2.jpg
369 ms
translateelement.css
52 ms
main.js
120 ms
embed.js
103 ms
bg_custutil.jpg
225 ms
bg_nav.jpg
229 ms
bg_footer.jpg
228 ms
bg_givenow.jpg
178 ms
dad65b4a-ccb3-4390-9a7d-311fbab8b926.png
163 ms
26da4b03-643a-47c3-ae67-3cf22efba737.jpg
235 ms
f9f737fa-b473-4329-a533-47cea3f12482.png
146 ms
985c2c8b-7a9b-4e3f-b0c0-491ec57f5c61.jpg
179 ms
583b4a03-e834-4527-ad49-ca0702f93d8d.jpg
144 ms
js
254 ms
ga.js
37 ms
element_main.js
69 ms
spotnav_h.png
140 ms
spotnav.png
142 ms
swiftype_nocode-d8273559be65c04593eb2a85dc0df637.js
66 ms
swiftype_nocode-bcc8d1c39f18a7802a7ee2c6f76577f3.css
48 ms
__utm.gif
22 ms
c6f83a98-0c89-4a65-a0ac-74ff50a24e8c.jpg
88 ms
a1e358d8-c993-414f-960e-f79c5498e4e1.png
114 ms
d4998514-9ac7-443a-9325-7a0e30f1ee82.jpg
85 ms
4911ba51-66b8-49f1-b499-08986e28b81f.jpg
101 ms
adaa4e49-d20f-407a-8260-e5772c6dc41c.jpg
102 ms
translate_24dp.png
33 ms
l
58 ms
eadd3ea9-9f66-4a44-8042-6f88bf4dc260.jpg
76 ms
5df9952f-be41-4dac-867c-1f8c29ba9e2b.jpg
37 ms
4032c8ec-5c3e-4071-a50f-f51dca1718f8.jpg
39 ms
e64483d1-da92-456c-9ea9-710ec07944df.png
75 ms
99e6d802-5af8-416f-a03d-bd8ff78919bc.jpg
83 ms
88bc8932-0d12-4024-a571-e5d350cff2a2.jpg
31 ms
93306963-3250-4675-aef3-2a4d8e7c8b4e.jpg
19 ms
ac271736-4b67-4a81-81dd-7ae66969a9eb.png
28 ms
in.php
134 ms
f24e6e25-2dbd-4790-9459-57c5a5bc6fe1.jpg
19 ms
overlay_bg-641ab15b9fe7cd9faabf12d0415c92d2.png
8 ms
cc.js
8 ms
psp.org 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
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
psp.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
psp.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Psp.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 Psp.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.
psp.org
Open Graph description is not detected on the main page of Psp. 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: