Sarmashg.Ir - Info receives about 7,258 unique visitors and 64,596 (8.90 per visitor) page views per day which should earn about $74.93/day from advertising revenue. Estimated site value is $54,700.05. According to Alexa Traffic Rank is ranked number 253,598 in the world and 0.00016% of global Internet users visit it. Site is hosted in Finland and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Landing Page Builders
Font Scripts
Google Font API
JavaScript Libraries
jQuery Migrate
Programming Languages
Web Frameworks
Yoast SEO
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

7.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:
253,598 visit alexa
Alexa Reach:
0.00016%   (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%9020

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 64,596$74.93

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 10,335$11.99

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Hetzner Online GmbH 
Server Location:

Finland, FI

Other sites hosted on

+ How fast does load?

Average Load Time:
(2923 ms) 24 % 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

Max Potential First Input Delay 60 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.2 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.
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 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.5 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.5 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.

Serve static assets with an efficient cache policy - 42 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
604800000 ms74 KB
604800000 ms49 KB
604800000 ms40 KB
604800000 ms34 KB
604800000 ms32 KB
604800000 ms31 KB
604800000 ms31 KB
604800000 ms29 KB
604800000 ms23 KB
604800000 ms22 KB
604800000 ms22 KB
604800000 ms20 KB
604800000 ms20 KB
604800000 ms14 KB
604800000 ms13 KB
604800000 ms13 KB
604800000 ms12 KB
604800000 ms12 KB
604800000 ms12 KB
604800000 ms5 KB
604800000 ms5 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms4 KB
604800000 ms3 KB
604800000 ms3 KB
604800000 ms3 KB
604800000 ms3 KB
604800000 ms2 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms1 KB
604800000 ms0 KB
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1481 ms
8 ms
1493 ms
62 ms
1777 ms
11 ms
1789 ms
7 ms
1891 ms
22 ms
1914 ms
20 ms
1938 ms
10 ms
1948 ms
133 ms
2099 ms
51 ms
2159 ms
26 ms
2184 ms
50 ms
2235 ms
8 ms
2289 ms
50 ms
2352 ms
16 ms
2371 ms
13 ms
2384 ms
6 ms
2389 ms
27 ms
2417 ms
23 ms
2443 ms
6 ms
2456 ms
32 ms
2488 ms
9 ms
2501 ms
19 ms
2532 ms
200 ms
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
8 ms
385 ms
267 ms
263 ms
4 ms
259 ms
6 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.

Total CPU TimeScript EvaluationScript Parse
522 ms6 ms1 ms
219 ms198 ms2 ms
60 ms59 ms2 ms
Minify CSS - Potential savings of 5 KB
Minifying CSS files can reduce network payload sizes. Learn more.

SizePotential Savings
34 KB5 KB
Defer offscreen images - Potential savings of 18 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
18 KB18 KB
Remove unused CSS - Potential savings of 136 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
49 KB49 KB
34 KB32 KB
20 KB20 KB
13 KB12 KB
12 KB12 KB
12 KB11 KB
Avoids enormous network payloads - Total size was 648 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

74 KB
49 KB
40 KB
34 KB
32 KB
31 KB
31 KB
29 KB
23 KB
22 KB
Minimizes main-thread work - 1.0 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
Script Evaluation
359 ms
Style & Layout
329 ms
109 ms
Parse HTML & CSS
74 ms
43 ms
Script Parsing & Compilation
27 ms
Garbage Collection
11 ms
Serve images in next-gen formats - Potential savings of 12 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
18 KB12 KB
Avoids an excessive DOM size - 567 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
Keep request counts low and transfer sizes small - 49 requests • 648 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
49648 KB
19239 KB
7196 KB
20171 KB
231 KB
112 KB
00 KB
00 KB
669 KB
Eliminate render-blocking resources - Potential savings of 1,220 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
49 KB470
4 KB110
1 KB110
0 KB110
34 KB430
1 KB110
1 KB190
3 KB70
3 KB70
13 KB190
20 KB230
12 KB150
4 KB70
4 KB70
1 KB70
2 KB230
12 KB150
1 KB70
1 KB70
32 KB190
4 KB70
4 KB70
5 KB70
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms1454 ms12 KB71 KB200text/htmlDocument
1470 ms1865 ms49 KB407 KB200text/cssStylesheet
1470 ms1610 ms4 KB25 KB200text/cssStylesheet
1470 ms1638 ms1 KB2 KB200text/cssStylesheet
1471 ms1614 ms0 KB0 KB200text/cssStylesheet
1471 ms1748 ms34 KB194 KB200text/cssStylesheet
1472 ms1630 ms1 KB7 KB200text/cssStylesheet
1472 ms1491 ms1 KB1 KB200text/cssStylesheet
1472 ms1630 ms3 KB14 KB200text/cssStylesheet
1472 ms1637 ms3 KB18 KB200text/cssStylesheet
1472 ms1746 ms13 KB101 KB200text/cssStylesheet
1473 ms1760 ms20 KB190 KB200text/cssStylesheet
1473 ms1634 ms12 KB55 KB200text/cssStylesheet
1473 ms1750 ms4 KB26 KB200text/cssStylesheet
1473 ms1633 ms4 KB44 KB200text/cssStylesheet
1473 ms1629 ms1 KB6 KB200text/cssStylesheet
1474 ms1500 ms2 KB46 KB200text/cssStylesheet
1474 ms1635 ms12 KB53 KB200text/cssStylesheet
1474 ms1619 ms1 KB1 KB200text/cssStylesheet
1474 ms1631 ms1 KB1 KB200text/cssStylesheet
1474 ms1863 ms32 KB95 KB200application/javascriptScript
1474 ms1735 ms4 KB10 KB200application/javascriptScript
1474 ms1731 ms4 KB15 KB200application/javascriptScript
1475 ms1743 ms5 KB24 KB200text/cssStylesheet
1475 ms1697 ms18 KB18 KB200image/pngImage
1529 ms1783 ms4 KB12 KB200application/javascriptScript
1699 ms1833 ms4 KB14 KB200application/javascriptScript
1784 ms1923 ms1 KB1 KB200application/javascriptScript
1835 ms2091 ms22 KB78 KB200application/javascriptScript
1918 ms2049 ms22 KB75 KB200application/javascriptScript
1918 ms2050 ms1 KB1 KB200application/javascriptScript
1919 ms2320 ms40 KB132 KB200application/javascriptScript
1919 ms2064 ms13 KB46 KB200application/javascriptScript
1919 ms2071 ms3 KB6 KB200application/javascriptScript
1920 ms2080 ms4 KB10 KB200application/javascriptScript
1920 ms2060 ms3 KB12 KB200application/javascriptScript
1920 ms2083 ms31 KB123 KB200application/javascriptScript
1920 ms2181 ms23 KB92 KB200application/javascriptScript
1920 ms2090 ms5 KB17 KB200application/javascriptScript
1920 ms2063 ms2 KB6 KB200application/javascriptScript
1921 ms2214 ms20 KB111 KB200application/javascriptScript
1952 ms2100 ms12 KB12 KB200image/pngImage
1986 ms1994 ms16 KB15 KB200font/woff2Font
1989 ms2374 ms74 KB74 KB200font/woff2Font
1989 ms2256 ms29 KB29 KB200font/woff2Font
1989 ms2252 ms31 KB31 KB200font/woff2Font
1997 ms2001 ms16 KB16 KB200font/woff2Font
1999 ms2258 ms14 KB13 KB200font/woff2Font
2025 ms2031 ms16 KB15 KB200font/woff2Font
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.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. 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.

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

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 1,450 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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: 70.88 KB
Compressed size: 11.6 KB
File reduced by: 59.28 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...

+ 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
X-Powered-By: PHP/7.2.24
Content-Type: text/html; charset=UTF-8
Link: <>; rel=""
Link: <>; rel=shortlink
Transfer-Encoding: chunked
Content-Encoding: br
Vary: Accept-Encoding,User-Agent
Date: Tue, 03 Dec 2019 01:17:06 GMT

+ DNS Lookup

Currently Not Available

+ 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) mohammad hamza
remarks: (Domain Holder Address) azarbayjane shargi-charavimag - qarehagaj, qarehagaj, azarbayjane shargi, IR
holder-c: mh4930-irnic
admin-c: mh4930-irnic
tech-c: mh4930-irnic
last-updated: 2019-12-01
expire-date: 2020-07-06
source: IRNIC # Filtered

nic-hdl: mh4930-irnic
person: mohammad hamza
org: sayberi
e-mail: email
address: azarbayjane shargi-charavimag - qarehagaj, qarehagaj, azarbayjane shargi, IR
phone: +989394812277
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.

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