Tools & Wizards About Us
quickpay.lk screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

quickpay.lk

QuickPay - Recharge Service

Page Load Speed

5.3 sec in total

First Response

930 ms

Resources Loaded

3.7 sec

Page Rendered

710 ms

quickpay.lk screenshot

About Website

Click here to check amazing Quick Pay content for Sri Lanka. Otherwise, check out these important facts you probably never knew about quickpay.lk

Quickpay is an Leading Multi Recharge Provider in Sri Lanka. We provide a recharge service for all major prepaid, postpaid, bill payment mobile service providers in Srilanka. We have been making remar...

Visit quickpay.lk

Key Findings

We analyzed Quickpay.lk page load time and found that the first response time was 930 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

quickpay.lk performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

quickpay.lk

930 ms

css

34 ms

bootstrap.css

1246 ms

fontawesome-all.css

1033 ms

swiper.css

642 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 85% of them (41 requests) were addressed to the original Quickpay.lk, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Api.ampal.group. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Api.ampal.group.

Page Optimization Overview & Recommendations

Page size can be reduced by 557.9 kB (49%)

Content Size

1.1 MB

After Optimization

579.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Quickpay.lk main page is 1.1 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. 55% of websites need less resources to load. Images take 444.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 33.9 kB

  • Original 38.9 kB
  • After minification 24.6 kB
  • After compression 5.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 14.3 kB, which is 37% 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 33.9 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 10.4 kB

  • Original 444.8 kB
  • After minification 434.4 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. Quick Pay images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 240.5 kB

  • Original 338.8 kB
  • After minification 328.9 kB
  • After compression 98.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 240.5 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 273.1 kB

  • Original 315.2 kB
  • After minification 252.8 kB
  • After compression 42.1 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. Quickpay.lk needs all CSS files to be minified and compressed as it can save up to 273.1 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

41

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quickpay.lk

quickpay.lk

930 ms

css

css

34 ms

bootstrap.css

bootstrap.css

1246 ms

fontawesome-all.css

fontawesome-all.css

1033 ms

swiper.css

swiper.css

642 ms

magnific-popup.css

magnific-popup.css

433 ms

styles.css

styles.css

1001 ms

jquery.min.js

jquery.min.js

887 ms

popper.min.js

popper.min.js

437 ms

bootstrap.min.js

bootstrap.min.js

855 ms

jquery.easing.min.js

jquery.easing.min.js

655 ms

swiper.min.js

swiper.min.js

1311 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

1001 ms

validator.min.js

validator.min.js

1029 ms

scripts.js

scripts.js

1111 ms

gtm.js

gtm.js

101 ms

playstore_button.png

playstore_button.png

1020 ms

logo.jpg

logo.jpg

210 ms

header-background.jpg

header-background.jpg

430 ms

header-teamwork.svg

header-teamwork.svg

431 ms

customer-logo-1.png

customer-logo-1.png

213 ms

customer-logo-2.png

customer-logo-2.png

255 ms

customer-logo-3.png

customer-logo-3.png

416 ms

customer-logo-4.png

customer-logo-4.png

426 ms

customer-logo-5.png

customer-logo-5.png

469 ms

customer-logo-6.png

customer-logo-6.png

479 ms

customer-logo-7.png

customer-logo-7.png

623 ms

customer-logo-8.png

customer-logo-8.png

638 ms

customer-logo-9.png

customer-logo-9.png

644 ms

customer-logo-10.png

customer-logo-10.png

646 ms

services-icon-1.svg

services-icon-1.svg

682 ms

services-icon-2.svg

services-icon-2.svg

693 ms

services-icon-3.svg

services-icon-3.svg

832 ms

store-1977.svg

store-1977.svg

850 ms

user-247.svg

user-247.svg

858 ms

team-management-9838.svg

team-management-9838.svg

862 ms

details-1-office-worker.svg

details-1-office-worker.svg

895 ms

details-2-office-team-work.svg

details-2-office-team-work.svg

911 ms

contact-background.jpg

contact-background.jpg

1039 ms

details-lightbox-2.svg

details-lightbox-2.svg

1063 ms

appstore_button.png

appstore_button.png

1670 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

27 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

38 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

39 ms

fa-solid-900.woff

fa-solid-900.woff

1038 ms

fa-regular-400.woff

fa-regular-400.woff

1043 ms

fa-brands-400.woff

fa-brands-400.woff

1369 ms

up-arrow.png

up-arrow.png

846 ms

Accessibility Review

quickpay.lk accessibility score

76

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.

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 IDs are not unique

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

quickpay.lk 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

quickpay.lk SEO score

99

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

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 Quickpay.lk 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 Quickpay.lk 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

quickpay.lk

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