5.3 sec in total
1.1 sec
4.1 sec
121 ms
Welcome to afraa.org homepage info - get ready to check AFRAA best content for Senegal right away, or after learning these important things about afraa.org
The African Airlines Association, abbreviated AFRAA, is a trade association of African airlines. AFRAA was founded in Accra, Ghana, in 1968.
Visit afraa.orgWe analyzed Afraa.org page load time and found that the first response time was 1.1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
afraa.org performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value14.6 s
0/100
25%
Value50.0 s
0/100
10%
Value56,330 ms
0/100
30%
Value0
100/100
15%
Value78.7 s
0/100
10%
1124 ms
52 ms
289 ms
252 ms
58 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 94% of them (64 requests) were addressed to the original Afraa.org, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Afraa.org.
Page size can be reduced by 1.1 MB (33%)
3.4 MB
2.3 MB
In fact, the total size of Afraa.org main page is 3.4 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. 20% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 69.0 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 36.7 kB, which is 48% 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 69.0 kB or 91% of the original size.
Potential reduce by 518.3 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. Obviously, AFRAA needs image optimization as it can save up to 518.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 346.9 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 346.9 kB or 69% of the original size.
Potential reduce by 184.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. Afraa.org needs all CSS files to be minified and compressed as it can save up to 184.0 kB or 82% of the original size.
Number of requests can be reduced by 22 (33%)
66
44
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AFRAA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
afraa.org
1124 ms
grid-responsive.css
52 ms
bootstrap.css
289 ms
master-866986fc87d77bcf4c46198d91f0e62e.css
252 ms
960fixed.css
58 ms
css
24 ms
gantry-custom.css
96 ms
btcontentslider.css
136 ms
modal.css
150 ms
menu-bb6af0b57d7fce74eabeffebe397c0ec.css
295 ms
mootools-core.js
406 ms
core.js
235 ms
jquery.min.js
455 ms
jquery-noconflict.js
315 ms
jquery-migrate.min.js
353 ms
k2.js
431 ms
caption.js
355 ms
browser-engines.js
431 ms
slides.js
498 ms
default.js
444 ms
jquery.easing.1.3.js
477 ms
mootools-more.js
702 ms
modal.js
506 ms
vsir.js
502 ms
ga.js
69 ms
bg.png
1051 ms
logo.png
153 ms
rss.png
53 ms
facebook.png
54 ms
twitter.png
55 ms
moduletable_h3.png
213 ms
GHI-ad.jpg
1467 ms
19.jpg
333 ms
4.jpg
354 ms
26.jpg
631 ms
22.jpg
796 ms
1.jpg
963 ms
18.jpg
1154 ms
25.jpg
1505 ms
23.jpg
1530 ms
2.jpg
1517 ms
21.jpg
1565 ms
27.jpg
1584 ms
3.jpg
1656 ms
24.jpg
1700 ms
11.jpg
1664 ms
5.jpg
1715 ms
16.jpg
1751 ms
30.jpg
1773 ms
6.jpg
1854 ms
20.jpg
1865 ms
29.jpg
1837 ms
15.jpg
1893 ms
14.jpg
1913 ms
9.jpg
1983 ms
17.jpg
2061 ms
8.jpg
2074 ms
7.jpg
2089 ms
12.jpg
2130 ms
10.jpg
2117 ms
13.jpg
2156 ms
28.jpg
2175 ms
ASC%202015%20logo.JPG
2222 ms
fontawesome-webfont.woff
2235 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
17 ms
__utm.gif
12 ms
AW_Covers.jpg
2150 ms
pagination.png
1982 ms
afraa.org accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
afraa.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
afraa.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afraa.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 Afraa.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.
afraa.org
Open Graph description is not detected on the main page of AFRAA. 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: