Your Website Score is

Similar Ranking

41
IDPAY | آیدی پی
idpay.ir
41
KÊNH THÔNG TIN KINH TẾ - TÀI CHÍNH VIỆT NAM
cafef.vn
41
FREE CLIP ART - CLIP ART COLLECTION - DOWNLOAD CLIPART ON CLIPART LIBRARY
clipart-library.com
41
MUBI: WATCH AND DISCOVER MOVIES
mubi.com
41
SIMPLENOTE
simplenote.com
41
МВД РОССИИ
xn--b1aew.xn--p1ai
41
سینماتیکت بزرگترین مرجع فروش بلیت سینما
cinematicket.org

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1
-
av4.xyz

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

41 idpay.ir Last Updated: 6 months

Success 78% of passed verification steps
Warning 15% of total warning
Errors 7% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 77%
SEO Desktop Score 91%
Progressive Web App Desktop Score 58%
Performance Mobile Score 64%
Best Practices Mobile Score 69%
SEO Mobile Score 89%
Progressive Web App Mobile Score 59%
Page Authority Authority 45%
Domain Authority Domain Authority 31%
Moz Rank 4.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 15 Characters
IDPAY | آیدی پی
Meta Description 89 Characters
آیدی پی یک سیستم درگاه پرداخت شخصی است. بهترین، راحت ترین و امن ترین راه برای دریافت پول.
Effective URL 16 Characters
https://idpay.ir
Excerpt Page content
IDPay | آیدی پی رفتن به محتوای اصلی IDPay ورود خانهآیدی پی چیست؟پرسش های متداولراهنمای API پرداختتماس با ماورودثبت نام آیدی پی خود را رایگان بسازیددرگاه پرداخت شخصی و کارت خوان مجازی خودتان را داشته باشید ثبت نام و ساخت ...
Meta Keywords 8 Detected
آیدی‌پی آیدیپی درگاه پرداخت درگاه شخصی درگاه پرداخت شخصی پرداخت الکترونیک انتقال وجه پرداخت آسان
Keywords Cloud Density
آیدی20 پرداخت17 شماره12 idpay10 برای10 کنید10 درگاه8 دریافت8 mostafa7 صفحه6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
آیدی 20
پرداخت 17
شماره 12
idpay 10
برای 10
کنید 10
درگاه 8
دریافت 8
mostafa 7
صفحه 6
Google Preview Your look like this in google search result
IDPAY | آیدی پی
https://idpay.ir
آیدی پی یک سیستم درگاه پرداخت شخصی است. بهترین، راحت ترین و امن ترین راه برای دریافت پول.
Robots.txt File Detected
http://idpay.ir/robots.txt
Sitemap.xml File Detected
http://idpay.ir/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~28.12 KB
Code Size: ~16.92 KB
Text Size: ~11.2 KB Ratio: 39.82%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 287 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 43 requests • 921 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 3 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 49 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 230 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 1,680 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 730 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 8 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 131 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 921 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted

Mobile

Mobile Screenshot
Time to Interactive 6.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 30 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Contentful Paint (3G) 5405 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 66% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 98.46% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 49 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 230 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 1,580 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 8 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 169 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 33 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 921 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 291 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 43 requests • 921 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 3 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Date: Thu, 23 Apr 2020 19:00:11 GMT
Vary: Accept-Encoding
Strict-Transport-Security: max-age=2592000; includeSubDomains; preload
Vary: Accept-Encoding
Expires: Thu, 23 Apr 2020 19:00:11 GMT
Cache-Control: max-age=0
X-Content-Type-Options: nosniff
Content-Language: fa
X-Frame-Options: SAMEORIGIN
Link: ; rel="canonical",; rel="shortlink",; rel="shortcut icon",; rel="icon_16x16",; rel="icon_32x32",; rel="icon_96x96",; rel="icon_192x192",; rel="apple-touch-icon",; rel="apple-touch-icon_72x72",; rel="apple-touch-icon_76x76",; rel="apple-touch-icon_114x114",; rel="apple-touch-icon_120x120",; rel="apple-touch-icon_144x144",; rel="apple-touch-icon_152x152",; rel="apple-touch-icon_180x180",; rel="apple-touch-icon-precomposed",; rel="apple-touch-icon-precomposed_72x72",; rel="apple-touch-icon-precomposed_76x76",; rel="apple-touch-icon-precomposed_114x114",; rel="apple-touch-icon-precomposed_120x120",; rel="apple-touch-icon-precomposed_144x144",; rel="apple-touch-icon-precomposed_152x152",; rel="apple-touch-icon-precomposed_180x180"
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload;
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Server: ArvanCloud
ar-sid: 6200
AR-CACHE: MISS
Content-Encoding: gzip
AR-PoweredBy: Arvan Cloud (arvancloud.com)
AR-ATIME: 1.387
AR-Request-ID: 1ca1c94d40b1c7a47604c3f539d019be
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A idpay.ir 185.143.234.5 IN 117
A idpay.ir 185.143.233.5 IN 117
NS idpay.ir l.ns.arvancdn.com IN 7200
NS idpay.ir z.ns.arvancdn.com IN 7200
MX idpay.ir mx3.zoho.com IN 120
MX idpay.ir mx2.zoho.com IN 120
MX idpay.ir mx.zoho.com IN 120
TXT idpay.ir ppkey-655def3d9015306d8b10111469b7a5c4 IN 120
TXT idpay.ir v=spf1 include:_spf.elasticemail.com include:pepipost.net include:zoho.com ~all IN 120
TXT idpay.ir google-site-verification=PmuhP8jpr1oC7A9fdV1I-DonRSz_afXaGbKNz5xIHoY IN 120
TXT idpay.ir zoho-verification=zb14893898.zmverify.zoho.com IN 120

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome