1.7 sec in total
27 ms
1.4 sec
194 ms
Welcome to openstates.org homepage info - get ready to check Open States best content for United States right away, or after learning these important things about openstates.org
Use our free democracy tools and open data to discover politics in your area, including bill search, find your legislators, and API access.
Visit openstates.orgWe analyzed Openstates.org page load time and found that the first response time was 27 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.
openstates.org performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value2.4 s
92/100
25%
Value1.2 s
100/100
10%
Value250 ms
84/100
30%
Value0.537
14/100
15%
Value3.6 s
92/100
10%
27 ms
57 ms
36 ms
71 ms
435 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Openstates.org, 34% (23 requests) were made to Static.openstates.org and 22% (15 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (435 ms) relates to the external source Static.openstates.org.
Page size can be reduced by 719.8 kB (61%)
1.2 MB
457.5 kB
In fact, the total size of Openstates.org main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 596.4 kB which makes up the majority of the site volume.
Potential reduce by 63.0 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 63.0 kB or 72% of the original size.
Potential reduce by 4.7 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. Open States images are well optimized though.
Potential reduce by 385.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 385.7 kB or 65% of the original size.
Potential reduce by 266.4 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. Openstates.org needs all CSS files to be minified and compressed as it can save up to 266.4 kB or 83% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open States. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
openstates.org
27 ms
main.css
57 ms
select2.css
36 ms
jquery-1.9.0.min.js
71 ms
jquery.hotkeys.min.js
435 ms
select2.min.js
22 ms
main.js
35 ms
xau7dem.js
94 ms
jquery.calendar-widget.js
35 ms
simple-socialite-pack.min.js
62 ms
brandingbar.css
103 ms
sf-icons.css
103 ms
d3.v3.min.js
46 ms
brandingbar.min.js.gz
191 ms
openstates.org
125 ms
analytics.js
112 ms
bg.jpg
234 ms
bg_header.jpg
95 ms
btn_search.png
92 ms
logo.png
93 ms
bg_tagline.jpg
97 ms
bg_tagline_star.png
180 ms
btn_searchAddress.png
95 ms
bg_appBox.png
96 ms
bg_dataBox.png
102 ms
bg_footer.jpg
95 ms
bg_sunlightLogo.png
97 ms
bg_resources.png
100 ms
bg_resourcesTitle.png
101 ms
btn_submitFooter.png
101 ms
twitter.png
67 ms
widgets.js
62 ms
all.js
287 ms
select2.png
79 ms
facebook.png
78 ms
lHKbMg1tPsg
159 ms
3RTkaDVeGBPJS5U7H0e17gBfUcxFnydrStRHjzVwxwGffwVMggMWeMJ6Mk6f5M9.woff
59 ms
RbMh0tORE7Pt2hWh6Flg1Cp1Jkb3MqSfDVShas97AWbffVEgggMWeMJ6Mk6f5Mw.woff
99 ms
HeEEk1Ac0a97Ux1E98ToKFqBA6DrBmTA9X1oihJdnUSffVruggMWeMJ6Mk6f5MS.woff
136 ms
pCVPVejBFGYD2UXmVTxu8NaQ4s_IbxBab3j-pIhTx96ffJzjMUMWeMJ6Mk6f5M6.woff
152 ms
zNnBoMbxHxCjt1WHw17O3nAtkhfbBC98-jeOJwxmWEXffHEUggMWeMJ6Mk6f5Mt.woff
166 ms
qdLVkcr74_wEwGo8UE1DJQDOegU5MlEN-H7NMLyaTZqffOHUggMWeMJ6Mk6f5gI.woff
165 ms
MkoMf2ZSJtp3WrF2lGcMzzhCR_0xqmPJ6_HI66lCiN3ffHhUggMWeMJ6Mk6f5Mb.woff
164 ms
PytnjvoJCE4hCygxN284-QxS_W0yTpxbYsO5-ipcIZSff5-oggMWeMJ6Mk6f5M9.woff
162 ms
3eFtj1piVne_3JG3h7tn68bLDayx5OWUZSzh7wZJFQ6ffOeUggMWeMJ6Mk6f5MS.woff
180 ms
rYPZQ8805wcih_1qW2M-7NvaQmwaKj460AYLeeDwejqffwefggMWeMJ6Mk6f5MX.woff
200 ms
TaJdiMUFWT8t3lAD0b0GUJRL1pDfQ_NA7E-vXgSgQy9ffJRjMUMWeMJ6Mk6f5Mv.woff
188 ms
E68YEL1wAol03LF7bzCChSvMeLykW0e4B88ea6xr4wXffJnjMUMWeMJ6Mk6f5gI.woff
194 ms
r_Jsw2uNr4rNcLCnWAn5MR5uWfcNkfRoK8G1waAmXJqffJDjMUMWeMJ6Mk6f5gJ.woff
192 ms
collect
48 ms
collect
42 ms
32 ms
sunlight-logo.svg
25 ms
sf-icons.svg
53 ms
sf-icons.woff
21 ms
www-embed-player-vflQrT_sR.css
72 ms
www-embed-player.js
116 ms
base.js
180 ms
p.gif
204 ms
41 ms
xd_arbiter.php
219 ms
xd_arbiter.php
430 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
32 ms
ad_status.js
33 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
73 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
83 ms
chartbeat.js
50 ms
ping
6 ms
openstates.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
openstates.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
openstates.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Openstates.org 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 Openstates.org 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.
openstates.org
Open Graph description is not detected on the main page of Open States. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: