2.1 sec in total
94 ms
1.6 sec
391 ms
Visit foster.house.gov now to see the best up-to-date Foster House content for United States and also check out these interesting facts you probably never knew about foster.house.gov
Representing the 11th District of Illinois
Visit foster.house.govWe analyzed Foster.house.gov page load time and found that the first response time was 94 ms and then it took 2 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.
foster.house.gov performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value8.5 s
2/100
25%
Value6.7 s
36/100
10%
Value5,240 ms
0/100
30%
Value0.627
9/100
15%
Value22.9 s
1/100
10%
94 ms
128 ms
76 ms
92 ms
66 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 87% of them (105 requests) were addressed to the original Foster.house.gov, 3% (4 requests) were made to Platform.twitter.com and 2% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (627 ms) belongs to the original domain Foster.house.gov.
Page size can be reduced by 851.4 kB (43%)
2.0 MB
1.1 MB
In fact, the total size of Foster.house.gov main page is 2.0 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 883.3 kB which makes up the majority of the site volume.
Potential reduce by 55.4 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 55.4 kB or 81% of the original size.
Potential reduce by 14.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. Foster House images are well optimized though.
Potential reduce by 414.2 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 414.2 kB or 70% of the original size.
Potential reduce by 367.3 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. Foster.house.gov needs all CSS files to be minified and compressed as it can save up to 367.3 kB or 83% of the original size.
Number of requests can be reduced by 74 (64%)
116
42
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foster 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 16 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
foster.house.gov
94 ms
system.base.css
128 ms
system.menus.css
76 ms
system.messages.css
92 ms
system.theme.css
66 ms
jquery.ui.core.min.css
68 ms
jquery.ui.theme.min.css
122 ms
jquery.ui.tabs.min.css
98 ms
jquery.ui.accordion.min.css
179 ms
jquery.ui.datepicker.min.css
169 ms
date.css
132 ms
datepicker.1.7.css
128 ms
field.css
156 ms
node.css
184 ms
panopoly-featured.css
161 ms
panopoly-accordian.css
241 ms
search.css
188 ms
user.css
238 ms
views.css
223 ms
caption-filter.css
253 ms
toggle.css
231 ms
colorbox_style.css
217 ms
ctools.css
253 ms
panels.css
282 ms
flexslider_img.css
299 ms
flexslider.css
437 ms
validationEngine.jquery.css
299 ms
superfish.css
291 ms
widgets.css
293 ms
alpha-reset.css
340 ms
alpha-mobile.css
325 ms
alpha-alpha.css
327 ms
formalize.css
343 ms
omega-text.css
413 ms
omega-branding.css
370 ms
omega-menu.css
375 ms
omega-forms.css
387 ms
omega-visuals.css
375 ms
congress-omega-global.css
357 ms
member-omega-global.css
382 ms
member-one-global.css
380 ms
one-foster-global.css
358 ms
member-omega-alpha-default.css
343 ms
member-one-alpha-default.css
362 ms
one-foster-alpha-default.css
364 ms
alpha-default-fluid-24.css
383 ms
member-omega-alpha-default-narrow.css
364 ms
member-one-alpha-default-narrow.css
429 ms
one-foster-alpha-default-narrow.css
438 ms
alpha-default-narrow-24.css
415 ms
member-omega-alpha-default-normal.css
341 ms
member-one-alpha-default-normal.css
366 ms
one-foster-alpha-default-normal.css
343 ms
alpha-default-normal-24.css
349 ms
member-omega-alpha-default-wide.css
350 ms
member-one-alpha-default-wide.css
358 ms
one-foster-alpha-default-wide.css
374 ms
alpha-default-wide-24.css
362 ms
js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js
455 ms
js_MGQ_rlJayLEGpg9xuwoO7aXdRkZjjRJGrWorOAprFxE.js
373 ms
js_XHDEsZ5M3UcLWIZoyXipJ3j-DhT-aOua-EOxpFrJRYo.js
347 ms
js_WSyDHMt8M6b-QDVRM_9OiVlUyPsgVZcd1xRmpIupDG0.js
400 ms
js_FZKHtlutSaoSmyEPVs6i_Ve0K3E3hGbUb6u8MEGCidI.js
362 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
346 ms
js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js
345 ms
js_rRpJbTj4LGknFR0buzCTOZJr5Roy7tSlsozt8w3J4qw.js
355 ms
analytics.js
57 ms
page-background.png
177 ms
header-background-bridge.jpg
268 ms
branding-bg-none.png
120 ms
logo.png
177 ms
menu-background-blue.jpg
118 ms
menu-leaf.png
42 ms
menu-expanded.png
116 ms
nav-about-bg.jpg
190 ms
nav-contact-bg.jpg
177 ms
nav-services-bg.jpg
225 ms
nav-media-bg.jpg
233 ms
nav-legislation-bg.jpg
253 ms
nav-resources-bg.jpg
231 ms
rotator-bg-bl.png
299 ms
scicmtehearingvidbutton.jpg
315 ms
Untitled%20design%20%2820%29.jpg
343 ms
1.3millionreturned.jpg
476 ms
iran%20press%20conf%20play.jpg
455 ms
connect-bg75.png
343 ms
twitter.png
343 ms
facebook.png
480 ms
flickr.png
462 ms
youtube.png
475 ms
rss.png
475 ms
connect-newsletter-bg.png
478 ms
newsletter-image-bg-ul_1_small.png
476 ms
block-background-bl.png
484 ms
long-ribbon-bl.png
479 ms
line-ribbon-b.png
498 ms
bg-popup-capitol.jpg
482 ms
twitter.png
481 ms
facebook.png
575 ms
flickr.png
558 ms
youtube.png
484 ms
rss.png
494 ms
widgets.js
11 ms
thomas-bl.png
627 ms
videoseries
132 ms
select-arrow.gif
465 ms
footer-bg.png
610 ms
footer-third-bg.png
541 ms
collect
47 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
23 ms
collect
66 ms
312252082868592640
484 ms
www-embed-player-vflfNyN_r.css
38 ms
www-embed-player.js
72 ms
base.js
103 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
65 ms
ad_status.js
68 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
79 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
87 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
foster.house.gov accessibility score
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
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.
foster.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
foster.house.gov 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
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 Foster.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 Foster.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.
foster.house.gov
Open Graph data is detected on the main page of Foster House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: