Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

isge-bf.org

ISGE BF

Page Load Speed

6.6 sec in total

First Response

1.3 sec

Resources Loaded

5 sec

Page Rendered

343 ms

isge-bf.org screenshot

About Website

Click here to check amazing ISGE BF content for Burkina Faso. Otherwise, check out these important facts you probably never knew about isge-bf.org

Visit isge-bf.org

Key Findings

We analyzed Isge-bf.org page load time and found that the first response time was 1.3 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

isge-bf.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.41

24/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

www.isge-bf.org

1304 ms

fblb.css

178 ms

styles.css

171 ms

jquery.js

337 ms

userscripts.js

171 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 89% of them (116 requests) were addressed to the original Isge-bf.org, 4% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Isge-bf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 338.0 kB (23%)

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Isge-bf.org main page is 1.5 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 41.9 kB

  • Original 52.5 kB
  • After minification 50.6 kB
  • After compression 10.5 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 41.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 46.7 kB

  • Original 1.1 MB
  • After minification 1.0 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. ISGE BF images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 151.7 kB

  • Original 224.3 kB
  • After minification 222.9 kB
  • After compression 72.7 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 151.7 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 97.7 kB

  • Original 117.9 kB
  • After minification 93.6 kB
  • After compression 20.2 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. Isge-bf.org needs all CSS files to be minified and compressed as it can save up to 97.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (47%)

Requests Now

125

After Optimization

66

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

Accessibility Review

isge-bf.org accessibility score

65

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

isge-bf.org best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

isge-bf.org SEO score

77

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Isge-bf.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Isge-bf.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 ISGE BF. 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: