Tools & Wizards About Us
eweb.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

eweb.org

Home | EWEB

Page Load Speed

3.8 sec in total

First Response

233 ms

Resources Loaded

3.3 sec

Page Rendered

312 ms

eweb.org screenshot

About Website

Visit eweb.org now to see the best up-to-date EWEB content for United States and also check out these interesting facts you probably never knew about eweb.org

Eugene Water & Electric Board (EWEB) is a publicly-owned water and electric utility in Eugene, Oregon.

Visit eweb.org

Key Findings

We analyzed Eweb.org page load time and found that the first response time was 233 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

eweb.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.372

28/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

eweb.org

233 ms

eweb.org

453 ms

www.eweb.org

513 ms

css

39 ms

boilerplateResets.css

86 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 75% of them (30 requests) were addressed to the original Eweb.org, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Eweb.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.2 kB (1%)

Content Size

22.9 MB

After Optimization

22.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 78.6 kB

  • Original 86.3 kB
  • After minification 45.9 kB
  • After compression 7.6 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 40.4 kB, which is 47% 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 78.6 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 155.7 kB

  • Original 22.7 MB
  • After minification 22.5 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. EWEB images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 17.6 kB

  • Original 96.0 kB
  • After minification 96.0 kB
  • After compression 78.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 17.6 kB or 18% of the original size.

CSS Optimization

-36%

Potential reduce by 14.3 kB

  • Original 39.8 kB
  • After minification 39.8 kB
  • After compression 25.5 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. Eweb.org needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (56%)

Requests Now

34

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eweb.org

eweb.org

233 ms

eweb.org

eweb.org

453 ms

www.eweb.org

www.eweb.org

513 ms

css

css

39 ms

boilerplateResets.css

boilerplateResets.css

86 ms

bootstrapColumns.css

bootstrapColumns.css

173 ms

font-awesome.min.css

font-awesome.min.css

261 ms

main.css

main.css

400 ms

flexslider.css

flexslider.css

325 ms

magnific-popup.css

magnific-popup.css

322 ms

slick.css

slick.css

325 ms

igx-dev.css

igx-dev.css

320 ms

jQuery_2.2.4.js

jQuery_2.2.4.js

432 ms

siteScripts.js

siteScripts.js

408 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

409 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

407 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

409 ms

slick.min.js

slick.min.js

481 ms

element.js

element.js

53 ms

js

js

66 ms

hotjar-2253147.js

hotjar-2253147.js

195 ms

EWEBMainLogo.png

EWEBMainLogo.png

169 ms

water-filtration-employee-at-plant-darkened.jpg

water-filtration-employee-at-plant-darkened.jpg

324 ms

electric_substation_currin_2.jpg

electric_substation_currin_2.jpg

653 ms

Thermostat%20Banner_3photos.png

Thermostat%20Banner_3photos.png

1580 ms

staff-at-picnic.jpg

staff-at-picnic.jpg

417 ms

Carmen%20Smith%20Powerhouse.jpg

Carmen%20Smith%20Powerhouse.jpg

387 ms

wards-map-dark-filter.jpg

wards-map-dark-filter.jpg

250 ms

construction%20on%20currin%20substation.jpeg

construction%20on%20currin%20substation.jpeg

493 ms

e40th_1_20221209.jpg

e40th_1_20221209.jpg

522 ms

rebates-loans-tile.jpg

rebates-loans-tile.jpg

650 ms

join-email-list-highlight.jpg

join-email-list-highlight.jpg

684 ms

Rely_On_Us_Logo%403x.png

Rely_On_Us_Logo%403x.png

576 ms

analytics.js

analytics.js

98 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

454 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

31 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

39 ms

modules.e5979922753cf3b8b069.js

modules.e5979922753cf3b8b069.js

33 ms

collect

collect

17 ms

js

js

47 ms

Accessibility Review

eweb.org accessibility score

90

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-hidden="true"] elements contain focusable descendents

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

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

eweb.org best practices score

83

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

SEO Factors

eweb.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 Eweb.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 Eweb.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

eweb.org

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