1.7 sec in total
58 ms
1.3 sec
371 ms
Welcome to beraforms.house.gov homepage info - get ready to check Bera Forms House best content for United States right away, or after learning these important things about beraforms.house.gov
Representing the 6th District of California
Visit beraforms.house.govWe analyzed Beraforms.house.gov page load time and found that the first response time was 58 ms and then it took 1.6 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.
beraforms.house.gov performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value11.1 s
0/100
25%
Value7.6 s
25/100
10%
Value1,950 ms
8/100
30%
Value0.687
7/100
15%
Value14.9 s
8/100
10%
58 ms
196 ms
85 ms
23 ms
52 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Beraforms.house.gov, 89% (115 requests) were made to Bera.house.gov and 2% (3 requests) were made to Docs.google.com. The less responsive or slowest element that took the longest time to load (449 ms) relates to the external source Bera.house.gov.
Page size can be reduced by 682.4 kB (33%)
2.1 MB
1.4 MB
In fact, the total size of Beraforms.house.gov main page is 2.1 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 60.5 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 60.5 kB or 80% of the original size.
Potential reduce by 62.1 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. Bera Forms House images are well optimized though.
Potential reduce by 342.7 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 342.7 kB or 70% of the original size.
Potential reduce by 217.1 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. Beraforms.house.gov needs all CSS files to be minified and compressed as it can save up to 217.1 kB or 82% of the original size.
Number of requests can be reduced by 94 (76%)
124
30
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bera Forms 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 30 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
beraforms.house.gov
58 ms
bera.house.gov
196 ms
fbevents.js
85 ms
system.base.css
23 ms
system.menus.css
52 ms
system.messages.css
38 ms
system.theme.css
44 ms
jquery.ui.core.min.css
39 ms
jquery.ui.theme.min.css
41 ms
jquery.ui.tabs.min.css
44 ms
jquery.ui.accordion.min.css
60 ms
jquery.ui.datepicker.min.css
46 ms
date.css
69 ms
datepicker.1.7.css
57 ms
field.css
70 ms
node.css
66 ms
panopoly-featured.css
74 ms
panopoly-accordian.css
74 ms
search.css
76 ms
user.css
97 ms
views.css
113 ms
caption-filter.css
94 ms
toggle.css
88 ms
colorbox_style.css
97 ms
ctools.css
94 ms
panels.css
113 ms
flexslider_img.css
133 ms
flexslider.css
129 ms
validationEngine.jquery.css
128 ms
widgets.css
130 ms
superfish.css
130 ms
quicktabs.css
177 ms
alpha-reset.css
189 ms
alpha-mobile.css
151 ms
alpha-alpha.css
188 ms
formalize.css
157 ms
omega-text.css
149 ms
omega-branding.css
174 ms
omega-menu.css
170 ms
omega-forms.css
175 ms
omega-visuals.css
166 ms
congress-omega-global.css
166 ms
member-omega-global.css
177 ms
bera-global.css
172 ms
css_injector_1.css
204 ms
member-omega-alpha-default.css
169 ms
bera-alpha-default.css
190 ms
alpha-default-fluid-24.css
178 ms
alpha-default-fluid-12.css
194 ms
member-omega-alpha-default-narrow.css
173 ms
bera-alpha-default-narrow.css
163 ms
alpha-default-narrow-24.css
185 ms
alpha-default-narrow-12.css
184 ms
member-omega-alpha-default-normal.css
207 ms
bera-alpha-default-normal.css
185 ms
123 ms
139 ms
alpha-default-normal-24.css
173 ms
alpha-default-normal-12.css
171 ms
member-omega-alpha-default-wide.css
177 ms
bera-alpha-default-wide.css
213 ms
alpha-default-wide-24.css
175 ms
alpha-default-wide-12.css
169 ms
jquery.min.js
189 ms
jquery.once.js
161 ms
drupal.js
203 ms
jquery.ui.core.min.js
205 ms
jquery.ui.widget.min.js
200 ms
jquery.ui.tabs.min.js
213 ms
jquery.ui.accordion.min.js
207 ms
jquery.ui.datepicker.min.js
223 ms
panopoly-accordion.js
220 ms
caption-filter.js
204 ms
toggle.js
216 ms
progress.js
216 ms
jquery.colorbox-min.js
225 ms
colorbox.js
236 ms
colorbox_style.js
227 ms
jquery.flexslider-min.js
224 ms
googleanalytics.js
233 ms
superfish.js
227 ms
jquery.hoverIntent.minified.js
269 ms
quicktabs.js
250 ms
jquery.cookie.js
237 ms
house_enews_popup.js
242 ms
jquery.formalize.js
236 ms
omega-mediaqueries.js
256 ms
flexslider.load.js
358 ms
jquery.validationEngine-en.js
353 ms
jquery.validationEngine.js
349 ms
analytics.js
6 ms
collect
12 ms
viewform
280 ms
logo.png
127 ms
twitter.png
125 ms
facebook.png
124 ms
flickr.png
123 ms
youtube.png
124 ms
rss.png
123 ms
button_submit_glass.png
199 ms
bera-img-banner.png
228 ms
menu-leaf.png
137 ms
menu-expanded.png
157 ms
email-icon.png
157 ms
meeting-icon.png
163 ms
tickets-icon.png
199 ms
help-icon.png
208 ms
flags-icon.png
209 ms
updates-icon.png
215 ms
cab_vso.png
382 ms
cab_listening.jpg
266 ms
howicanhelp_0.jpg
273 ms
Checkmark_green.svg_.png
296 ms
glidecruisers.jpg
274 ms
view-more-icon.png
449 ms
thomas-icon.png
330 ms
select-arrow.gif
356 ms
7th-district-map.jpg
356 ms
CA-state-seal.png
369 ms
1535.jpg
414 ms
cab_localoffice.jpg
384 ms
flexslider-icon.woff
268 ms
css
64 ms
901542931-formview_embedded_st_ltr.css
7 ms
3972931225-formviewer_prd.js
25 ms
blue-stripe-bg.png
37 ms
forms_logo_2_small_dark.png
19 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
21 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
24 ms
beraforms.house.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
beraforms.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
beraforms.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beraforms.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 Beraforms.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.
beraforms.house.gov
Open Graph data is detected on the main page of Bera Forms House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: