Report Summary

  • 0

    Performance

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

efi.org

AM Conservation

Page Load Speed

1.3 sec in total

First Response

31 ms

Resources Loaded

795 ms

Page Rendered

431 ms

efi.org screenshot

About Website

Click here to check amazing Efi content for India. Otherwise, check out these important facts you probably never knew about efi.org

For more than 30 years, EFI has been providing energy efficient products and delivering utility program services in order to assist people in their efforts to use less energy and water.

Visit efi.org

Key Findings

We analyzed Efi.org page load time and found that the first response time was 31 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

efi.org performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

efi.org

31 ms

efi.org

275 ms

css

60 ms

all.css

56 ms

bootstrap.css

31 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 77% of them (34 requests) were addressed to the original Efi.org, 7% (3 requests) were made to Use.fontawesome.com and 5% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Efi.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.2 kB (5%)

Content Size

2.8 MB

After Optimization

2.6 MB

In fact, the total size of Efi.org main page is 2.8 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. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 36.2 kB

  • Original 45.0 kB
  • After minification 35.0 kB
  • After compression 8.8 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. This page needs HTML code to be minified as it can gain 10.0 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.2 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 93.9 kB

  • Original 2.7 MB
  • After minification 2.6 MB

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. Efi images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 30 B

  • Original 19.0 kB
  • After minification 19.0 kB
  • After compression 19.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 3.1 kB

  • Original 54.9 kB
  • After minification 54.8 kB
  • After compression 51.8 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. Efi.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (64%)

Requests Now

39

After Optimization

14

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Efi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

efi.org accessibility score

81

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

efi.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

efi.org SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efi.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 Efi.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Efi. 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: