Tools & Wizards About Us
ehai.org screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ehai.org

Elkhart Housing Authority - Rental Assistance, Suitable Housing, Rental Assistance Programs

Page Load Speed

1.4 sec in total

First Response

44 ms

Resources Loaded

1.2 sec

Page Rendered

129 ms

ehai.org screenshot

About Website

Welcome to ehai.org homepage info - get ready to check Ehai best content right away, or after learning these important things about ehai.org

Elkhart Housing Authority rental assistance programs offer two low income assistance programs. Please visit our web page for income eligibility information.

Visit ehai.org

Key Findings

We analyzed Ehai.org page load time and found that the first response time was 44 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

ehai.org performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.205

60/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

www.ehai.org

44 ms

font-awesome.min.css

36 ms

site.css

16 ms

duel.js

28 ms

scc-c2.min.js

23 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ehai.org, 25% (14 requests) were made to P3pprd001.cloudstorage.secureserver.net and 25% (14 requests) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (491 ms) relates to the external source P3pprd001.cloudstorage.secureserver.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.2 kB (2%)

Content Size

11.4 MB

After Optimization

11.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 55.5 kB

  • Original 71.3 kB
  • After minification 71.3 kB
  • After compression 15.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. 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 55.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 16.6 kB

  • Original 11.0 MB
  • After minification 11.0 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. Ehai images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 72.3 kB

  • Original 173.1 kB
  • After minification 172.7 kB
  • After compression 100.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 72.3 kB or 42% of the original size.

CSS Optimization

-83%

Potential reduce by 106.7 kB

  • Original 128.0 kB
  • After minification 127.9 kB
  • After compression 21.2 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. Ehai.org needs all CSS files to be minified and compressed as it can save up to 106.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (58%)

Requests Now

50

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ehai.org

www.ehai.org

44 ms

font-awesome.min.css

font-awesome.min.css

36 ms

site.css

site.css

16 ms

duel.js

duel.js

28 ms

scc-c2.min.js

scc-c2.min.js

23 ms

jq.js

jq.js

491 ms

subNavigation.js

subNavigation.js

344 ms

1854f40022f7d15b9dfda01fe2f196c6

1854f40022f7d15b9dfda01fe2f196c6

34 ms

media.gallery.js

media.gallery.js

344 ms

facebookSDKHelper.js

facebookSDKHelper.js

339 ms

cookiemanager.js

cookiemanager.js

340 ms

iebackground.js

iebackground.js

338 ms

5dd4392f7e0c4a5edab518f0ad93d6b4

5dd4392f7e0c4a5edab518f0ad93d6b4

23 ms

e93d624c44f081bf1e7bb18d49fad108

e93d624c44f081bf1e7bb18d49fad108

23 ms

babbf16aa42e37fcf6af6e57a6d86be9

babbf16aa42e37fcf6af6e57a6d86be9

51 ms

86077c048003fb596ca5a1dab7b34f77

86077c048003fb596ca5a1dab7b34f77

21 ms

380fb145a65839369879c911b273f207

380fb145a65839369879c911b273f207

27 ms

8ca37422922119c4a2638f504fddcb3d

8ca37422922119c4a2638f504fddcb3d

24 ms

6483192da574bd3bb1268212b5ccb767

6483192da574bd3bb1268212b5ccb767

24 ms

943a8267bccbfa109e93c0798a4fc0c2

943a8267bccbfa109e93c0798a4fc0c2

24 ms

11hPGpDKz1rGb3dkFE8.woff

11hPGpDKz1rGb3dkFE8.woff

17 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

7 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

15 ms

_Xmr-H4zszafZw3A-KPSZut9wQiX.woff

_Xmr-H4zszafZw3A-KPSZut9wQiX.woff

15 ms

9oRPNYsQpS4zjuA_iwgQ.woff

9oRPNYsQpS4zjuA_iwgQ.woff

15 ms

vm8vdRfvXFLG3OLnsO15WYS5DG74wNQ.woff

vm8vdRfvXFLG3OLnsO15WYS5DG74wNQ.woff

16 ms

util.fbSDKLoader.js

util.fbSDKLoader.js

56 ms

util.window.js

util.window.js

55 ms

util.instances.js

util.instances.js

62 ms

util.model.js

util.model.js

55 ms

documentHelper.js

documentHelper.js

55 ms

helper.js

helper.js

59 ms

growl.js

growl.js

55 ms

sf.core.pkg.js

sf.core.pkg.js

27 ms

browser.js

browser.js

57 ms

app.css

app.css

25 ms

dafc818b9e5c0839f5907642044e1b26

dafc818b9e5c0839f5907642044e1b26

27 ms

sdk.js

sdk.js

26 ms

ecf5e1760e62205395f7146cf1d9058e

ecf5e1760e62205395f7146cf1d9058e

60 ms

f74b23384bb28439bcd1fb48e4d3bb3a

f74b23384bb28439bcd1fb48e4d3bb3a

71 ms

7f16d9a1e8b18a3935db67c729ede676

7f16d9a1e8b18a3935db67c729ede676

73 ms

7bf07720a9a7d4dcdcf7c234dea9d943

7bf07720a9a7d4dcdcf7c234dea9d943

58 ms

sdk.js

sdk.js

15 ms

48 ms

page.php

page.php

219 ms

YSVNzQMiK3c.css

YSVNzQMiK3c.css

15 ms

_tdn2SGo1cv.js

_tdn2SGo1cv.js

23 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

54 ms

Mw5y7Z3v-mj.js

Mw5y7Z3v-mj.js

55 ms

pLoSlJD7y1F.js

pLoSlJD7y1F.js

58 ms

Glud--w-qOK.js

Glud--w-qOK.js

64 ms

_eawcKGGOQC.js

_eawcKGGOQC.js

56 ms

p55HfXW__mM.js

p55HfXW__mM.js

56 ms

256307081_105588495275617_6592450246362484760_n.jpg

256307081_105588495275617_6592450246362484760_n.jpg

155 ms

255271589_105587631942370_1668513671996825055_n.jpg

255271589_105587631942370_1668513671996825055_n.jpg

97 ms

Dpom1HQzAgH.js

Dpom1HQzAgH.js

9 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

6 ms

Accessibility Review

ehai.org accessibility score

52

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

ehai.org best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ehai.org SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

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

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 Ehai.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 Ehai.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

ehai.org

Open Graph data is detected on the main page of Ehai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: