1.7 sec in total
51 ms
1.2 sec
424 ms
Click here to check amazing Vibrant content for United States. Otherwise, check out these important facts you probably never knew about vibrant.org
Groundbreaking mental health solutions delivering high-quality services and support, when, where, and how people need it for over 50 years.
Visit vibrant.orgWe analyzed Vibrant.org page load time and found that the first response time was 51 ms and then it took 1.6 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.
vibrant.org performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value20.5 s
0/100
25%
Value7.4 s
28/100
10%
Value1,930 ms
8/100
30%
Value0.147
76/100
15%
Value21.8 s
1/100
10%
51 ms
36 ms
44 ms
10 ms
20 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 87% of them (98 requests) were addressed to the original Vibrant.org, 4% (5 requests) were made to Use.fontawesome.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (287 ms) relates to the external source A.omappapi.com.
Page size can be reduced by 336.3 kB (8%)
4.1 MB
3.8 MB
In fact, the total size of Vibrant.org main page is 4.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. 85% 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. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 158.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. 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 158.9 kB or 85% of the original size.
Potential reduce by 79.5 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. Vibrant images are well optimized though.
Potential reduce by 66.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 66.4 kB or 14% of the original size.
Potential reduce by 31.5 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. Vibrant.org needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 22% of the original size.
Number of requests can be reduced by 68 (68%)
100
32
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vibrant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
vibrant.org
51 ms
www.vibrant.org
36 ms
css
44 ms
all.min.css
10 ms
v4-shims.min.css
20 ms
cnss.css
21 ms
style.min.css
28 ms
style.css
29 ms
style.css
28 ms
style.css
32 ms
style.css
30 ms
style.css
27 ms
styles.css
31 ms
style.css
33 ms
jquery.fancybox.css
32 ms
wpa-style.css
30 ms
vibrant.css
40 ms
custom.css
33 ms
style.css
34 ms
jquery.min.js
41 ms
jquery-migrate.min.js
40 ms
cnss.js
80 ms
conditionizr-4.3.0.min.js
39 ms
modernizr-2.7.1.min.js
92 ms
scripts.js
81 ms
jquery.fancybox.js
83 ms
cookie_popup_test.js
89 ms
cookie_test.js
84 ms
fingerprint.min.js
81 ms
easy-testimonials-reveal.js
82 ms
normalize.css
83 ms
style.css
87 ms
jquery.bxslider.css
86 ms
style.css
83 ms
4ea14a3321.js
195 ms
js
131 ms
core.min.js
82 ms
mouse.min.js
127 ms
sortable.min.js
83 ms
index.js
85 ms
api.js
84 ms
index.js
85 ms
slick.min.js
84 ms
jquery.fitvids.js
113 ms
scrollreveal.min.js
73 ms
odometer.min.js
67 ms
js.cookie.js
103 ms
vibrant.js
103 ms
navigation.js
103 ms
focus-within.js
103 ms
wp-polyfill-inert.min.js
102 ms
regenerator-runtime.min.js
105 ms
wp-polyfill.min.js
104 ms
index.js
102 ms
longdesc.min.js
103 ms
wp-accessibility.min.js
104 ms
jquery.cycle2.min.js
102 ms
jquery.cycle2.carousel.min.js
98 ms
jquery.cycle2.swipe.min.js
98 ms
jquery.cycle2.video.min.js
98 ms
player.js
61 ms
client.js
58 ms
jquery.cycle2.min.js
58 ms
jquery.bxslider.js
56 ms
gtm.js
54 ms
js
140 ms
192 ms
js
184 ms
Banner_1.jpg
166 ms
Banner_2-new.jpg
160 ms
Banner_3.jpg
161 ms
Banner_4.jpg
170 ms
FOR_UPLOAD_iStock-495654633_280x190.jpg
158 ms
FOR_UPLOAD_iStock-665805064_280x190.jpg
161 ms
FOR_UPLOAD_iStock-690730770_280x190.jpg
177 ms
FOR_UPLOAD_iStock-640289536_280x190.jpg
163 ms
3.2Million_Transparent.png
162 ms
FOR_UPLOAD_Stat_02.jpg
164 ms
FOR_UPLOAD_Stat_03_v4.jpg
166 ms
FOR_UPLOAD_Map_03.jpg
168 ms
stories.png
166 ms
Mari-Franqui1-592x385.jpg
166 ms
Devenkumar1-592x333.jpg
167 ms
Stephanie2-592x578.png
173 ms
partners.png
170 ms
pexels-rdne-stock-project-7982221-544x456.jpg
171 ms
ideas.png
171 ms
Untitled-design-1-544x456.png
174 ms
donghun-shin-bOEf13XYWjw-unsplash-scaled-e1678457436849-544x456.jpg
175 ms
anna-selle-BNRC73A-uLc-unsplash-544x456.jpg
176 ms
Vibrant-Website-2-544x456.png
177 ms
FOR_UPLOAD_get_involved_guy.jpg
233 ms
FOR_UPLOAD_events_Icon_02.jpg
179 ms
FOR_UPLOAD_donate_Icon_02.jpg
178 ms
FOR_UPLOAD_team_Icon_02.jpg
177 ms
CentraNo2-Book.woff
143 ms
4ea14a3321.css
137 ms
fa-solid-900.woff
120 ms
fa-regular-400.woff
218 ms
CentraNo2-Extrabold.woff
79 ms
fa-brands-400.woff
127 ms
CentraNo2-Bold.woff
81 ms
CentraNo2-Medium.woff
81 ms
font-awesome-css.min.css
101 ms
43 ms
api.min.js
287 ms
recaptcha__en.js
287 ms
4ea14a3321.css
202 ms
ajax-loader.gif
71 ms
facebook-76658_1280-138x69.png
71 ms
slick.woff
4 ms
fontawesome-webfont.woff
76 ms
fontawesome-webfont.woff
13 ms
vibrant.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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
vibrant.org 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
Browser errors were logged to the console
Page has valid source maps
vibrant.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
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 Vibrant.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 Vibrant.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.
vibrant.org
Open Graph data is detected on the main page of Vibrant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: