Coper.Ir - Info coper.ir

coper.ir receives about 907 unique visitors and 1,814 (2.00 per visitor) page views per day which should earn about $2.10/day from advertising revenue. Estimated site value is $1,536.58. According to Alexa Traffic Rank coper.ir is ranked number 1,716,495 in the world and 2.0E-5% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.28.4.21. This server supports HTTPS and doesn't support HTTP/2.

About - coper.ir


Technologies used on Website

CDN
CloudFlare
Programming Languages
PHP
CMS
WordPress
Blogs
WordPress
Databases
MySQL

coper.ir Profile

Title: کوپر
Last update was 51 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is coper.ir?

0.9K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
907
Monthly Unique Visitors:
21,768
Pages per Visit:
2.00
Daily Pageviews:
1,814
Alexa Rank:
1,716,495 visit alexa
Alexa Reach:
2.0E-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%68162

Where do visitors go on this site?

Reach%Pageviews%PerUser
coper.ir
100.00%100.00%2

Competitive Data

SEMrush
Domain:
  coper.ir
Rank:
(Rank based on keywords, cost and organic traffic)
  10,363,819
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  75
Organic Traffic:
(Number of visitors coming from top 20 search results)
  8
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 coper.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:
coper.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:
coper.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 coper.ir can earn?

Daily Revenue:
$2.10
Monthly Revenue:
$63.00
Yearly Revenue:
$766.50
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Iran 1,814$2.10

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

Daily Revenue Loss:
$0.34
Monthly Revenue Loss:
$10.10
Yearly Revenue Loss:
$122.89
Daily Pageviews Blocked:
290
Monthly Pageviews Blocked:
8,707
Yearly Pageviews Blocked:
105,938
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Iran 290$0.34

How much is coper.ir worth?

Website Value:
$1,536.58

+ Where is coper.ir hosted?

Server IP:
104.28.4.21
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.28.4.21

+ How fast does coper.ir load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
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 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.6 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.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 0.6 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.6 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://coper.ir/
0 ms930 ms58 KB274 KB200text/htmlDocument
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
957 ms978 ms14 KB13 KB200image/jpegImage
data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
998 ms999 ms0 KB0 KB200image/gifImage
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
1001 ms1034 ms12 KB28 KB200application/javascriptScript
http://coper.ir/wp-content/themes/coper/assets/fonts/base.woff
1026 ms1058 ms43 KB43 KB200font/woffFont
http://coper.ir/wp-content/themes/coper/assets/fonts/fontawesome-webfont.woff2?v=4.7.0
1029 ms1067 ms76 KB75 KB200application/font-woff2Font
http://coper.ir/wp-content/themes/coper/assets/fonts/base-bold.woff
1030 ms1053 ms44 KB43 KB200font/woffFont
http://coper.ir/logo.jpg
1363 ms1385 ms2 KB2 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%D9%BE%D9%88%D8%B2%D8%A7%D9%84-%D8%B1%D8%B6%D8%A7%DB%8C%D8%AA-%D8%B2%D9%86%D8%A7%D8%B4%D9%88%DB%8C%DB%8C-150x150.jpg
1363 ms1386 ms7 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%DA%98%D9%87-%D8%AF%D8%A7%D9%86%D8%B4%D8%AC%D9%88%DB%8C%DB%8C-%D8%AA%D8%B1%D9%85%DB%8C%D9%86%D8%A7%D9%84-150x150.jpg
1364 ms1836 ms7 KB6 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A7%D8%AA%D9%88%DA%A9%D8%AF-%D9%BE%D9%84%D8%A7%D9%86-%D9%88%DB%8C%D9%84%D8%A7-150x150.jpg
1364 ms1846 ms4 KB4 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D8%AA%D8%A7%D8%A8-%D8%AF%DB%8C%D8%B3%DA%A9-150x150.jpg
1365 ms1387 ms6 KB5 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%DA%A9%D9%85%D9%BE%D9%88%D8%AA-%D9%88-%DA%A9%D9%86%D8%B3%D8%B1%D9%88-150x150.jpg
1365 ms1406 ms8 KB8 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%AD%D8%B1%D8%A7%D9%86-%D8%B7%D9%84%D8%A7%D9%82-150x150.jpg
1366 ms1403 ms8 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%B3%D8%AA%D9%86%DB%8C-%DA%86%D9%88%D8%A8%DB%8C-150x150.jpg
1366 ms1847 ms4 KB4 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/Super-Decisions-150x117.jpg
1366 ms1392 ms5 KB4 KB200image/jpegImage
data:image/gif;base64,R0lGODlhIAAgAPQeAIyKjIyOjJSSlJSWlJyanJyenKSipKSmpKyqrKyurLSytLS2tLy6vLy+vMTCxM
1367 ms1367 ms0 KB2 KB200image/gifImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%B3%D9%86%DA%AF%D8%A8%D8%B1%DB%8C-150x150.jpg
2358 ms2379 ms7 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%A7%D8%B2%DB%8C%D8%A7%D9%81%D8%AA-%D9%85%D9%88%D8%A7%D8%AF-%D9%BE%D9%84%D8%A7%D8%B3%D8%AA%DB%8C%DA%A9%DB%8C-150x150.jpg
2358 ms2378 ms7 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A2%D9%85%D9%88%D8%B2%D8%B4%DA%AF%D8%A7%D9%87-%D8%B2%D8%A8%D8%A7%D9%86-150x150.jpg
2359 ms2381 ms6 KB5 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%A7%D8%B2%D8%A7%D8%B1%DB%8C%D8%A7%D8%A8%DB%8C-%D8%A8%DB%8C%D9%86-%D8%A7%D9%84%D9%85%D9%84%D9%84%DB%8C-150x150.jpg
2491 ms2970 ms6 KB6 KB200image/jpegImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
961 ms
11 ms
979 ms
6 ms
987 ms
39 ms
1030 ms
99 ms
1139 ms
27 ms
1167 ms
37 ms
1204 ms
10 ms
1214 ms
147 ms
1362 ms
11 ms
1376 ms
17 ms
1393 ms
9 ms
1423 ms
7 ms
1449 ms
5 ms
1866 ms
6 ms
1883 ms
6 ms
2383 ms
9 ms
2416 ms
6 ms
2516 ms
8 ms
2998 ms
5 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
348 ms16 ms1 ms
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
180 ms104 ms2 ms
Defer offscreen images - Potential savings of 13 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
13 KB13 KB
Remove unused CSS - Potential savings of 44 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.

URL
SizePotential Savings
@charset "UTF-8";.edd-icon{display:inline-block;fill:currentColor;position:relative;top:-.0625em; ... } ...
48 KB44 KB
Avoids enormous network payloads - Total size was 324 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://coper.ir/wp-content/themes/coper/assets/fonts/fontawesome-webfont.woff2?v=4.7.0
76 KB
http://coper.ir/
58 KB
http://coper.ir/wp-content/themes/coper/assets/fonts/base-bold.woff
44 KB
http://coper.ir/wp-content/themes/coper/assets/fonts/base.woff
43 KB
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
14 KB
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
12 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%DA%A9%D9%85%D9%BE%D9%88%D8%AA-%D9%88-%DA%A9%D9%86%D8%B3%D8%B1%D9%88-150x150.jpg
8 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%AD%D8%B1%D8%A7%D9%86-%D8%B7%D9%84%D8%A7%D9%82-150x150.jpg
8 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%B3%D9%86%DA%AF%D8%A8%D8%B1%DB%8C-150x150.jpg
7 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%A7%D8%B2%DB%8C%D8%A7%D9%81%D8%AA-%D9%85%D9%88%D8%A7%D8%AF-%D9%BE%D9%84%D8%A7%D8%B3%D8%AA%DB%8C%DA%A9%DB%8C-150x150.jpg
7 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
Style & Layout
222 ms
Script Evaluation
122 ms
Other
79 ms
Rendering
65 ms
Parse HTML & CSS
40 ms
Script Parsing & Compilation
4 ms
Avoids an excessive DOM size - 475 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
475
Maximum DOM Depth
12
Maximum Child Elements
45
Keep request counts low and transfer sizes small - 21 requests • 324 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
21324 KB
Font
3163 KB
Image
1690 KB
Document
158 KB
Script
112 KB
Stylesheet
00 KB
Media
00 KB
Other
00 KB
Third-party
20 KB
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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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 - 3 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 930 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.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)3.3s 0% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 13% 52% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 52% 33% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 33%
First Input Delay (FID)39ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)3.3s 13% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 13% 52% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 52% 33% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 33%
First Input Delay (FID)39ms 0% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.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 1.1 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.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
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 1.5 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.
First Contentful Paint (3G) 1967 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.2 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
772 ms29 ms3 ms
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
267 ms161 ms8 ms
Defer offscreen images - Potential savings of 13 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
13 KB13 KB
Remove unused CSS - Potential savings of 44 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.

URL
SizePotential Savings
@charset "UTF-8";.edd-icon{display:inline-block;fill:currentColor;position:relative;top:-.0625em; ... } ...
48 KB44 KB
Avoids enormous network payloads - Total size was 292 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://coper.ir/wp-content/themes/coper/assets/fonts/fontawesome-webfont.woff2?v=4.7.0
76 KB
http://coper.ir/
58 KB
http://coper.ir/wp-content/themes/coper/assets/fonts/base-bold.woff
44 KB
http://coper.ir/wp-content/themes/coper/assets/fonts/base.woff
43 KB
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
14 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%DA%A9%D9%85%D9%BE%D9%88%D8%AA-%D9%88-%DA%A9%D9%86%D8%B3%D8%B1%D9%88.jpg
14 KB
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
12 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%DA%98%D9%87-%D8%AF%D8%A7%D9%86%D8%B4%D8%AC%D9%88%DB%8C%DB%8C-%D8%AA%D8%B1%D9%85%DB%8C%D9%86%D8%A7%D9%84.jpg
8 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%AD%D8%B1%D8%A7%D9%86-%D8%B7%D9%84%D8%A7%D9%82-150x150.jpg
8 KB
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%D9%BE%D9%88%D8%B2%D8%A7%D9%84-%D8%B1%D8%B6%D8%A7%DB%8C%D8%AA-%D8%B2%D9%86%D8%A7%D8%B4%D9%88%DB%8C%DB%8C-150x150.jpg
7 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.

Category
Time Spent
Style & Layout
442 ms
Script Evaluation
193 ms
Other
191 ms
Rendering
132 ms
Parse HTML & CSS
72 ms
Script Parsing & Compilation
13 ms
Garbage Collection
1 ms
Avoids an excessive DOM size - 475 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
475
Maximum DOM Depth
12
Maximum Child Elements
45
Keep request counts low and transfer sizes small - 15 requests • 292 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
15292 KB
Font
3163 KB
Document
158 KB
Image
1058 KB
Script
112 KB
Stylesheet
00 KB
Media
00 KB
Other
00 KB
Third-party
20 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://coper.ir/
0 ms987 ms58 KB274 KB200text/htmlDocument
http://coper.ir/wp-content/uploads/2019/11/register-1.jpg
1005 ms2281 ms14 KB13 KB200image/jpegImage
data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
1023 ms1023 ms0 KB0 KB200image/gifImage
http://coper.ir/wp-content/cache/autoptimize/js/autoptimize_c567e1ce8a421b393ac14d1904924a51.js
1024 ms1066 ms12 KB28 KB200application/javascriptScript
http://coper.ir/wp-content/themes/coper/assets/fonts/base.woff
1034 ms1163 ms43 KB43 KB200font/woffFont
http://coper.ir/wp-content/themes/coper/assets/fonts/fontawesome-webfont.woff2?v=4.7.0
1035 ms1194 ms76 KB75 KB200application/font-woff2Font
http://coper.ir/wp-content/themes/coper/assets/fonts/base-bold.woff
1038 ms1096 ms44 KB43 KB200font/woffFont
http://coper.ir/logo.jpg
1145 ms1165 ms2 KB2 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%D9%BE%D9%88%D8%B2%D8%A7%D9%84-%D8%B1%D8%B6%D8%A7%DB%8C%D8%AA-%D8%B2%D9%86%D8%A7%D8%B4%D9%88%DB%8C%DB%8C-150x150.jpg
1145 ms1641 ms7 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D9%88%DA%98%D9%87-%D8%AF%D8%A7%D9%86%D8%B4%D8%AC%D9%88%DB%8C%DB%8C-%D8%AA%D8%B1%D9%85%DB%8C%D9%86%D8%A7%D9%84.jpg
1145 ms2658 ms8 KB8 KB200image/jpegImage
data:image/gif;base64,R0lGODlhIAAgAPQeAIyKjIyOjJSSlJSWlJyanJyenKSipKSmpKyqrKyurLSytLS2tLy6vLy+vMTCxM
1146 ms1146 ms0 KB2 KB200image/gifImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D9%BE%D8%B1%D8%AA%D8%A7%D8%A8-%D8%AF%DB%8C%D8%B3%DA%A9-150x150.jpg
2685 ms3138 ms6 KB5 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%DA%A9%D9%85%D9%BE%D9%88%D8%AA-%D9%88-%DA%A9%D9%86%D8%B3%D8%B1%D9%88.jpg
2686 ms3137 ms14 KB13 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A8%D8%AD%D8%B1%D8%A7%D9%86-%D8%B7%D9%84%D8%A7%D9%82-150x150.jpg
2686 ms2707 ms8 KB7 KB200image/jpegImage
http://coper.ir/wp-content/uploads/edd/2019/12/%D8%A7%D8%AA%D9%88%DA%A9%D8%AF-%D9%BE%D9%84%D8%A7%D9%86-%D9%88%DB%8C%D9%84%D8%A7.jpg
2801 ms0 ms0 KB0 KB-1Image
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1012 ms
8 ms
1029 ms
16 ms
1046 ms
36 ms
1085 ms
17 ms
1105 ms
32 ms
1142 ms
25 ms
1168 ms
6 ms
1189 ms
23 ms
1217 ms
5 ms
1223 ms
22 ms
2705 ms
6 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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 - 3 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 990 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.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does coper.ir use compression?

coper.ir use gzip compression.
Original size: 274.04 KB
Compressed size: 57.76 KB
File reduced by: 216.28 KB (78%)

+ 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

coper.ir supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.coper.ir
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 25 10:03:21 2019 GMT
Valid until: Feb 23 10:03:21 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

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

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Mon, 09 Dec 2019 12:36:40 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d69e70d5a8c084d08fadffb0e44e085bb1575894998; expires=Wed, 08-Jan-20 12:36:38 GMT; path=/; domain=.coper.ir; HttpOnly
X-Frame-Options: SAMEORIGIN, SAMEORIGIN
X-Powered-By: PHP/5.6.40
Set-Cookie: PHPSESSID=sruet2ec8vcg1b0744git7c0f2; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: max-age=60, public, no-transform, must-revalidate
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 5427069b8ee9c64f-MSP

+ DNS Lookup

Type Ip Target TTL
A 104.28.5.21 263
A 104.28.4.21 263
HINFO 3600
NS cortney.ns.cloudflare.com 1401
NS jay.ns.cloudflare.com 1401

+ 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 'coper.ir'


domain: coper.ir
ascii: coper.ir
remarks: (Domain Holder) bahman maleki Kusalar Olyai
remarks: (Domain Holder Address) qazvin chahar rahe nezam vafa koche sadi farie, qazvin, qazvin, IR
holder-c: bm580-irnic
admin-c: bm580-irnic
tech-c: bm580-irnic
nserver: cortney.ns.cloudflare.com
nserver: jay.ns.cloudflare.com
last-updated: 2019-11-25
expire-date: 2020-02-05
source: IRNIC # Filtered

nic-hdl: bm580-irnic
person: bahman maleki Kusalar Olyai
e-mail: email
address: qazvin chahar rahe nezam vafa koche sadi farie, qazvin, qazvin, IR
phone: 0098 281 5551242
source: IRNIC # Filtered
Last update was 51 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with coper.ir in any way. Only publicly available statistics data are displayed.
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!
coper.ir widget