Tools & Wizards About Us
aye.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

aye.com

FECorpHome

Page Load Speed

1.4 sec in total

First Response

23 ms

Resources Loaded

838 ms

Page Rendered

491 ms

aye.com screenshot

About Website

Click here to check amazing Aye content for India. Otherwise, check out these important facts you probably never knew about aye.com

Firstenergy

Visit aye.com

Key Findings

We analyzed Aye.com page load time and found that the first response time was 23 ms and then it took 1.3 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.

Performance Metrics

aye.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value4,050 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.19

65/100

15%

TTI (Time to Interactive)

Value28.7 s

0/100

10%

Network Requests Diagram

fehome.html

23 ms

font-awesome.min.css

14 ms

jquery.faloading.css

18 ms

datatables.min.css

21 ms

slick-theme.css

16 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Aye.com, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (518 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (23%)

Content Size

5.7 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aye.com main page is 5.7 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. Only a small number of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 84.7 kB

  • Original 95.4 kB
  • After minification 70.1 kB
  • After compression 10.7 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 25.3 kB, which is 27% 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 84.7 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 46.4 kB

  • Original 4.2 MB
  • After minification 4.1 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. Aye images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 778.0 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 237.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 778.0 kB or 77% of the original size.

CSS Optimization

-86%

Potential reduce by 387.3 kB

  • Original 452.9 kB
  • After minification 446.3 kB
  • After compression 65.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. Aye.com needs all CSS files to be minified and compressed as it can save up to 387.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (36%)

Requests Now

61

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fehome.html

fehome.html

23 ms

font-awesome.min.css

font-awesome.min.css

14 ms

jquery.faloading.css

jquery.faloading.css

18 ms

datatables.min.css

datatables.min.css

21 ms

slick-theme.css

slick-theme.css

16 ms

slick.css

slick.css

13 ms

style.css

style.css

38 ms

vendor.css

vendor.css

28 ms

static.css

static.css

18 ms

resources.css

resources.css

18 ms

jquery.min.js

jquery.min.js

25 ms

what-input.min.js

what-input.min.js

21 ms

foundation-6.7.5.min.js

foundation-6.7.5.min.js

137 ms

handlebars-v4.0.5.min.js

handlebars-v4.0.5.min.js

33 ms

jquery.faloading.min.js

jquery.faloading.min.js

33 ms

jquery.mask.min.js

jquery.mask.min.js

33 ms

typeahead.bundle.min.js

typeahead.bundle.min.js

34 ms

moment-2.29.4.min.js

moment-2.29.4.min.js

132 ms

foundation-datepicker.min.js

foundation-datepicker.min.js

131 ms

foundation-datepicker.min.css

foundation-datepicker.min.css

134 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

131 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

132 ms

slick.min.js

slick.min.js

134 ms

app.all.min.js

app.all.min.js

132 ms

gtm.js

gtm.js

518 ms

blank.png

blank.png

441 ms

icon-account.png

icon-account.png

439 ms

invest.png

invest.png

441 ms

hand.png

hand.png

436 ms

safety.png

safety.png

439 ms

contact.png

contact.png

439 ms

HomePageOutageIconBlue.svg

HomePageOutageIconBlue.svg

443 ms

HomePagePaymentIconBlue.svg

HomePagePaymentIconBlue.svg

444 ms

HomePageMovingIconBlue.svg

HomePageMovingIconBlue.svg

440 ms

icon-corporate-account.png

icon-corporate-account.png

445 ms

icon-corporate-bill.png

icon-corporate-bill.png

446 ms

icon-outage-bolt.png

icon-outage-bolt.png

446 ms

icon-corporate-service.png

icon-corporate-service.png

444 ms

icon-corporate-moving.png

icon-corporate-moving.png

445 ms

E365-promo-final-940-x-520.png

E365-promo-final-940-x-520.png

453 ms

Stop-Look-Live-Street-Scene-940-x-520-2020-promo-v2.jpg

Stop-Look-Live-Street-Scene-940-x-520-2020-promo-v2.jpg

447 ms

corporate-responsibility-940x520.jpg

corporate-responsibility-940x520.jpg

448 ms

lineman1-940x520.jpg

lineman1-940x520.jpg

449 ms

products-smartmart-940x520.jpg

products-smartmart-940x520.jpg

447 ms

EV-Driven-940-x-520-2023-4.jpg

EV-Driven-940-x-520-2023-4.jpg

450 ms

weather-heat-thermometer-940x520-1.jpg

weather-heat-thermometer-940x520-1.jpg

448 ms

jcpl-logo-940x520.jpg

jcpl-logo-940x520.jpg

449 ms

Rao,nikhil_940x520.jpg

Rao,nikhil_940x520.jpg

455 ms

Avila,stephen_940x520.jpg

Avila,stephen_940x520.jpg

452 ms

mon-power-logo-940x520.jpg

mon-power-logo-940x520.jpg

454 ms

fe.png

fe.png

450 ms

FoundationSans-Roman-webfont.woff

FoundationSans-Roman-webfont.woff

437 ms

FoundationSans-Bold-webfont.woff

FoundationSans-Bold-webfont.woff

317 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

318 ms

FoundationSans-Light-webfont.woff

FoundationSans-Light-webfont.woff

316 ms

fe.png

fe.png

108 ms

logo-corporate.png

logo-corporate.png

109 ms

stay-connected-2_right-face_gradient_1366x575.jpg

stay-connected-2_right-face_gradient_1366x575.jpg

115 ms

BA_Ginger_gradient_1366x575.jpg

BA_Ginger_gradient_1366x575.jpg

113 ms

good-energy-1_gradient_1366x575.jpg

good-energy-1_gradient_1366x575.jpg

113 ms

reliability-2_gradient_1366x575.jpg

reliability-2_gradient_1366x575.jpg

114 ms

arrow-slider-prev.png

arrow-slider-prev.png

109 ms

ajax-loader.gif

ajax-loader.gif

107 ms

arrow-slider-next.png

arrow-slider-next.png

108 ms

arrow-twitterSlider-prev.png

arrow-twitterSlider-prev.png

108 ms

arrow-twitterSlider-next.png

arrow-twitterSlider-next.png

108 ms

Accessibility Review

aye.com accessibility score

98

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

aye.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

aye.com SEO score

75

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 Aye.com 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 Aye.com 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

aye.com

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