Tools & Wizards About Us
qelola.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

qelola.com

Qelola | A Better Way to Manage & Send Money for TKI

Page Load Speed

6.3 sec in total

First Response

969 ms

Resources Loaded

4.6 sec

Page Rendered

642 ms

qelola.com screenshot

About Website

Visit qelola.com now to see the best up-to-date Qelola content for Indonesia and also check out these interesting facts you probably never knew about qelola.com

A mobile application that helps migrant workers (TKI) who works overseas to manage their fund in their origin country (Indonesia) effectively anywhere anytime.

Visit qelola.com

Key Findings

We analyzed Qelola.com page load time and found that the first response time was 969 ms 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

qelola.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.9

3/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

qelola.com

969 ms

qelola.com

1132 ms

js

96 ms

fbevents.js

46 ms

css

90 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 74% of them (32 requests) were addressed to the original Qelola.com, 7% (3 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Qelola.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.4 kB (34%)

Content Size

916.1 kB

After Optimization

607.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qelola.com main page is 916.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 820.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.9 kB

  • Original 25.5 kB
  • After minification 21.1 kB
  • After compression 6.6 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 4.4 kB, which is 17% 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 18.9 kB or 74% of the original size.

Image Optimization

-31%

Potential reduce by 256.6 kB

  • Original 820.9 kB
  • After minification 564.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, Qelola needs image optimization as it can save up to 256.6 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 12.4 kB

  • Original 41.7 kB
  • After minification 41.7 kB
  • After compression 29.3 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 12.4 kB or 30% of the original size.

CSS Optimization

-73%

Potential reduce by 20.5 kB

  • Original 28.1 kB
  • After minification 28.1 kB
  • After compression 7.5 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. Qelola.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

34

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qelola.com

qelola.com

969 ms

qelola.com

qelola.com

1132 ms

js

js

96 ms

fbevents.js

fbevents.js

46 ms

css

css

90 ms

style.css

style.css

461 ms

anime.min.js

anime.min.js

91 ms

scrollreveal.min.js

scrollreveal.min.js

93 ms

responsive-nav.js

responsive-nav.js

691 ms

style.scss

style.scss

926 ms

main.min.js

main.min.js

958 ms

fastclick.js

fastclick.js

958 ms

scroll.js

scroll.js

959 ms

fixed-responsive-nav.js

fixed-responsive-nav.js

960 ms

js

js

48 ms

analytics.js

analytics.js

19 ms

collect

collect

37 ms

bgphone1.svg

bgphone1.svg

272 ms

phone1.png

phone1.png

1140 ms

aboutcompany.svg

aboutcompany.svg

691 ms

circularbg.svg

circularbg.svg

465 ms

benefit1.svg

benefit1.svg

500 ms

benefit2.svg

benefit2.svg

503 ms

benefit3.svg

benefit3.svg

504 ms

benefit4.svg

benefit4.svg

696 ms

bgphone2.svg

bgphone2.svg

735 ms

phone2.png

phone2.png

1682 ms

f1.png

f1.png

1210 ms

f2.png

f2.png

1147 ms

f3.png

f3.png

1152 ms

f4.png

f4.png

1679 ms

p1.svg

p1.svg

1367 ms

p2.svg

p2.svg

1376 ms

p3.svg

p3.svg

1380 ms

p5.svg

p5.svg

1447 ms

getintouch.svg

getintouch.svg

1596 ms

footerbgall.svg

footerbgall.svg

1374 ms

muliBlack.ttf

muliBlack.ttf

1568 ms

muliRegular.ttf

muliRegular.ttf

1414 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf

16 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmj.ttf

22 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EbiusdUmj.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EbiusdUmj.ttf

29 ms

muliBold.ttf

muliBold.ttf

1554 ms

Accessibility Review

qelola.com accessibility score

88

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-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

qelola.com best practices score

67

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

Browser errors were logged to the console

SEO Factors

qelola.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qelola.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 Qelola.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

qelola.com

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