Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

forefdn.org

Home | Foundation for Opioid Response Efforts (FORE)

Page Load Speed

1.9 sec in total

First Response

140 ms

Resources Loaded

947 ms

Page Rendered

769 ms

forefdn.org screenshot

About Website

Click here to check amazing FORE Fdn content. Otherwise, check out these important facts you probably never knew about forefdn.org

FORE is a national, private, grantmaking foundation focused solely on inspiring and accelerating action to end the nation’s opioid epidemic.

Visit forefdn.org

Key Findings

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

Performance Metrics

forefdn.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

forefdn.org

140 ms

forefdn.org

221 ms

style.min.css

21 ms

styles.css

24 ms

ctf-styles.min.css

25 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Forefdn.org, 4% (2 requests) were made to Pbs.twimg.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (401 ms) relates to the external source Pbs.twimg.com.

Page Optimization Overview & Recommendations

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

Content Size

4.1 MB

After Optimization

4.0 MB

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

HTML Optimization

-82%

Potential reduce by 64.3 kB

  • Original 78.4 kB
  • After minification 71.1 kB
  • After compression 14.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 64.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.7 MB
  • After minification 3.7 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. FORE Fdn images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 9.8 kB

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

CSS Optimization

-4%

Potential reduce by 2.0 kB

  • Original 49.0 kB
  • After minification 49.0 kB
  • After compression 47.0 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. Forefdn.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (48%)

Requests Now

42

After Optimization

22

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

Accessibility Review

forefdn.org accessibility score

87

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

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.

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

forefdn.org SEO score

90

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

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