Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

afrima.org

Africa's Global Music Awards

Page Load Speed

17.3 sec in total

First Response

1.1 sec

Resources Loaded

14.9 sec

Page Rendered

1.2 sec

afrima.org screenshot

About Website

Click here to check amazing Afrima content for Nigeria. Otherwise, check out these important facts you probably never knew about afrima.org

All Africa Music Awards (AFRIMA)

Visit afrima.org

Key Findings

We analyzed Afrima.org page load time and found that the first response time was 1.1 sec and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

afrima.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value7,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value44.6 s

0/100

10%

Network Requests Diagram

afrima.org

1090 ms

grey-border-shadow.css

205 ms

category.css

203 ms

lightbox.css

205 ms

mootools-core.js

444 ms

Our browser made a total of 261 requests to load all elements on the main page. We found that 70% of them (183 requests) were addressed to the original Afrima.org, 10% (25 requests) were made to Static.xx.fbcdn.net and 5% (12 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (11.8 sec) belongs to the original domain Afrima.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (13%)

Content Size

12.0 MB

After Optimization

10.4 MB

In fact, the total size of Afrima.org main page is 12.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 143.5 kB

  • Original 177.4 kB
  • After minification 163.3 kB
  • After compression 33.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. 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 143.5 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 403.4 kB

  • Original 10.5 MB
  • After minification 10.1 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. Afrima images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 597.4 kB

  • Original 844.1 kB
  • After minification 805.9 kB
  • After compression 246.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 597.4 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 411.8 kB

  • Original 486.6 kB
  • After minification 449.6 kB
  • After compression 74.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. Afrima.org needs all CSS files to be minified and compressed as it can save up to 411.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 86 (34%)

Requests Now

254

After Optimization

168

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

Accessibility Review

afrima.org accessibility score

70

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

Best Practices

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

High

Page has valid source maps

SEO Factors

afrima.org SEO score

75

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

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afrima.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Afrima.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 Afrima. 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: