1.4 sec in total
89 ms
864 ms
484 ms
Welcome to dutch.house.gov homepage info - get ready to check Dutch House best content for United States right away, or after learning these important things about dutch.house.gov
Representing the 2nd District of Maryland
Visit dutch.house.govWe analyzed Dutch.house.gov page load time and found that the first response time was 89 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 25% of websites can load faster.
dutch.house.gov performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.6 s
0/100
25%
Value7.0 s
32/100
10%
Value330 ms
75/100
30%
Value0.276
44/100
15%
Value12.7 s
14/100
10%
89 ms
85 ms
13 ms
8 ms
17 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dutch.house.gov, 74% (43 requests) were made to Ruppersberger.house.gov and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (280 ms) relates to the external source Cdn.syndication.twimg.com.
Page size can be reduced by 873.9 kB (37%)
2.4 MB
1.5 MB
In fact, the total size of Dutch.house.gov main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.9 kB or 80% of the original size.
Potential reduce by 66.5 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. Dutch House images are well optimized though.
Potential reduce by 384.5 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 384.5 kB or 71% of the original size.
Potential reduce by 370.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. Dutch.house.gov needs all CSS files to be minified and compressed as it can save up to 370.0 kB or 84% of the original size.
Number of requests can be reduced by 32 (59%)
54
22
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dutch House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
dutch.house.gov
89 ms
ruppersberger.house.gov
85 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
13 ms
css_zhvx-jY7BKtc5CzwS2ygtUXVBw4l9s4sPkcbfS19KGI.css
8 ms
css_CQ5Mp3bkA9ZMxmmUXOtokUHprfWUsi_whSaziW9WvAk.css
17 ms
css_T4-0ckqRwqAs0IiBObinGEwkxJwkK2WjKIiUOpI4qyw.css
12 ms
css_wX74kl5SIRcuwthpuzMhYYlg5LCFlhTKvnUMZBDfHNE.css
31 ms
css__1PpCfY3Rv1RPfNoeyzPrrc67kAR02-BiRrE7rZXBbc.css
35 ms
js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js
35 ms
js_MGQ_rlJayLEGpg9xuwoO7aXdRkZjjRJGrWorOAprFxE.js
17 ms
js_XHDEsZ5M3UcLWIZoyXipJ3j-DhT-aOua-EOxpFrJRYo.js
16 ms
js_osmR5n3tbU6P2gNS_UIQS8rlw70afGbPX1CqmuPmAAU.js
73 ms
js_SfCbCGYW2BPYiaWCB7uVbb3pmTMTu8r3HMm49-mBsj8.js
23 ms
js_uwrfBOJCFVq42muTMjrq2bD-RUh8NNq_fZRTb6dsNb4.js
23 ms
js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js
120 ms
js_rRpJbTj4LGknFR0buzCTOZJr5Roy7tSlsozt8w3J4qw.js
118 ms
widgets.js
135 ms
all.js
136 ms
bg-section-header.jpg
153 ms
twitter.png
131 ms
facebook.png
132 ms
youtube.png
135 ms
rss.png
130 ms
btn-glass.png
129 ms
menu-expanded.png
131 ms
menu-leaf.png
135 ms
logo.png
131 ms
1012578_10153899304911474_2433978665657837616_n.jpg
140 ms
WHTourPic.jpg
143 ms
appchallenge2_0.png
153 ms
another-happy-customer-feb2015.png
145 ms
bg-actioncarousel.png
139 ms
twitter.png
142 ms
facebook.png
163 ms
bg-section-footer.jpg
144 ms
bg-news-extend.png
148 ms
bg-footer-offices.png
152 ms
DCSTAFF16_0.jpg
148 ms
group-of-people.jpg
149 ms
pop-up-banner.jpg
157 ms
twitter.png
159 ms
facebook.png
155 ms
youtube.png
157 ms
rss.png
158 ms
banner.jpg
141 ms
videoseries
205 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
59 ms
170 ms
xd_arbiter.php
33 ms
xd_arbiter.php
46 ms
css_WWtW7BY6CwB6ZHj9Z8CSA1yV6erTTjU0VihIHkBXD5g.css
68 ms
392760935640612864
280 ms
www-embed-player-vflfNyN_r.css
33 ms
www-embed-player.js
48 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
48 ms
ad_status.js
47 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
dutch.house.gov accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
dutch.house.gov 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
Page has valid source maps
dutch.house.gov 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 Dutch.house.gov 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 Dutch.house.gov 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.
dutch.house.gov
Open Graph data is detected on the main page of Dutch House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: