3 sec in total
792 ms
1.5 sec
714 ms
Click here to check amazing Seattle Spinal Cord content. Otherwise, check out these important facts you probably never knew about seattlespinalcord.com
Stritmatter attorneys have won a number of six-figure settlements for victims of spinal cord injury. To find out what you may be entitled to, call us today.
Visit seattlespinalcord.comWe analyzed Seattlespinalcord.com page load time and found that the first response time was 792 ms and then it took 2.2 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.
seattlespinalcord.com performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.6 s
0/100
25%
Value7.6 s
26/100
10%
Value1,070 ms
24/100
30%
Value0.05
99/100
15%
Value12.4 s
15/100
10%
792 ms
88 ms
136 ms
145 ms
199 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 85% of them (33 requests) were addressed to the original Seattlespinalcord.com, 8% (3 requests) were made to S.gravatar.com and 3% (1 request) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (792 ms) belongs to the original domain Seattlespinalcord.com.
Page size can be reduced by 275.2 kB (33%)
831.8 kB
556.6 kB
In fact, the total size of Seattlespinalcord.com main page is 831.8 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. 35% of websites need less resources to load. Images take 492.0 kB which makes up the majority of the site volume.
Potential reduce by 35.0 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 35.0 kB or 80% of the original size.
Potential reduce by 23.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. Seattle Spinal Cord images are well optimized though.
Potential reduce by 115.4 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 115.4 kB or 66% of the original size.
Potential reduce by 101.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. Seattlespinalcord.com needs all CSS files to be minified and compressed as it can save up to 101.3 kB or 85% of the original size.
Number of requests can be reduced by 20 (53%)
38
18
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seattle Spinal Cord. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
seattlespinalcord.com
792 ms
style.css
88 ms
style.responsive.css
136 ms
jetpack.css
145 ms
jquery.js
199 ms
script.js
139 ms
script.responsive.js
138 ms
script.js
159 ms
devicepx-jetpack.js
5 ms
gprofiles.js
55 ms
wpgroho.js
262 ms
e-201611.js
5 ms
wp-emoji-release.min.js
186 ms
page.png
79 ms
header.jpg
204 ms
menuseparator.png
95 ms
stats14-600x384.jpg
112 ms
postcategoryicon.png
82 ms
Spinal-Cord-Injury-Pressure-Sores-600x450.jpg
251 ms
posttagicon.png
146 ms
googleglass-300x166.jpg
227 ms
sciaging-300x182.jpg
160 ms
asia1-300x230.jpg
193 ms
asia2-300x205.jpg
271 ms
postcommentsicon.png
226 ms
schwann-cel-300x180.png
266 ms
SCIcoules.jpg
327 ms
postbullets.png
292 ms
DSCN2652-225x300.jpg
484 ms
DSCN2590-225x300.jpg
381 ms
karen.jpg
339 ms
facebook.png
335 ms
twitter.png
357 ms
linkedin.png
392 ms
youtube.png
402 ms
logo-193x62_white.png
411 ms
hovercard.css
37 ms
services.css
53 ms
g.gif
32 ms
seattlespinalcord.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
Links do not have a discernible name
seattlespinalcord.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
Page has valid source maps
seattlespinalcord.com SEO score
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 Seattlespinalcord.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 Seattlespinalcord.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.
seattlespinalcord.com
Open Graph description is not detected on the main page of Seattle Spinal Cord. 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: