Famha.Ir - Info famha.ir

famha.ir receives about 1,633 unique visitors and 2,123 (1.30 per visitor) page views per day which should earn about $2.46/day from advertising revenue. Estimated site value is $1,797.73. According to Alexa Traffic Rank famha.ir is ranked number 1,192,516 in the world and 3.6E-5% of global Internet users visit it. Site is hosted in Iran and links to network IP address 185.8.175.168. This server doesn't support HTTPS and doesn't support HTTP/2.

About - famha.ir


Technologies used on Website

Web Servers
Apache
Programming Languages
PHP

famha.ir Profile

Title: link | مرجع دانلود فایل
Last update was 7 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is famha.ir?

1.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,633
Monthly Unique Visitors:
39,192
Pages per Visit:
1.30
Daily Pageviews:
2,123
Alexa Rank:
1,192,516 visit alexa
Alexa Reach:
3.6E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Iran 100.0%100.0%54725

Where do visitors go on this site?

Currently Not Available

Competitive Data

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

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is famha.ir?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

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


Mobile summary

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

+ Abusive Experience Report

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

+ How much famha.ir can earn?

Daily Revenue:
$2.46
Monthly Revenue:
$73.80
Yearly Revenue:
$897.90
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Iran 2,123$2.46

How much money do famha.ir lose due to Adblock?

Daily Revenue Loss:
$0.39
Monthly Revenue Loss:
$11.82
Yearly Revenue Loss:
$143.82
Daily Pageviews Blocked:
340
Monthly Pageviews Blocked:
10,190
Yearly Pageviews Blocked:
123,983
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Iran 340$0.39

How much is famha.ir worth?

Website Value:
$1,797.73

+ Where is famha.ir hosted?

Server IP:
185.8.175.168
ASN:
AS60631 
ISP:
Pars Parva System Co. LTD 
Server Location:

Iran, IR
 

Other sites hosted on 185.8.175.168

+ How fast does famha.ir load?

Average Load Time:
(226 ms) 99 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
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

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.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 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.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 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.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 30 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). Learn more.

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

URL
Time Spent
(Initial: http://famha.ir/)
0
http://link.famha.ir/link.html
190
User Timing marks and measures - 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name
TypeStart TimeDuration
is
Mark919 ms0 ms
dr
Mark921 ms0 ms
visible
Mark933 ms0 ms
ofv
Mark933 ms0 ms
mbv
Mark942 ms0 ms
ol
Mark947 ms0 ms
e_is
Mark949 ms0 ms
pc
Mark952 ms0 ms
Keep request counts low and transfer sizes small - 5 requests • 93 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
593 KB
Script
391 KB
Document
12 KB
Other
10 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Third-party
391 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://famha.ir/
0 ms413 ms0 KB0 KB302text/html
http://link.famha.ir/link.html
413 ms843 ms2 KB5 KB200text/htmlDocument
https://cdn.ampproject.org/v0.js
855 ms866 ms71 KB254 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-form-0.1.js
855 ms872 ms16 KB48 KB200text/javascriptScript
https://cdn.ampproject.org/rtv/012005151844001/v0/amp-auto-lightbox-0.1.js
959 ms963 ms4 KB7 KB200text/javascriptScript
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
91 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
871 ms
8 ms
884 ms
22 ms
923 ms
41 ms
974 ms
8 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
56 ms9 ms1 ms
https://cdn.ampproject.org/v0.js
51 ms43 ms6 ms
Avoids enormous network payloads - Total size was 93 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://cdn.ampproject.org/v0.js
71 KB
https://cdn.ampproject.org/v0/amp-form-0.1.js
16 KB
https://cdn.ampproject.org/rtv/012005151844001/v0/amp-auto-lightbox-0.1.js
4 KB
http://link.famha.ir/link.html
2 KB
http://famha.ir/
0 KB
Minimizes main-thread work - 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.

Category
Time Spent
Script Evaluation
53 ms
Style & Layout
24 ms
Other
18 ms
Script Parsing & Compilation
10 ms
Parse HTML & CSS
3 ms
Rendering
3 ms
Avoid chaining critical requests - 1 chain 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.

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.

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

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

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

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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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.

Serve images in next-gen formats
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.


Page Speed (Google PageSpeed Insights) - Mobile

97
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

Max Potential First Input Delay 90 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 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 40 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.
First Contentful Paint (3G) 2460 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.6 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 1.3 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 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://famha.ir/
0 ms696 ms0 KB0 KB302text/html
http://link.famha.ir/link.html
696 ms1398 ms2 KB4 KB200text/htmlDocument
https://cdn.ampproject.org/v0.js
1415 ms1426 ms71 KB254 KB200text/javascriptScript
https://cdn.ampproject.org/v0/amp-form-0.1.js
1415 ms1422 ms16 KB48 KB200text/javascriptScript
https://cdn.ampproject.org/rtv/012005151844001/v0/amp-auto-lightbox-0.1.js
1534 ms1539 ms4 KB7 KB200text/javascriptScript
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
91 KB54 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1422 ms
11 ms
1439 ms
26 ms
1484 ms
47 ms
1542 ms
11 ms
JavaScript execution time - 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
254 ms39 ms5 ms
https://cdn.ampproject.org/v0.js
241 ms203 ms29 ms
Avoids enormous network payloads - Total size was 93 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://cdn.ampproject.org/v0.js
71 KB
https://cdn.ampproject.org/v0/amp-form-0.1.js
16 KB
https://cdn.ampproject.org/rtv/012005151844001/v0/amp-auto-lightbox-0.1.js
4 KB
http://link.famha.ir/link.html
2 KB
http://famha.ir/
0 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.

Category
Time Spent
Script Evaluation
247 ms
Style & Layout
113 ms
Other
80 ms
Script Parsing & Compilation
46 ms
Parse HTML & CSS
13 ms
Rendering
13 ms
Garbage Collection
2 ms
Avoids an excessive DOM size - 30 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). Learn more.

Statistic
ElementValue
Total DOM Elements
30
Maximum DOM Depth
10
Maximum Child Elements
4
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://famha.ir/)
0
http://link.famha.ir/link.html
630
User Timing marks and measures - 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Name
TypeStart TimeDuration
is
Mark1483 ms0 ms
dr
Mark1486 ms0 ms
visible
Mark1501 ms0 ms
ofv
Mark1501 ms0 ms
mbv
Mark1510 ms0 ms
ol
Mark1515 ms0 ms
e_is
Mark1518 ms0 ms
pc
Mark1521 ms0 ms
Keep request counts low and transfer sizes small - 5 requests • 93 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
593 KB
Script
391 KB
Document
12 KB
Other
10 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Third-party
391 KB
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 700 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

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

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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.

Serve images in next-gen formats
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.

Avoid chaining critical requests - 1 chain 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.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does famha.ir use compression?

famha.ir use gzip compression.
Original size: 4.66 KB
Compressed size: 1.82 KB
File reduced by: 2.83 KB (60%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

famha.ir does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

famha.ir does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 23 May 2020 00:28:30 GMT
Server: Apache/2
X-Powered-By: PHP/7.2.11
Location: http://link.famha.ir/link.html
Cache-Control: max-age=31536000
Expires: Sun, 23 May 2021 00:28:30 GMT
Vary: User-Agent
Content-Length: 0
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Sat, 23 May 2020 00:28:30 GMT
Server: Apache/2
X-Powered-By: PHP/7.2.11
Cache-Control: max-age=31536000
Expires: Sun, 23 May 2021 00:28:30 GMT
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 1868
Content-Type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
A 185.8.175.168 3576
NS ns1.ampf.ir 1416
NS ns2.ampf.ir 1416

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

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

% NOTE: This output has been filtered.

% Information related to 'famha.ir'


domain: famha.ir
ascii: famha.ir
remarks: (Domain Holder) Ali Alemardan
remarks: (Domain Holder Address) Mohammadshahr, Karaj, Alborz, IR
holder-c: aa6293-irnic
admin-c: aa6293-irnic
tech-c: aa6293-irnic
bill-c: ra1722-irnic
nserver: ns1.ampf.ir
nserver: ns2.ampf.ir
last-updated: 2019-10-14
expire-date: 2020-10-13
source: IRNIC # Filtered

nic-hdl: aa6293-irnic
person: Ali Alemardan
e-mail: email
address: Mohammadshahr, Karaj, Alborz, IR
phone: +989168416830
source: IRNIC # Filtered

nic-hdl: ra1722-irnic
org: Rayan Dadeh Negar Dena
e-mail: email
source: IRNIC # Filtered
Last update was 7 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

wfima.org
33 secs
botalka.com
40 secs
larryjunetfm.com
1 min
borey.ru
1 min
tag.crsspxl.com
2 mins
borboza.ru
2 mins
wfima.com
3 mins
borafilter.ru
3 mins
itimf.com
3 mins
modmafia.co
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
famha.ir widget