Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

cfee.net

HOME | CFEE | California nonprofit policy institution

Page Load Speed

3.5 sec in total

First Response

545 ms

Resources Loaded

2.9 sec

Page Rendered

68 ms

cfee.net screenshot

About Website

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

The California Foundation on the Environment and the Economy (CFEE), a nonprofit policy institution, has connected labor, business, local government and environmental leaders to facilitate productive ...

Visit cfee.net

Key Findings

We analyzed Cfee.net page load time and found that the first response time was 545 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

cfee.net performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

www.cfee.net

545 ms

minified.js

29 ms

focus-within-polyfill.js

26 ms

polyfill.min.js

1069 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

59 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cfee.net, 37% (14 requests) were made to Static.parastorage.com and 32% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 655.0 kB (59%)

Content Size

1.1 MB

After Optimization

464.6 kB

In fact, the total size of Cfee.net main page is 1.1 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. HTML takes 670.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 526.1 kB

  • Original 670.2 kB
  • After minification 668.5 kB
  • After compression 144.1 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 526.1 kB or 78% of the original size.

Image Optimization

-31%

Potential reduce by 36.5 kB

  • Original 116.2 kB
  • After minification 79.7 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. Obviously, CFEE needs image optimization as it can save up to 36.5 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 92.5 kB

  • Original 333.3 kB
  • After minification 333.3 kB
  • After compression 240.8 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 92.5 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

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

Accessibility Review

cfee.net 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

cfee.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

cfee.net SEO score

97

Search Engine Optimization Advices

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 Cfee.net 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 Cfee.net 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 data is detected on the main page of CFEE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: