2.8 sec in total
428 ms
1.9 sec
518 ms
Click here to check amazing Pfh content for United States. Otherwise, check out these important facts you probably never knew about pfh.org
PFH is a comprehensive behavioral health non-profit organization. We provide substance abuse treatment, prevention, and mental health services.
Visit pfh.orgWe analyzed Pfh.org page load time and found that the first response time was 428 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
pfh.org performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value5.6 s
18/100
25%
Value5.5 s
55/100
10%
Value40 ms
100/100
30%
Value0.05
99/100
15%
Value4.8 s
79/100
10%
428 ms
24 ms
179 ms
123 ms
125 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 89% of them (78 requests) were addressed to the original Pfh.org, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (674 ms) belongs to the original domain Pfh.org.
Page size can be reduced by 410.5 kB (19%)
2.2 MB
1.7 MB
In fact, the total size of Pfh.org main page is 2.2 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 16.6 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 16.6 kB or 75% of the original size.
Potential reduce by 108.6 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. Pfh images are well optimized though.
Potential reduce by 207.9 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 207.9 kB or 70% of the original size.
Potential reduce by 77.4 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. Pfh.org needs all CSS files to be minified and compressed as it can save up to 77.4 kB or 84% of the original size.
Number of requests can be reduced by 30 (37%)
82
52
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pfh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
pfh.org
428 ms
html5.js
24 ms
pfh.css
179 ms
slider.css
123 ms
mosaic.css
125 ms
mediaelementplayer.css
296 ms
css
96 ms
jquery.fancybox.css
203 ms
jquery.fancybox-buttons.css
135 ms
chapter_marker_player.css
140 ms
pfh.css
364 ms
pfh_mobile.css
294 ms
jquery.min.js
113 ms
raphael-min.js
467 ms
jquery.anystretch.min.js
257 ms
jquery.fancybox.js
528 ms
jquery.fancybox-buttons.js
310 ms
jquery.fancybox-media.js
316 ms
fancybox_functions.js
359 ms
pfh.js
382 ms
audio-player.js
382 ms
audio-player-setup.js
418 ms
mosaic.1.0.1.js
421 ms
chapter_marker_player.js
435 ms
mediaelement-and-player.min.js
552 ms
jquery.nivo.slider.js
475 ms
body_bg2.png
72 ms
header_bg_blank.png
212 ms
pfhlogo_v13.png
81 ms
pfhlogo_v13_emblem.png
78 ms
pfhlogo_v13_emblem_home.png
77 ms
mobile_logo_small.png
75 ms
mobile_logo_normal.png
206 ms
mobile_menu.png
207 ms
mobile_logo_very_small.png
204 ms
underlinemenu_border_bottom.png
205 ms
close_icon.png
206 ms
index_bg.png
412 ms
title_bg.png
350 ms
progress.gif
228 ms
slide_joplin.png
561 ms
slide_pfh_virtual_world_presentation2.png
465 ms
slide_pfh_jcadol3.png
361 ms
slide_find_pfh.png
428 ms
slide_pfh_artc.png
617 ms
ss_index.png
428 ms
performanceresults_index.png
472 ms
newsletter_index.png
500 ms
facebook_48.png
499 ms
youtube_48.png
525 ms
twitter_48.png
539 ms
blogger_48.png
566 ms
pinterest_48.png
579 ms
linkedin_48.png
589 ms
google_48.png
596 ms
MFH.jpg
616 ms
stlc_CSF.jpg
631 ms
dbh.jpg
642 ms
mhb.jpg
650 ms
CCRB_logo.jpg
661 ms
LCRB.jpg
674 ms
FCCRB.jpg
631 ms
22ndJudicial.jpg
629 ms
samsha.jpg
639 ms
nmrhn.jpg
648 ms
csc.jpg
654 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
130 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
131 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
178 ms
J0G-xR46MCQ1NwlKplDuiA.woff
180 ms
QS5qjU-Gc2sqWEq5kDfWQfesZW2xOQ-xsNqO47m55DA.woff
179 ms
katee_hessler_foundation.jpg
666 ms
ga.js
74 ms
mo_ded.jpg
546 ms
kdads.jpg
570 ms
ucs_ks.jpg
572 ms
city_of_wichita.jpg
581 ms
value_options_ks.jpg
586 ms
up_button.png
600 ms
__utm.gif
27 ms
welcome_text_spacer.png
553 ms
carf.png
483 ms
years_of_experience.png
474 ms
healthiest_emp.png
440 ms
footer_logo.png
421 ms
pfh.org
182 ms
arrows.png
70 ms
bullets.png
59 ms
pfh.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pfh.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
pfh.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Pfh.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 Pfh.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.
pfh.org
Open Graph description is not detected on the main page of Pfh. 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: