Tools & Wizards About Us
forpay.in screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

forpay.in

ForPay - Mobile Recharge , Dth Recharge , Bill Payment , Fast Tag Rech

Page Load Speed

4.9 sec in total

First Response

444 ms

Resources Loaded

4.2 sec

Page Rendered

257 ms

forpay.in screenshot

About Website

Welcome to forpay.in homepage info - get ready to check For Pay best content right away, or after learning these important things about forpay.in

ForPay - Mobile Recharge , Dth Recharge , Bill Payment , Fast Tag Recharge , Recharge , Bill Payment , Recharge Payment , Flight Booking , Bus Booking , Hotel Booking and more service available . Pay ...

Visit forpay.in

Key Findings

We analyzed Forpay.in page load time and found that the first response time was 444 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

forpay.in performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

forpay.in

444 ms

forpay.in

1508 ms

css2

24 ms

bootstrap.min.css

755 ms

all.min.css

636 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original Forpay.in, 24% (15 requests) were made to Imgfpay.b-cdn.net and 18% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Imgfpay.b-cdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.0 kB (12%)

Content Size

1.1 MB

After Optimization

984.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forpay.in 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 579.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 21.6 kB

  • Original 27.0 kB
  • After minification 20.9 kB
  • After compression 5.5 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 6.1 kB, which is 23% 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 21.6 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 39.5 kB

  • Original 579.1 kB
  • After minification 539.7 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. For Pay images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 62.8 kB

  • Original 381.1 kB
  • After minification 353.9 kB
  • After compression 318.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 62.8 kB or 16% of the original size.

CSS Optimization

-3%

Potential reduce by 4.2 kB

  • Original 125.0 kB
  • After minification 125.0 kB
  • After compression 120.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. Forpay.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (47%)

Requests Now

47

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of For 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 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

forpay.in

forpay.in

444 ms

forpay.in

forpay.in

1508 ms

css2

css2

24 ms

bootstrap.min.css

bootstrap.min.css

755 ms

all.min.css

all.min.css

636 ms

owl.carousel.min.css

owl.carousel.min.css

640 ms

jquery-ui.css

jquery-ui.css

641 ms

stylesheet.css

stylesheet.css

862 ms

custom.css

custom.css

659 ms

daterangepicker.css

daterangepicker.css

843 ms

logo.png

logo.png

1055 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

13 ms

jquery.min.js

jquery.min.js

856 ms

jquery-ui.min.js

jquery-ui.min.js

1195 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

732 ms

owl.carousel.min.js

owl.carousel.min.js

797 ms

bootstrap-spinner.js

bootstrap-spinner.js

1060 ms

moment.min.js

moment.min.js

1176 ms

daterangepicker.js

daterangepicker.js

1177 ms

theme.js

theme.js

1177 ms

customJs.js

customJs.js

1178 ms

mobile_recharge.png

mobile_recharge.png

567 ms

playstore.png

playstore.png

1284 ms

app-store.png

app-store.png

564 ms

google-play-store.png

google-play-store.png

603 ms

dth.png

dth.png

863 ms

electricity.png

electricity.png

1013 ms

fastag2.png

fastag2.png

1016 ms

landline1.1.png

landline1.1.png

1019 ms

hospital1.1.png

hospital1.1.png

1025 ms

subscription.png

subscription.png

1036 ms

education1.1.png

education1.1.png

1088 ms

water1.1.png

water1.1.png

1295 ms

credit_card.png

credit_card.png

1276 ms

loan.png

loan.png

1298 ms

health_insurence.png

health_insurence.png

1287 ms

cable_tv.png

cable_tv.png

1571 ms

housing.png

housing.png

1356 ms

municipal.png

municipal.png

1539 ms

H2SV4-Sc76A

H2SV4-Sc76A

139 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

23 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

40 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

55 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

56 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

56 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

55 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

56 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

54 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

65 ms

fa-solid-900.woff

fa-solid-900.woff

967 ms

fa-regular-400.woff

fa-regular-400.woff

576 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

29 ms

base.js

base.js

72 ms

ad_status.js

ad_status.js

184 ms

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

148 ms

embed.js

embed.js

71 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

24 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

25 ms

id

id

32 ms

Create

Create

106 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

forpay.in accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

forpay.in best practices score

75

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

forpay.in SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Forpay.in 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 Forpay.in 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

forpay.in

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