12.8 sec in total
312 ms
9.5 sec
3 sec
Click here to check amazing Regulations content for United States. Otherwise, check out these important facts you probably never knew about regulations.gov
Visit regulations.govWe analyzed Regulations.gov page load time and found that the first response time was 312 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
regulations.gov performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value17.7 s
0/100
25%
Value16.2 s
0/100
10%
Value8,680 ms
0/100
30%
Value0.001
100/100
15%
Value21.1 s
1/100
10%
312 ms
458 ms
36 ms
62 ms
21 ms
Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Regulations.gov, 10% (1 request) were made to Googletagmanager.com and 10% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Js-agent.newrelic.com.
Page size can be reduced by 526.2 kB (61%)
862.4 kB
336.1 kB
In fact, the total size of Regulations.gov main page is 862.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 738.2 kB which makes up the majority of the site volume.
Potential reduce by 35.2 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 35.2 kB or 43% of the original size.
Potential reduce by 455.4 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 455.4 kB or 62% of the original size.
Potential reduce by 35.6 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. Regulations.gov needs all CSS files to be minified and compressed as it can save up to 35.6 kB or 85% of the original size.
Number of requests can be reduced by 4 (50%)
8
4
The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regulations. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
regulations.gov
312 ms
www.regulations.gov
458 ms
Regs.nocache.js,qbuildTag=2017060615060011.pagespeed.jm.Y4toXyx32-.js
36 ms
chrome.css
62 ms
reset.css
21 ms
9A8A7369221413B7B60F8735D3680755.cache.js
643 ms
gtm.js
703 ms
regs-loading.gif.pagespeed.ce.Xngeoqp3Iu.gif
785 ms
nr-1044.min.js
4242 ms
analytics.js
333 ms
regulations.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
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
regulations.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
Missing source maps for large first-party JavaScript
regulations.gov SEO score
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
N/A
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regulations.gov can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Regulations.gov main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
regulations.gov
Open Graph description is not detected on the main page of Regulations. 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: