Tools & Wizards About Us
iloveafrica.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

iloveafrica.com

I Love Africa | Global African

Page Load Speed

3.6 sec in total

First Response

147 ms

Resources Loaded

2.9 sec

Page Rendered

558 ms

iloveafrica.com screenshot

About Website

Click here to check amazing I Love Africa content for Nigeria. Otherwise, check out these important facts you probably never knew about iloveafrica.com

Visit iloveafrica.com

Key Findings

We analyzed Iloveafrica.com page load time and found that the first response time was 147 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

iloveafrica.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value3,220 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

iloveafrica.com

147 ms

iloveafrica.com

935 ms

styles.css

107 ms

style.css

159 ms

style.css

160 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 58% of them (40 requests) were addressed to the original Iloveafrica.com, 17% (12 requests) were made to Fonts.gstatic.com and 12% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (935 ms) belongs to the original domain Iloveafrica.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.9 kB (32%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iloveafrica.com main page is 1.8 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. 70% of websites need less resources to load. HTML takes 605.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 518.4 kB

  • Original 605.7 kB
  • After minification 568.5 kB
  • After compression 87.2 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 518.4 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 36.6 kB

  • Original 572.7 kB
  • After minification 536.1 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. I Love Africa images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 499.2 kB
  • After minification 499.2 kB
  • After compression 498.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 9.6 kB

  • Original 82.4 kB
  • After minification 82.4 kB
  • After compression 72.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. Iloveafrica.com needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (74%)

Requests Now

54

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iloveafrica.com

iloveafrica.com

147 ms

iloveafrica.com

iloveafrica.com

935 ms

styles.css

styles.css

107 ms

style.css

style.css

159 ms

style.css

style.css

160 ms

css

css

47 ms

tds-front.css

tds-front.css

161 ms

open-iconic.css

open-iconic.css

166 ms

font-awesome.css

font-awesome.css

165 ms

style.css

style.css

215 ms

td_legacy_main.css

td_legacy_main.css

266 ms

tdb_main.css

tdb_main.css

213 ms

jquery.min.js

jquery.min.js

276 ms

jquery-migrate.min.js

jquery-migrate.min.js

222 ms

js

js

84 ms

adsbygoogle.js

adsbygoogle.js

170 ms

pub-7983531510553911

pub-7983531510553911

96 ms

adsbygoogle.js

adsbygoogle.js

157 ms

hooks.min.js

hooks.min.js

166 ms

i18n.min.js

i18n.min.js

220 ms

index.js

index.js

355 ms

index.js

index.js

355 ms

tracker.js

tracker.js

355 ms

tagdiv_theme.min.js

tagdiv_theme.min.js

443 ms

tdPostImages.js

tdPostImages.js

442 ms

tdSocialSharing.js

tdSocialSharing.js

443 ms

tdModalPostImages.js

tdModalPostImages.js

444 ms

comment-reply.min.js

comment-reply.min.js

443 ms

underscore.min.js

underscore.min.js

444 ms

js_files_for_front.min.js

js_files_for_front.min.js

444 ms

js_files_for_front.min.js

js_files_for_front.min.js

445 ms

tdToTop.js

tdToTop.js

444 ms

tdLoginMobile.js

tdLoginMobile.js

444 ms

tdAjaxSearch.js

tdAjaxSearch.js

445 ms

tdbMenu.js

tdbMenu.js

445 ms

tdbSearch.js

tdbSearch.js

444 ms

tdMenu.js

tdMenu.js

445 ms

tdTrendingNow.js

tdTrendingNow.js

445 ms

tdLoadingBox.js

tdLoadingBox.js

446 ms

tdSmartSidebar.js

tdSmartSidebar.js

445 ms

pub-7983531510553911

pub-7983531510553911

208 ms

africa-5-1.png

africa-5-1.png

193 ms

202201098838d7e0-0fbb-181e-8ab6-370d7fb9f2ba.jpg

202201098838d7e0-0fbb-181e-8ab6-370d7fb9f2ba.jpg

411 ms

show_ads_impl.js

show_ads_impl.js

351 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ViesC.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ViesC.ttf

66 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ViesC.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ViesC.ttf

321 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekViesC.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekViesC.ttf

203 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

206 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

206 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

206 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

206 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

205 ms

va9b4kzIxd1KFppkaRKvDRPJVDf_FRjekGrW.ttf

va9b4kzIxd1KFppkaRKvDRPJVDf_FRjekGrW.ttf

207 ms

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

207 ms

newspaper.woff

newspaper.woff

201 ms

elements.png

elements.png

100 ms

zrt_lookup.html

zrt_lookup.html

62 ms

20220109d4ba9e06-924d-0630-44ee-2bfed2261d99.jpg

20220109d4ba9e06-924d-0630-44ee-2bfed2261d99.jpg

246 ms

ads

ads

658 ms

ads

ads

356 ms

ads

ads

561 ms

ads

ads

478 ms

ads

ads

424 ms

ads

ads

262 ms

ads

ads

316 ms

reactive_library.js

reactive_library.js

152 ms

ca-pub-7983531510553911

ca-pub-7983531510553911

93 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

25 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

24 ms

Accessibility Review

iloveafrica.com accessibility score

97

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.

Best Practices

iloveafrica.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

iloveafrica.com SEO score

83

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

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 Iloveafrica.com 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 Iloveafrica.com 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

iloveafrica.com

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