1.7 sec in total
19 ms
1.4 sec
269 ms
Click here to check amazing Facingdisability content for United States. Otherwise, check out these important facts you probably never knew about facingdisability.com
Facing Disability’s extensive video library focuses on the life experiences of people coping with spinal cord injury, plus expert medical information.
Visit facingdisability.comWe analyzed Facingdisability.com page load time and found that the first response time was 19 ms and then it took 1.7 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.
facingdisability.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value12.0 s
0/100
25%
Value5.9 s
48/100
10%
Value830 ms
35/100
30%
Value0.003
100/100
15%
Value12.0 s
16/100
10%
19 ms
235 ms
36 ms
14 ms
23 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 51% of them (46 requests) were addressed to the original Facingdisability.com, 9% (8 requests) were made to Apis.google.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (634 ms) relates to the external source Player.ooyala.com.
Page size can be reduced by 767.4 kB (54%)
1.4 MB
641.6 kB
In fact, the total size of Facingdisability.com 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. 75% 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. Javascripts take 953.3 kB which makes up the majority of the site volume.
Potential reduce by 77.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. 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 77.3 kB or 45% 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. Facingdisability images are well optimized though.
Potential reduce by 654.1 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 654.1 kB or 69% of the original size.
Potential reduce by 36.1 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. Facingdisability.com needs all CSS files to be minified and compressed as it can save up to 36.1 kB or 76% of the original size.
Number of requests can be reduced by 61 (73%)
84
23
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facingdisability. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
facingdisability.com
19 ms
www.facingdisability.com
235 ms
css
36 ms
application.css
14 ms
slim-081711.css
23 ms
jquery.min.js
22 ms
jquery-ui.min.js
24 ms
swfobject_src.js
28 ms
corners.js
19 ms
carousel.js
19 ms
condense.js
20 ms
qtip.js
24 ms
columns.js
25 ms
smooth.scroll.js
24 ms
font.size.js
23 ms
jqplugin.js
24 ms
jquery.easing.1.3.js
23 ms
captify.tiny.js
25 ms
ckeditor.js
30 ms
application.js
31 ms
jquery.url.js
31 ms
jquery.spine.js
31 ms
collapsable.js
31 ms
a595fa885e9a4c2eae74125c85e40dfb
303 ms
addthis_widget.js
23 ms
reset.css
27 ms
960.css
27 ms
layout.css
28 ms
typography.css
30 ms
index.css
30 ms
navigation.css
30 ms
search.css
31 ms
videos.css
32 ms
forms.css
32 ms
resources.css
33 ms
app-ads.css
33 ms
responsive.css
34 ms
spine.css
35 ms
collapsable.css
36 ms
2ac739
25 ms
dc.js
31 ms
inpage_linkid.js
6 ms
__utm.gif
13 ms
facingdisability_logo_alt.jpg
59 ms
Screen-Shot-2016-03-15-at-1.08.31-PM.png
261 ms
btn-search.jpg
54 ms
btn-increase.jpg
54 ms
btn-decrease.jpg
54 ms
bg-li.jpg
55 ms
bg-li-videos.jpg
54 ms
facing-app-med.png
56 ms
icon-facebook.jpg
55 ms
icon-twitter.jpg
53 ms
5wcjlsYzq-Z0tN5om5I4KLkR2Kc24jVt
138 ms
img-topic.jpg
132 ms
bg-co.png
133 ms
img-questions.jpg
134 ms
img-experts.jpg
134 ms
B0txb0blf2N29WdYPJjMShZ1gqmQBTb4Nwa_fF0DajA.woff
34 ms
Ez4zJbsGr2BgXcNUWBVgECyW0kDznfHZ5pM_3J5q0b8.woff
35 ms
Ez4zJbsGr2BgXcNUWBVgEJwdxg8gzQNM6zG8Kbi0OAw.woff
35 ms
Ez4zJbsGr2BgXcNUWBVgEFxo_3fQgeDvKMambfIp_uA.woff
35 ms
NiZjNtMTE6fEZTgxMMb5ozqLGv0x3D8_
634 ms
spinal.jpg
76 ms
all.js
56 ms
ooyala_storage.html
36 ms
300lo.json
102 ms
widgets.js
11 ms
plusone.js
97 ms
1339.js
86 ms
sh.8e5f85691f9aaa082472a194.html
83 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
96 ms
128 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
86 ms
fastbutton
153 ms
xd_arbiter.php
37 ms
xd_arbiter.php
65 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
24 ms
postmessageRelay
38 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
33 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
21 ms
cb=gapi.loaded_0
3 ms
jot
105 ms
ping
47 ms
like.php
66 ms
qeKvIRsJabD.js
27 ms
LVx-xkvaJ0b.png
20 ms
facingdisability.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
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
Form elements do not have associated labels
Links do not have a discernible name
facingdisability.com 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
facingdisability.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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facingdisability.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Facingdisability.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
facingdisability.com
Open Graph description is not detected on the main page of Facingdisability. 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: