Tools & Wizards About Us
nextpay.ir screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nextpay.ir

درگاه پرداخت نکست پی | درگاه پرداخت مستقیم | درگاه بانکی | درگاه واسط | درگاه شتاب

Page Load Speed

10.1 sec in total

First Response

2.6 sec

Resources Loaded

7.2 sec

Page Rendered

344 ms

nextpay.ir screenshot

About Website

Visit nextpay.ir now to see the best up-to-date Nextpay content for Iran and also check out these interesting facts you probably never knew about nextpay.ir

نکست پی: ارائه درگاه پرداخت اینترنتی و درگاه پرداخت مستقیم و درگاه پرداخت واسط و درگاه پرداخت بانکی در 5 دقیقه، امکان تسویه به دیگران، بدون نیاز به اینماد و ...

Visit nextpay.ir

Key Findings

We analyzed Nextpay.ir page load time and found that the first response time was 2.6 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

nextpay.ir performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

nextpay.org

2574 ms

js

45 ms

bootstrap.min.css

479 ms

elementor-icons.min.css

381 ms

frontend-lite-rtl.min.css

637 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nextpay.ir, 3% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Nextpay.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 606.1 kB (38%)

Content Size

1.6 MB

After Optimization

981.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nextpay.ir main page is 1.6 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. 50% of websites need less resources to load. Images take 589.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 172.0 kB

  • Original 202.0 kB
  • After minification 196.4 kB
  • After compression 29.9 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 172.0 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 65.3 kB

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

JavaScript Optimization

-41%

Potential reduce by 223.0 kB

  • Original 541.1 kB
  • After minification 540.8 kB
  • After compression 318.1 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 223.0 kB or 41% of the original size.

CSS Optimization

-57%

Potential reduce by 145.7 kB

  • Original 255.3 kB
  • After minification 217.1 kB
  • After compression 109.6 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. Nextpay.ir needs all CSS files to be minified and compressed as it can save up to 145.7 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (75%)

Requests Now

51

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nextpay.org

nextpay.org

2574 ms

js

js

45 ms

bootstrap.min.css

bootstrap.min.css

479 ms

elementor-icons.min.css

elementor-icons.min.css

381 ms

frontend-lite-rtl.min.css

frontend-lite-rtl.min.css

637 ms

post-6.css

post-6.css

486 ms

global.css

global.css

506 ms

post-4284.css

post-4284.css

508 ms

flickity.min.css

flickity.min.css

557 ms

style.min.css

style.min.css

558 ms

jquery-confirm.min.css

jquery-confirm.min.css

645 ms

bootstrap-select.min.css

bootstrap-select.min.css

671 ms

pix-essentials-style-2.css

pix-essentials-style-2.css

1160 ms

masterslider.main.css

masterslider.main.css

919 ms

custom.css

custom.css

734 ms

css

css

36 ms

jquery.min.js

jquery.min.js

949 ms

jquery-migrate.min.js

jquery-migrate.min.js

804 ms

elementor-widgets.js

elementor-widgets.js

835 ms

rtl.css

rtl.css

909 ms

post-4008.css

post-4008.css

810 ms

pixfort-likes.css

pixfort-likes.css

846 ms

odometer-theme-default.css

odometer-theme-default.css

930 ms

css

css

20 ms

animations.min.css

animations.min.css

946 ms

rs6.css

rs6.css

956 ms

index.js

index.js

967 ms

index.js

index.js

1203 ms

rbtools.min.js

rbtools.min.js

1450 ms

rs6.min.js

rs6.min.js

1493 ms

popper.min.js

popper.min.js

1203 ms

bootstrap.min.js

bootstrap.min.js

1203 ms

bootstrap-select.min.js

bootstrap-select.min.js

1204 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

1341 ms

core.min.js

core.min.js

1283 ms

essentials.min.js

essentials.min.js

1462 ms

odometer.min.js

odometer.min.js

1338 ms

pixfort-likes.js

pixfort-likes.js

1432 ms

webpack.runtime.min.js

webpack.runtime.min.js

1504 ms

frontend-modules.min.js

frontend-modules.min.js

1506 ms

waypoints.min.js

waypoints.min.js

1419 ms

frontend.min.js

frontend.min.js

1404 ms

favicon.ico.png

favicon.ico.png

544 ms

np-office.jpg

np-office.jpg

801 ms

uhlsport.png

uhlsport.png

626 ms

Tehranshomallogo-1.png

Tehranshomallogo-1.png

625 ms

charter724.png

charter724.png

689 ms

irib5.png

irib5.png

708 ms

irib2.png

irib2.png

915 ms

irib3.png

irib3.png

773 ms

cta-loop-points-1.png

cta-loop-points-1.png

780 ms

nextpay-pay-button.png

nextpay-pay-button.png

850 ms

markazi-1.jpg

markazi-1.jpg

867 ms

IRANSansWeb(FaNum)_Bold.woff

IRANSansWeb(FaNum)_Bold.woff

811 ms

IRANSansWeb(FaNum)_Black.woff

IRANSansWeb(FaNum)_Black.woff

842 ms

IRANSansWeb(FaNum)_Medium.woff

IRANSansWeb(FaNum)_Medium.woff

935 ms

IRANSansWeb(FaNum).woff

IRANSansWeb(FaNum).woff

936 ms

IRANSansWeb(FaNum)_Light.woff

IRANSansWeb(FaNum)_Light.woff

935 ms

IRANSansWeb(FaNum)_UltraLight.woff

IRANSansWeb(FaNum)_UltraLight.woff

991 ms

pixicon.ttf

pixicon.ttf

1140 ms

iranyekanwebregular.woff

iranyekanwebregular.woff

1035 ms

Accessibility Review

nextpay.ir accessibility score

82

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.

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

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

nextpay.ir 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nextpay.ir 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

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextpay.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Nextpay.ir 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

nextpay.ir

Open Graph data is detected on the main page of Nextpay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: