Tools & Wizards About Us
yeel.app screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

yeel.app

Yeel - Mobile Payment Platform for Africa and the Middle East

Page Load Speed

2.5 sec in total

First Response

224 ms

Resources Loaded

1.6 sec

Page Rendered

611 ms

yeel.app screenshot

About Website

Visit yeel.app now to see the best up-to-date Yeel content for India and also check out these interesting facts you probably never knew about yeel.app

Yeel is enabling sending money from anywhere to Africa and Middle East including Somalia, Somaliland, Kenya, Djibouti, Ethiopia, Sudan, Tanzania, Uganda, South Sudan.

Visit yeel.app

Key Findings

We analyzed Yeel.app page load time and found that the first response time was 224 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

yeel.app performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.2 s

61/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

yeel.app

224 ms

www.yeel.io

433 ms

style.css

270 ms

responsive.css

275 ms

jquery-3.6.0.min.js

24 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Yeel.app, 85% (47 requests) were made to Yeel.io and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (679 ms) relates to the external source Yeel.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 636.2 kB (35%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yeel.app 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 12.4 kB

  • Original 16.3 kB
  • After minification 12.4 kB
  • After compression 3.8 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 3.8 kB, which is 24% 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 12.4 kB or 76% of the original size.

Image Optimization

-22%

Potential reduce by 313.3 kB

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

JavaScript Optimization

-70%

Potential reduce by 953 B

  • Original 1.4 kB
  • After minification 824 B
  • After compression 414 B

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 953 B or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 309.5 kB

  • Original 351.2 kB
  • After minification 314.4 kB
  • After compression 41.7 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. Yeel.app needs all CSS files to be minified and compressed as it can save up to 309.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (32%)

Requests Now

50

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yeel.app

yeel.app

224 ms

www.yeel.io

www.yeel.io

433 ms

style.css

style.css

270 ms

responsive.css

responsive.css

275 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

24 ms

bootstrap.min.js

bootstrap.min.js

28 ms

custom.js

custom.js

137 ms

logo.svg

logo.svg

207 ms

google-play.svg

google-play.svg

209 ms

apple-store.svg

apple-store.svg

276 ms

phone.png

phone.png

410 ms

p1.png

p1.png

270 ms

p2.png

p2.png

276 ms

p3.png

p3.png

279 ms

img1.png

img1.png

549 ms

img2.png

img2.png

474 ms

map.png

map.png

477 ms

w1.png

w1.png

342 ms

w2.png

w2.png

347 ms

w3.png

w3.png

410 ms

01.png

01.png

483 ms

w4.png

w4.png

476 ms

w5.png

w5.png

477 ms

w6.png

w6.png

541 ms

r1.png

r1.png

545 ms

r2.png

r2.png

544 ms

r3.png

r3.png

545 ms

mp1.png

mp1.png

550 ms

mp2.png

mp2.png

609 ms

mp3.png

mp3.png

612 ms

footer-logo.svg

footer-logo.svg

611 ms

YeelISOLogo.svg

YeelISOLogo.svg

679 ms

F.svg

F.svg

615 ms

T.svg

T.svg

617 ms

I.svg

I.svg

677 ms

css

css

33 ms

bootstrap.min.css

bootstrap.min.css

10 ms

bootstrap-select.min.css

bootstrap-select.min.css

489 ms

flaticon.css

flaticon.css

490 ms

owl.carousel.css

owl.carousel.css

489 ms

owl.theme.default.min.css

owl.theme.default.min.css

490 ms

nouislider.css

nouislider.css

545 ms

nouislider.pips.css

nouislider.pips.css

547 ms

jquery.bootstrap-touchspin.css

jquery.bootstrap-touchspin.css

544 ms

magnific-popup.css

magnific-popup.css

542 ms

swiper.css

swiper.css

545 ms

jquery.bxslider.min.css

jquery.bxslider.min.css

545 ms

animate.min.css

animate.min.css

546 ms

hover-min.css

hover-min.css

608 ms

fontawesome-all.min.css

fontawesome-all.min.css

541 ms

slider-bg.svg

slider-bg.svg

70 ms

black.png

black.png

71 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1Uj.woff

15 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5Xs1Uj.woff

25 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1Uj.woff

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1Uj.woff

35 ms

Accessibility Review

yeel.app accessibility score

85

Accessibility Issues

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

Links do not have a discernible name

Best Practices

yeel.app best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

yeel.app SEO score

89

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

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

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 Yeel.app 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 Yeel.app 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

yeel.app

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