Firstdata.Ir - Info receives about 3,311 unique visitors and 7,948 (2.40 per visitor) page views per day which should earn about $9.22/day from advertising revenue. Estimated site value is $6,729.95. According to Alexa Traffic Rank is ranked number 592,841 in the world and 7.3E-5% of global Internet users visit it. Site is hosted in Iran and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

JavaScript Graphics
Programming Languages
MySQL Profile

Title: اولین دیتا - راهکار هوشمند میزبانی وب
Description: اولین دیتا - فروش هاست، میزبانی وب، سرور، هاستینگ لینوکس، فروش سرور مجازی ویندوز، نمایندگی فروش هاست و سرور از دیتاسنتر ایران
Last update was 4 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

3.3K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
592,841 visit alexa
Alexa Reach:
7.3E-5%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Iran 100.0%100.0%16686

Where do visitors go on this site?


Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Iran 7,948$9.22

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Iran 1,272$1.48

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Hamed Kavosh Vira Co. (PJS) 
Server Location:

Iran, IR

Other sites hosted on

+ How fast does load?

Average Load Time:
(1769 ms) 51 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn more.
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
827 ms
419 ms
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. Learn more.

Total CPU TimeScript EvaluationScript Parse
333 ms5 ms1 ms
53 ms44 ms5 ms
Properly size images - Potential savings of 7 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
5 KB4 KB
15 KB3 KB
Remove unused CSS - Potential savings of 60 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. Learn more.

SizePotential Savings
63 KB60 KB
Avoids enormous network payloads - Total size was 627 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

162 KB
101 KB
88 KB
63 KB
54 KB
33 KB
28 KB
21 KB
16 KB
12 KB
Minimizes main-thread work - 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Style & Layout
168 ms
Script Evaluation
126 ms
94 ms
42 ms
Parse HTML & CSS
31 ms
Script Parsing & Compilation
16 ms
Garbage Collection
3 ms
Serve images in next-gen formats - Potential savings of 66 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. Learn more.

SizePotential Savings
87 KB66 KB
Avoids an excessive DOM size - 532 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 20 requests • 627 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
20627 KB
6225 KB
2190 KB
6122 KB
480 KB
110 KB
10 KB
00 KB
5149 KB
Eliminate render-blocking resources - Potential savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
63 KB230
6 KB150
1 KB150
33 KB230
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms415 ms0 KB0 KB301text/html
416 ms1266 ms10 KB54 KB200text/htmlDocument
1291 ms1933 ms63 KB391 KB200text/cssStylesheet
1291 ms1503 ms6 KB40 KB200text/cssStylesheet
1291 ms1526 ms1 KB3 KB200text/cssStylesheet
1291 ms2154 ms33 KB95 KB200application/javascriptScript
1291 ms1926 ms5 KB5 KB200image/pngImage
1291 ms1911 ms88 KB87 KB200image/pngImage
1927 ms2136 ms2 KB1 KB200image/pngImage
2138 ms2347 ms1 KB0 KB200image/pngImage
2183 ms2595 ms16 KB15 KB200image/pngImage
2183 ms2395 ms11 KB10 KB200image/pngImage
1914 ms2550 ms54 KB176 KB200application/javascriptScript
2205 ms3032 ms162 KB162 KB200font/woff2Font
2205 ms2624 ms28 KB27 KB200font/woff2Font
3052 ms3397 ms4 KB7 KB200application/javascriptScript
3407 ms3665 ms10 KB48 KB200text/cssStylesheet
3409 ms3868 ms21 KB61 KB200application/javascriptScript
3409 ms4353 ms101 KB295 KB200application/javascriptScript
3409 ms3652 ms12 KB37 KB200application/javascriptScript
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1293 ms
13 ms
1956 ms
17 ms
2182 ms
25 ms
2207 ms
64 ms
2579 ms
27 ms
2607 ms
10 ms
2650 ms
25 ms
3054 ms
38 ms
3092 ms
6 ms
3419 ms
13 ms
3431 ms
27 ms
3689 ms
6 ms
3893 ms
12 ms
4387 ms
47 ms
4437 ms
19 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Avoid chaining critical requests - 7 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 850 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

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. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does use compression? use br compression.
Original size: 54.09 KB
Compressed size: 9.13 KB
File reduced by: 44.96 KB (83%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Let's Encrypt Authority X3
Valid from: Mar 26 23:02:45 2020 GMT
Valid until: Jun 24 23:02:45 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Connection: Keep-Alive
Content-Type: text/html
Content-Length: 706
Date: Sat, 23 May 2020 04:32:07 GMT
Vary: Accept-Encoding,User-Agent,Accept-Encoding
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

HTTP/2 200 
content-type: text/html; charset=UTF-8
strict-transport-security: “max-age=10886400; includeSubDomains; preload”
link: <>; rel=""
cache-control: public, max-age=0
expires: Sat, 23 May 2020 04:32:10 GMT
content-encoding: br
vary: Accept-Encoding,Accept-Encoding,User-Agent,Accept-Encoding
date: Sat, 23 May 2020 04:32:10 GMT
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
alt-svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-25=":443"; ma=2592000, h3-27=":443"; ma=2592000

+ DNS Lookup

Type Ip Target TTL
MX 3600
SOA 3600
Serial Number 2020051800
Refresh 3600
Retry 7200
Expire 1209600
Minimum TTL 0
TXT 3600
A 3558
NS 1398
NS 1398

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
% This is the IRNIC Whois server v1.6.2.
% Available on web at
% Find the terms and conditions of use on
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to ''

remarks: (Domain Holder) Zahed Alfak
remarks: (Domain Holder Address) Ahvaz Zayton, Karmandi, Zahed St., Between Komil St. And Bandar St.,, Tehran, Tehran, IR
holder-c: za113-irnic
admin-c: za113-irnic
tech-c: za113-irnic
last-updated: 2019-06-01
expire-date: 2024-06-20
source: IRNIC # Filtered

nic-hdl: za113-irnic
person: Zahed Alfak
e-mail: email
address: Ahvaz Zayton, Karmandi, Zahed St., Between Komil St. And Bandar St.,, Tehran, Tehran, IR
phone: +986114448687
source: IRNIC # Filtered
Last update was 4 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
18 secs
23 secs
38 secs
1 min
2 mins
2 mins
2 mins
3 mins
3 mins
3 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget