1.9 sec in total
134 ms
1.2 sec
564 ms
Click here to check amazing Fphnyc content for United States. Otherwise, check out these important facts you probably never knew about fphnyc.org
Everyone deserves to live a healthy life. The Fund for Public Health in New York City facilitates innovative projects to improve health for all New Yorkers.
Visit fphnyc.orgWe analyzed Fphnyc.org page load time and found that the first response time was 134 ms and then it took 1.8 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.
fphnyc.org performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value6.1 s
12/100
25%
Value10.0 s
9/100
10%
Value3,220 ms
2/100
30%
Value0.606
10/100
15%
Value19.0 s
3/100
10%
134 ms
237 ms
72 ms
29 ms
48 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 76% of them (47 requests) were addressed to the original Fphnyc.org, 8% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (457 ms) belongs to the original domain Fphnyc.org.
Page size can be reduced by 101.9 kB (6%)
1.7 MB
1.6 MB
In fact, the total size of Fphnyc.org main page is 1.7 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. Only a small number of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 97.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 97.9 kB or 73% of the original size.
Potential reduce by 0 B
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. Fphnyc images are well optimized though.
Potential reduce by 3.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. This website has mostly compressed JavaScripts.
Potential reduce by 120 B
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. Fphnyc.org has all CSS files already compressed.
Number of requests can be reduced by 38 (66%)
58
20
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fphnyc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fphnyc.org
134 ms
fphnyc.org
237 ms
css2
72 ms
style.min.css
29 ms
custom_blocks_style.bundle.css
48 ms
all.css
76 ms
widget-options.css
50 ms
style.css
60 ms
js
245 ms
jquery.min.js
72 ms
jquery-migrate.min.js
54 ms
custom_blocks_frontend.bundle.js
70 ms
meanmenu.min.js
70 ms
doubletaptogo.min.js
117 ms
main.js
116 ms
optimize.js
124 ms
gravity-forms-theme-foundation.min.css
117 ms
gravity-forms-theme-reset.min.css
108 ms
gravity-forms-theme-framework.min.css
193 ms
basic.min.css
203 ms
theme-ie11.min.css
207 ms
theme.min.css
208 ms
countUp.umd.js
224 ms
wp-polyfill-inert.min.js
225 ms
regenerator-runtime.min.js
224 ms
wp-polyfill.min.js
228 ms
dom-ready.min.js
225 ms
hooks.min.js
235 ms
i18n.min.js
235 ms
a11y.min.js
235 ms
jquery.json.min.js
236 ms
gravityforms.min.js
285 ms
utils.min.js
287 ms
vendor-theme.min.js
289 ms
scripts-theme.min.js
291 ms
fbevents.js
181 ms
ELOMFyKDGWM
266 ms
fund-for-puplic-health-nyc.png
162 ms
website-header-image2A-1-1920x608.jpg
168 ms
Support-Banner-950x325.jpg
161 ms
2023-History-578x325.jpg
162 ms
cdc-aeh1dbI_a7I-unsplash-767x483.jpg
158 ms
woman-looking-at-toddler-1832097-scaled-e1575560146501-767x483.jpg
166 ms
Untitled-design-56.png
188 ms
Untitled-design-11.jpg
236 ms
FPHNYC_3-12-24_0161-1-720x312.jpg
181 ms
FacebookIcon.png
228 ms
Twitter-icon.png
211 ms
LinkedInIcon.png
214 ms
YouTube-icon.png
265 ms
IG-icon.png
265 ms
Charity_Navigator_Encompass_GiveWithConfidence_100-e1599666212885.png
296 ms
candid-seal-platinum-2024-150x150.png
457 ms
www-player.css
8 ms
www-embed-player.js
33 ms
base.js
66 ms
ad_status.js
186 ms
YpaxWjHVNNO6KZk05PsGAol2GFYfBj4WvF05Ro9VHVE.js
133 ms
embed.js
50 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
52 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
53 ms
id
17 ms
fphnyc.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fphnyc.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
Page has valid source maps
fphnyc.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
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 Fphnyc.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 Fphnyc.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.
fphnyc.org
Open Graph data is detected on the main page of Fphnyc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: