2.6 sec in total
136 ms
2.3 sec
169 ms
Click here to check amazing ELI content for United States. Otherwise, check out these important facts you probably never knew about eli.org
ELI makes law work for people, places and the planet.
Visit eli.orgWe analyzed Eli.org page load time and found that the first response time was 136 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
eli.org performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value5.2 s
23/100
25%
Value4.3 s
76/100
10%
Value700 ms
43/100
30%
Value0.239
52/100
15%
Value9.6 s
29/100
10%
136 ms
274 ms
26 ms
262 ms
350 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 72% of them (36 requests) were addressed to the original Eli.org, 12% (6 requests) were made to Use.typekit.net and 6% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Eli.org.
Page size can be reduced by 1.3 MB (18%)
6.9 MB
5.6 MB
In fact, the total size of Eli.org main page is 6.9 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. 40% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 170.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 170.2 kB or 78% of the original size.
Potential reduce by 143.2 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. ELI images are well optimized though.
Potential reduce by 722.6 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 722.6 kB or 72% of the original size.
Potential reduce by 217.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. Eli.org needs all CSS files to be minified and compressed as it can save up to 217.6 kB or 83% of the original size.
Number of requests can be reduced by 19 (44%)
43
24
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
eli.org
136 ms
www.eli.org
274 ms
css
26 ms
css_f2ad1eb0903a8c21351a2771e36c32fa.css
262 ms
js_fd170f72a18251a7a7ed93a23d752546.js
350 ms
gcb5qff.js
147 ms
addthis_widget.js
10 ms
js_dc5ddf54da03f3b8d5b217078decbf69.js
156 ms
www.eli.org
241 ms
tDb3B5cmlnaHQgMjAwOSBieSBEYW5pZWwgSm9obnNvbi4gIFJlbGVhc2VkIHVuZGVyIHRoZSB0ZXJtcyBvZiB0aGUgT3BlbiBGb250IExpY2Vuc2UuIEtheWFoIExpIGdseXBocyBhcmUgcmVsZWFzZWQgdW5kZXIgdGhlIEdQTCB2ZXJzaW9uIDMuYmFlYzJhOTJiZmZlNTAzMiAtIHN1YnNldCBvZiBKdXJhTGlnaHRiYWVjMmE5MmJmZmU1MDMyIC0gc3Vic2V0IG9mIEZvbnRGb3JnZSAyLjAgOiBKdXJhIExpZ2h0IDogMjMtMS0yMDA5YmFlYzJhOTJiZmZlNTAzMiAtIHN1YnNldCBvZiBKdXJhIExpZ2h0VmVyc2lvbiAyIGJhZWMyYTkyYmZmZTUwMzIgLSBzdWJzZXQgb2YgSnVyYUxpZ2h0aHR0cDovL3NjcmlwdHMuc2lsLm9yZy9PRkwAQwBvAHAAeQByAGkAZwBoAHQAIAAyADAAMAA5ACAAYgB5ACAARABhAG4AaQBlAGwAIABKAG8AaABuAHMAbwBuAC4AIAAgAFIAZQBsAGUAYQBzAGUAZAAgAHUAbgBkAGUAcgAgAHQAaABlACAAdABlAHIAbQBzACAAbwBmACAAdABoAGUAIABPAHAAZQBuACAARgBvAG4AdAAgAEwAaQBjAGUAbgBzAGUALgAgAEsAYQB5AGEAaAAgAEwAaQAgAGcAbAB5AHAAaABzACAAYQByAGUAIAByAGUAbABlAGEAcwBlAGQAIAB1AG4AZABlAHIAIAB0AGgAZQAgAEcAUABMACAAdgBlAHIAcwBpAG8AbgAgADMALgBiAGEAZQBjADIAYQA5ADIAYgBmAGYAZQA1ADAAMwAyACAALQAgAHMAdQBiAHMAZQB0ACAAbwBmACAASgB1AHIAYQBMAGkAZwBoAHQAYgBhAGUAYwAyAGEAOQAyAGIAZgBmAGUANQAwADMAMgAgAC0AIABzAHUAYgBzAGUAdAAgAG8AZgAgAEYAbwBuAHQARgBvAHIAZwBlACAAMgAuADAAIAA6ACAASgB1AHIAYQAgAEwAaQBnAGgAdAAgADoAIAAyADMALQAxAC0AMgAwADAAOQBiAGEAZQBjADIAYQA5ADIAYgBmAGYAZQA1ADAAMwAyACAALQAgAHMAdQBiAHMAZQB0ACAAbwBmACAASgB1AHIAYQAgAEwAaQBnAGgAdABWAGUAcgBzAGkAbwBuACAAMgAgAGIAYQBlAGMAMgBhADkAMgBiAGYAZgBlADUAMAAzADIAIAAtACAAcwB1AGIAcwBlAHQAIABvAGYAIABKAHUAcgBhAEwAaQBnAGgAdABoAHQAdABwADoALwAvAHMAYwByAGkAcAB0AHMALgBzAGkAbAAuAG8AcgBnAC8ATwBGAEwAAAAAAgAAAAAAAP+BADMAAAAAAAAAAAAAAAAAAAAAAAAAAAAFAAAAAQACAQIAEQt6ZXJva2F5YWhsaQ==
0 ms
css_d3808fccad1687bc50b7c644a873cb31.css
70 ms
adaptive_eli_logo.png
89 ms
cpp.png
397 ms
afdb_report.png
430 ms
february_2016_fa_elr.png
674 ms
nwn_radar_remote_sensing_of_the_louisiana_wetlands.png
666 ms
2016_environmental_achievement_award_winner.png
797 ms
eli_interior_2_of_5.jpg
526 ms
mexwright7.jpg
880 ms
jan.feb_.png
913 ms
biloxi.jpg
1002 ms
homepageimage.jpg
988 ms
blackburn_2nd_0.png
805 ms
houckmehan_3d_cover.png
886 ms
elr-footer-logo.png
886 ms
menu-expanded.png
743 ms
right-white-arrow.png
748 ms
menu-leaf.png
746 ms
search-icon.png
777 ms
menu-right-arrow.png
808 ms
header-border.png
839 ms
press-release-icon.png
848 ms
cal-icon.png
836 ms
footer-bg.png
1286 ms
social-links.png
899 ms
ga.js
1022 ms
300lo.json
125 ms
loading_animation.gif
726 ms
controls.png
744 ms
left-slide-arrow.png
781 ms
right-slide-arrow.png
792 ms
logo-reverse.png
813 ms
sh.7c7179124ea24ac6ba46caac.html
39 ms
Yv7ms4hdMYep0F502UT2DQkkj9O-O7pao9NHzK_dsyGffHkqgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
95 ms
TKw-0clyyNKfnph0s32P52BQpF9jHDqkoPPAwh3kEo3ffOeqgsMWeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
150 ms
FytToCtRNWMQAkKM2eCakZiczU2y_TjVJ-TLLiJ4qWwffVEgggMWeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
158 ms
fbRbenlmsIX2mKrmt3nBxPsBThWBW5iikyJAbvmdNgXffVruggMWeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
159 ms
layers.3643cb2e25fb91c29386.js
29 ms
p.gif
128 ms
__utm.gif
22 ms
eli.org 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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
eli.org 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
eli.org 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
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 Eli.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 Eli.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.
eli.org
Open Graph description is not detected on the main page of ELI. 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: