Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

foag.org

FOAG - Farmers Overseas Action Group

Page Load Speed

2.6 sec in total

First Response

185 ms

Resources Loaded

2.2 sec

Page Rendered

225 ms

foag.org screenshot

About Website

Visit foag.org now to see the best up-to-date FOAG content and also check out these interesting facts you probably never knew about foag.org

Farmers Overseas Action Group (FOAG) is an independent charity founded in 1981. We help improve the social and economic development of Uganda’s rural communities.

Visit foag.org

Key Findings

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

Performance Metrics

foag.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.39

0/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

home

185 ms

css

24 ms

css

36 ms

style.css

335 ms

jquery.fancybox.css

253 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 86% of them (37 requests) were addressed to the original Foag.org, 5% (2 requests) were made to Fonts.googleapis.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.1 sec) belongs to the original domain Foag.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.5 kB (20%)

Content Size

826.3 kB

After Optimization

662.8 kB

In fact, the total size of Foag.org main page is 826.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 593.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 9.6 kB

  • Original 12.5 kB
  • After minification 10.1 kB
  • After compression 2.9 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 2.4 kB, which is 19% 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 9.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 9.0 kB

  • Original 593.5 kB
  • After minification 584.5 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. FOAG images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 120.3 kB

  • Original 189.9 kB
  • After minification 166.9 kB
  • After compression 69.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 120.3 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 24.6 kB

  • Original 30.3 kB
  • After minification 23.6 kB
  • After compression 5.8 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. Foag.org needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (45%)

Requests Now

40

After Optimization

22

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

Accessibility Review

foag.org accessibility score

87

Accessibility Issues

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

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

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

foag.org SEO score

82

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foag.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 Foag.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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