Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tegemeo.org

Tegemeo Institute of Agricultural Policy and Development

Page Load Speed

40 sec in total

First Response

454 ms

Resources Loaded

38.1 sec

Page Rendered

1.5 sec

tegemeo.org screenshot

About Website

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

Tegemeo Institute of Agricultural Policy and Development is a policy research institute under the Division of Research and Extension of Egerton University.

Visit tegemeo.org

Key Findings

We analyzed Tegemeo.org page load time and found that the first response time was 454 ms and then it took 39.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

tegemeo.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value50.8 s

0/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

tegemeo.org

454 ms

tegemeo.org

1977 ms

beed4c1f08d83b15cf87c4d42d4916ee.css

1509 ms

8b0c627161cbca47783d456569aa41e1.css

656 ms

c71c4a9fffb06bf7339142c06cf4ff84.css

871 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Tegemeo.org, 2% (1 request) were made to Res.cloudinary.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Tegemeo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (28%)

Content Size

3.6 MB

After Optimization

2.6 MB

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

HTML Optimization

-85%

Potential reduce by 105.9 kB

  • Original 124.3 kB
  • After minification 123.4 kB
  • After compression 18.4 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 105.9 kB or 85% of the original size.

Image Optimization

-26%

Potential reduce by 921.8 kB

  • Original 3.5 MB
  • After minification 2.6 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. Obviously, Tegemeo needs image optimization as it can save up to 921.8 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 13 (25%)

Requests Now

52

After Optimization

39

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

Accessibility Review

tegemeo.org accessibility score

88

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

High

ARIA progressbar elements do not have accessible names.

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

tegemeo.org best practices score

67

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

Browser errors were logged to the console

SEO Factors

tegemeo.org SEO score

83

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