1.4 sec in total
78 ms
899 ms
447 ms
Click here to check amazing Documenting Hope content. Otherwise, check out these important facts you probably never knew about documentinghope.com
Documenting Hope - In the United States over 50% of our children are diagnosed with a chronic health condition. We have no time to lose.
Visit documentinghope.comWe analyzed Documentinghope.com page load time and found that the first response time was 78 ms and then it took 1.3 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.
documentinghope.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value9.1 s
1/100
25%
Value9.0 s
15/100
10%
Value1,200 ms
20/100
30%
Value0.199
62/100
15%
Value13.6 s
11/100
10%
78 ms
111 ms
44 ms
40 ms
41 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 71% of them (68 requests) were addressed to the original Documentinghope.com, 14% (13 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (411 ms) relates to the external source Dnb.com.
Page size can be reduced by 184.7 kB (4%)
4.8 MB
4.6 MB
In fact, the total size of Documentinghope.com main page is 4.8 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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 179.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 179.6 kB or 80% of the original size.
Potential reduce by 516 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. Documenting Hope images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.2 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. Documentinghope.com has all CSS files already compressed.
Number of requests can be reduced by 63 (80%)
79
16
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Documenting Hope. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
documentinghope.com
78 ms
documentinghope.com
111 ms
cv.css
44 ms
cookie-law-info-public.css
40 ms
cookie-law-info-gdpr.css
41 ms
jquery-ui.css
28 ms
responsive-grid-framework.css
47 ms
style.css
43 ms
jquery.webui-popover.min.css
39 ms
lifterlms.min.css
63 ms
forms.min.css
55 ms
give.css
57 ms
give-donation-summary.css
68 ms
give-fee-recovery-frontend.min.css
68 ms
give-recurring.min.css
67 ms
style.min.css
66 ms
css
68 ms
style.css
66 ms
smartslider.min.css
72 ms
css
85 ms
fontawesome.min.css
81 ms
jquery.min.js
79 ms
jquery-migrate.min.js
75 ms
cookie-law-info-public.js
79 ms
jstz.js
78 ms
submit.js
102 ms
api.js
64 ms
wp-polyfill-inert.min.js
99 ms
regenerator-runtime.min.js
99 ms
wp-polyfill.min.js
100 ms
hooks.min.js
100 ms
i18n.min.js
100 ms
jquery.cookie.min.js
104 ms
tracking.min.js
107 ms
give.js
119 ms
give-fee-recovery-public.min.js
107 ms
give-recurring.min.js
112 ms
ds-script.js
113 ms
js
80 ms
n2.min.js
167 ms
smartslider-frontend.min.js
169 ms
ss-block.min.js
167 ms
ylu72wv62h.jsonp
43 ms
E-v1.js
60 ms
getTrackingCode
163 ms
47 ms
cv.js
162 ms
core.min.js
137 ms
datepicker.min.js
137 ms
tooltip.min.js
175 ms
mouse.min.js
170 ms
slider.min.js
170 ms
jquery.webui-popover.min.js
170 ms
llms.min.js
160 ms
llms-ajax.min.js
156 ms
llms-form-checkout.min.js
153 ms
give-stripe.js
152 ms
give-donation-summary.js
151 ms
scripts.min.js
152 ms
smoothscroll.js
149 ms
jquery.fitvids.js
148 ms
frontend-bundle.min.js
228 ms
common.js
224 ms
recaptcha__en.js
67 ms
api.min.js
92 ms
swatch
72 ms
duns_registered_logo.png
411 ms
et-divi-dynamic-tb-113-2-late.css
79 ms
favicon.png
151 ms
DH_proving-our-children-can-get-better.png
153 ms
DH_logo.png
151 ms
FollowResearch.png
175 ms
HelpYourChild.png
336 ms
FreeResources.png
154 ms
DH-Conference-Website.jpg
174 ms
Documenting-Hope-canary.png
174 ms
DH_FLIGHT_logo.png
174 ms
DH_CHIRP_logo.png
174 ms
DH_stay-up-to-date-1024x996.png
336 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNigDp6_dAyM.ttf
138 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jo43ZKyHqQg.ttf
158 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNigDp6_dAyM.ttf
319 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jo43ZKyHqQg.ttf
352 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNigDp6_dAyM.ttf
372 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNigDp6_dAyM.ttf
359 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNigDp6_dAyM.ttf
359 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNigDp6_dAyM.ttf
373 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNigDp6_dAyM.ttf
374 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNigDp6_dAyM.ttf
403 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNigDp6_dAyM.ttf
395 ms
app.js
248 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
229 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
230 ms
modules.woff
186 ms
modules.woff
187 ms
websiteTriggerIframe
126 ms
documentinghope.com 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
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.
documentinghope.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
documentinghope.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Documentinghope.com 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 Documentinghope.com 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.
documentinghope.com
Open Graph data is detected on the main page of Documenting Hope. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: