2.2 sec in total
347 ms
1.7 sec
165 ms
Welcome to facingus.org homepage info - get ready to check Facingus best content for United States right away, or after learning these important things about facingus.org
Find mental health facilities near you that treat depression, anxiety, eating disorders, panic disorder, OCD, PTSD and more.
Visit facingus.orgWe analyzed Facingus.org page load time and found that the first response time was 347 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
facingus.org performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value2.6 s
87/100
25%
Value2.6 s
97/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value3.8 s
90/100
10%
347 ms
202 ms
143 ms
145 ms
34 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 91% of them (31 requests) were addressed to the original Facingus.org, 3% (1 request) were made to Ssl.google-analytics.com and 3% (1 request) were made to Hello.myfonts.net. The less responsive or slowest element that took the longest time to load (990 ms) belongs to the original domain Facingus.org.
Page size can be reduced by 215.8 kB (14%)
1.6 MB
1.4 MB
In fact, the total size of Facingus.org main page is 1.6 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. 20% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 12.1 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 12.1 kB or 74% of the original size.
Potential reduce by 98.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. Facingus images are well optimized though.
Potential reduce by 70.5 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 70.5 kB or 61% of the original size.
Potential reduce by 34.6 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. Facingus.org needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 83% of the original size.
Number of requests can be reduced by 7 (22%)
32
25
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facingus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
facingus.org
347 ms
internal.css
202 ms
webfonts.css
143 ms
modernizr.min.js
145 ms
urchin.js
34 ms
jquery-1.9.1.min.js
309 ms
jquery.cookie.js
125 ms
scripts.js
126 ms
25ec35
25 ms
dbsa.css
186 ms
header-bg.png
125 ms
facing-us-link.gif
126 ms
sky.png
127 ms
cloud.png
129 ms
hill_a-bg.png
713 ms
hill_c-bg.png
744 ms
house.png
667 ms
hill-fg.png
693 ms
sun.png
263 ms
bg-color-only.gif
265 ms
dbsa-logo.gif
412 ms
tour-bg.png
430 ms
journal.jpg
619 ms
wellness-plan.jpg
650 ms
wellness-book-tips.jpg
776 ms
media-room.jpg
808 ms
resources.jpg
811 ms
creativity-center.jpg
815 ms
tracker.jpg
835 ms
sign-up.png
926 ms
radio.jpg
899 ms
postcards.jpg
932 ms
25EC35_0_0.woff
990 ms
__utm.gif
14 ms
facingus.org 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
facingus.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
facingus.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Facingus.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 Facingus.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.
facingus.org
Open Graph description is not detected on the main page of Facingus. 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: