1.3 sec in total
75 ms
982 ms
277 ms
Click here to check amazing Pvaf content. Otherwise, check out these important facts you probably never knew about pvaf.org
The Paralyzed Veterans of America Florida Chapter serves Fort Lauderdale and all of South FL. Our mission is to improve the lives of disabled veterans.
Visit pvaf.orgWe analyzed Pvaf.org page load time and found that the first response time was 75 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
pvaf.org performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.2 s
11/100
25%
Value4.9 s
66/100
10%
Value140 ms
95/100
30%
Value0.083
94/100
15%
Value5.4 s
72/100
10%
75 ms
175 ms
61 ms
42 ms
45 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pvaf.org, 34% (35 requests) were made to Pvafl.org and 34% (35 requests) were made to Assets.myregisteredsite.com. The less responsive or slowest element that took the longest time to load (229 ms) relates to the external source Pvafl.org.
Page size can be reduced by 499.1 kB (67%)
744.4 kB
245.3 kB
In fact, the total size of Pvaf.org main page is 744.4 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. Javascripts take 512.4 kB which makes up the majority of the site volume.
Potential reduce by 42.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 42.0 kB or 82% of the original size.
Potential reduce by 12.1 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. Pvaf images are well optimized though.
Potential reduce by 416.7 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 416.7 kB or 81% of the original size.
Potential reduce by 28.2 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. Pvaf.org needs all CSS files to be minified and compressed as it can save up to 28.2 kB or 83% of the original size.
Number of requests can be reduced by 77 (78%)
99
22
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pvaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
pvaf.org
75 ms
www.pvafl.org
175 ms
button.css
61 ms
browserBehavior.js
42 ms
utils.js
45 ms
shared.js
61 ms
navigation.js
44 ms
uaDefaultStylesReset.css
62 ms
popup.js
47 ms
ResourceLoader.js
64 ms
googleFonts.css
23 ms
css
25 ms
css
37 ms
css
47 ms
css
49 ms
css
46 ms
css
47 ms
css
45 ms
css
48 ms
css
58 ms
css
56 ms
css
59 ms
css
56 ms
css
58 ms
css
59 ms
css
70 ms
css
68 ms
css
67 ms
css
69 ms
css
69 ms
css
70 ms
css
79 ms
css
79 ms
css
82 ms
css
80 ms
css
80 ms
css
82 ms
css
89 ms
css
89 ms
css
91 ms
jquery.js
77 ms
core.js
26 ms
socialmediashare.js
30 ms
jqueryvalidate.js
32 ms
photoalbum.js
68 ms
footercontact.js
55 ms
galleria.js
89 ms
form.js
26 ms
json.js
23 ms
smstemplates.js
24 ms
socialmediashare.css
26 ms
templates.js
27 ms
defaults.js
25 ms
photoalbum.css
22 ms
jquery.json-2.2.min.js
29 ms
templates.js
44 ms
footercontact.css
45 ms
utils.js
47 ms
resources.js
47 ms
templates.js
49 ms
form.css
52 ms
form_generic.css
64 ms
38009168.gif
37 ms
btn_donateCC_LG.gif
43 ms
38009179.jpeg
39 ms
38009180.gif
39 ms
38009182.gif
40 ms
38009183.gif
40 ms
38009169.gif
41 ms
38009184.gif
48 ms
80954012_scaled_320x147.jpg
88 ms
80954012_scaled_224x103.jpg
73 ms
80954386.jpg
118 ms
38009170.gif
49 ms
38009185.gif
63 ms
38009186.gif
69 ms
38009187.jpeg
96 ms
38009188.png
85 ms
38009171.png
90 ms
38009174.png
95 ms
38009172.png
110 ms
38009189.png
110 ms
38009190.jpeg
131 ms
38009191.gif
119 ms
103158680_scaled_189x78.png
229 ms
103158365_scaled_184x53.png
175 ms
103158361_scaled_147x74.jpg
129 ms
103158363_scaled_192x40.jpg
139 ms
103158362_scaled_146x80.jpg
141 ms
88849544_scaled_168x108.png
170 ms
38009192.gif
151 ms
38009193.gif
162 ms
38009194.jpeg
163 ms
l_share_2.png
24 ms
galleria.classic.min.js
25 ms
galleria.classic.css
26 ms
facebook_share_2.png
27 ms
google_share_2.png
26 ms
twitter_share_2.png
28 ms
linkedIn_share_2.png
40 ms
loading.gif
25 ms
logger.php
46 ms
pvaf.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
pvaf.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
Page has valid source maps
pvaf.org 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pvaf.org 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 Pvaf.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.
pvaf.org
Open Graph description is not detected on the main page of Pvaf. 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: