1.1 sec in total
129 ms
741 ms
235 ms
Click here to check amazing Project HOME content for United States. Otherwise, check out these important facts you probably never knew about projecthome.org
None of us are home until all of us are home
Visit projecthome.orgWe analyzed Projecthome.org page load time and found that the first response time was 129 ms and then it took 976 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
projecthome.org performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value11.9 s
0/100
25%
Value13.2 s
2/100
10%
Value790 ms
37/100
30%
Value0
100/100
15%
Value29.5 s
0/100
10%
129 ms
23 ms
44 ms
62 ms
62 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Projecthome.org, 3% (2 requests) were made to Ssl.google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Projecthome.org.
Page size can be reduced by 545.3 kB (32%)
1.7 MB
1.2 MB
In fact, the total size of Projecthome.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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 45.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 45.1 kB or 78% of the original size.
Potential reduce by 212.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. Obviously, Project HOME needs image optimization as it can save up to 212.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 155.3 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 155.3 kB or 69% of the original size.
Potential reduce by 132.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. Projecthome.org needs all CSS files to be minified and compressed as it can save up to 132.4 kB or 85% of the original size.
Number of requests can be reduced by 43 (65%)
66
23
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project HOME. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
projecthome.org
129 ms
system.base.css
23 ms
system.menus.css
44 ms
system.messages.css
62 ms
system.theme.css
62 ms
date.css
68 ms
datepicker.1.7.css
64 ms
field.css
65 ms
fitvids.css
66 ms
logintoboggan.css
80 ms
menu_attach_block.css
79 ms
node.css
82 ms
search.css
83 ms
user.css
81 ms
views.css
80 ms
colorbox_default_style.css
100 ms
ctools.css
97 ms
panels.css
101 ms
tagclouds.css
105 ms
nice_menus.css
101 ms
nice_menus_default.css
103 ms
flexslider_img.css
115 ms
flexslider.css
117 ms
alpha-reset.css
118 ms
alpha-mobile.css
119 ms
alpha-alpha.css
119 ms
formalize.css
121 ms
omega-text.css
133 ms
omega-branding.css
134 ms
omega-menu.css
135 ms
omega-forms.css
139 ms
omega-visuals.css
137 ms
global.XcVzbo5GbrB4v7QVES377fts6uudS0o0YbaMpBamvPg.css
140 ms
js_7-QUBm7UNKxGysSRvvU8NUXK0dgit5hMewfryG8U0M8.js
170 ms
js_nT-3TqmhkiIn30tHICx1inWtvQizOLtaBPI9cbRYVJE.js
151 ms
js_jwESgYOirNfSG_WSOKlBAWpwitKVgcLQt5S9-dm0IoI.js
152 ms
js_pEFtshlBAtfa86hVW4krb5KJUXXc-aqG19FO8IqjV7M.js
190 ms
js_3HXVXavB_FyAx5cr2Hpfd9MCAt0-ih9KX5coZo_pF_Y.js
147 ms
js_meDomBEy82aWXpUVuohOCqoX7y2SY1EL4mcRvK0f97E.js
130 ms
js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js
140 ms
ga.js
78 ms
nav-div.png
33 ms
ph-logo-sm.png
31 ms
logo.png
62 ms
icon-phone.png
29 ms
icon-cart.png
32 ms
icon-mag.png
32 ms
HOMEPAGE_2415.jpg
194 ms
HOME_HubOfHope.jpg
111 ms
LANDING_MercyJustice-WhatNext_0.jpg
192 ms
HOMEPAGE_TuftsTalk.jpg
142 ms
HOME_MayorKenney.jpg
196 ms
PAGE_Donate.jpg
137 ms
ADVO_MG_0747.JPG
164 ms
Home-Page-Call-to-Action-Images_Get-Involved.jpg
188 ms
dots.png
171 ms
shadow.png
190 ms
title-line.png
196 ms
4Star%20234x60.jpg
213 ms
twitter.png
215 ms
facebook.png
213 ms
google_plus.png
216 ms
youtube.png
217 ms
mail.png
218 ms
bg-trans-gray.png
232 ms
FuturaStd-Book.svg
275 ms
FuturaStd-Book.woff
252 ms
FuturaStd-Light.woff
237 ms
__utm.gif
14 ms
collect
59 ms
ga-audiences
39 ms
projecthome.org accessibility score
projecthome.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
projecthome.org SEO score
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 Projecthome.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 Projecthome.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.
projecthome.org
Open Graph description is not detected on the main page of Project HOME. 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: