4.7 sec in total
161 ms
4.2 sec
388 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 161 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
documentinghope.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value13.0 s
0/100
25%
Value33.8 s
0/100
10%
Value29,400 ms
0/100
30%
Value0.007
100/100
15%
Value42.1 s
0/100
10%
161 ms
199 ms
54 ms
34 ms
21 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 56% of them (53 requests) were addressed to the original Documentinghope.com, 14% (13 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Documentinghope.com.
Page size can be reduced by 1.3 MB (26%)
4.8 MB
3.5 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. 70% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 169.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 169.1 kB or 81% of the original size.
Potential reduce by 1.1 MB
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, Documenting Hope needs image optimization as it can save up to 1.1 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.0 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 3.0 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 52 (72%)
72
20
The browser has sent 72 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 37 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
documentinghope.com
161 ms
documentinghope.com
199 ms
cv.css
54 ms
cookie-law-info-public.css
34 ms
cookie-law-info-gdpr.css
21 ms
jquery-ui.css
30 ms
responsive-grid-framework.css
65 ms
style.css
122 ms
give.css
59 ms
give-donation-summary.css
66 ms
give-fee-recovery-frontend.min.css
64 ms
give-recurring.css
66 ms
css
53 ms
style.css
31 ms
smartslider.min.css
117 ms
css
63 ms
fontawesome.min.css
156 ms
jquery.min.js
45 ms
jquery-migrate.min.js
43 ms
cookie-law-info-public.js
42 ms
jstz.js
52 ms
submit.js
54 ms
api.js
56 ms
regenerator-runtime.min.js
62 ms
wp-polyfill.min.js
60 ms
hooks.min.js
65 ms
i18n.min.js
70 ms
give.js
79 ms
give-fee-recovery-public.min.js
80 ms
give-recurring.js
79 ms
ds-script.js
91 ms
getTrackingCode
139 ms
js
66 ms
n2.min.js
93 ms
smartslider-frontend.min.js
103 ms
ss-block.min.js
87 ms
cv.js
96 ms
core.min.js
104 ms
datepicker.min.js
106 ms
getTrackingCode
294 ms
wpf-leadsource-tracking.js
110 ms
44 ms
give-stripe.js
111 ms
give-donation-summary.js
120 ms
scripts.min.js
126 ms
smoothscroll.js
117 ms
jquery.fitvids.js
125 ms
common.js
118 ms
helper.min.js
120 ms
recaptcha__en.js
137 ms
api.min.js
160 ms
153786999
368 ms
favicon.png
99 ms
DH_proving-our-children-can-get-better.png
3389 ms
DH_logo.png
200 ms
DH-OurResearch-VideoThumbnail-2.png
366 ms
EA_DH_logo-new-1024x256.png
209 ms
DH_CHIRP_logo.png
97 ms
DH_FLIGHT_logo.png
141 ms
DH_stay-up-to-date-1024x996.png
452 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf
133 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf
163 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf
186 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf
162 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf
186 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf
184 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNig.ttf
145 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf
186 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNig.ttf
189 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNig.ttf
189 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNig.ttf
190 ms
analytics.js
120 ms
et-divi-dynamic-tb-113-2-late.css
66 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
104 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
105 ms
modules.ttf
109 ms
api.min.js
75 ms
collect
108 ms
api.min.js
46 ms
collect
953 ms
601273523-516ccc8cd34257370fe992535551c26d71f2076cc57a397b621bdf1f0cad4f6d-d.jpg
62 ms
player.js
59 ms
player.css
59 ms
m-outer-e7de605ddb82ddd9dd0b0d0d7c06b7d6.html
74 ms
invisible.js
80 ms
153786999
905 ms
m-outer-01936564b57cfdef4da595dd64c150b4.js
21 ms
inner.html
855 ms
754e653afe9f5a40
37 ms
601273523-516ccc8cd34257370fe992535551c26d71f2076cc57a397b621bdf1f0cad4f6d-d.jpg
6 ms
player.js
20 ms
player.css
9 ms
601273523-516ccc8cd34257370fe992535551c26d71f2076cc57a397b621bdf1f0cad4f6d-d
55 ms
websiteTriggerIframe
183 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
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
Browser errors were logged to the console
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: