E-Register.Am - Info e-register.am

e-register.am receives about 1,497 unique visitors and 6,287 (4.20 per visitor) page views per day which should earn about $5.72/day from advertising revenue. Estimated site value is $4,176.61. According to Alexa Traffic Rank e-register.am is ranked number 947,975 in the world and 3.3E-5% of global Internet users visit it. Site is hosted in Armenia and links to network IP address 91.221.228.249. This server supports HTTPS and doesn't support HTTP/2.

About - e-register.am


Technologies used on Website

Web Servers
Apache
Programming Languages
PHP

e-register.am Profile

Title: Electronic Register, Government of Armenia
Last update was 6 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with e-register.am in any way. Only publicly available statistics data are displayed.

How popular is e-register.am?

1.5K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,497
Monthly Unique Visitors:
35,928
Pages per Visit:
4.20
Daily Pageviews:
6,287
Alexa Rank:
947,975 visit alexa
Alexa Reach:
3.3E-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
Armenia 100.0%100.0%1064

Where do visitors go on this site?

Reach%Pageviews%PerUser
e-register.am
100.00%100.00%4.6

Competitive Data

SEMrush
Domain:
  e-register.am
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 e-register.am?

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:
e-register.am
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:
e-register.am
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 e-register.am can earn?

Daily Revenue:
$5.72
Monthly Revenue:
$171.60
Yearly Revenue:
$2,087.80
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Armenia 6,287$5.72

How much money do e-register.am lose due to Adblock?

Daily Revenue Loss:
$0.29
Monthly Revenue Loss:
$8.58
Yearly Revenue Loss:
$104.41
Daily Pageviews Blocked:
314
Monthly Pageviews Blocked:
9,431
Yearly Pageviews Blocked:
114,738
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Armenia 314$0.29

How much is e-register.am worth?

Website Value:
$4,176.61

+ Where is e-register.am hosted?

Server IP:
91.221.228.249
ASN:
AS197497 
ISP:
Republic of Armenia Government staff Public administration Institution. 
Server Location:

Armenia, AM
 

Other sites hosted on 91.221.228.249

There are no other sites hosted on this IP

+ How fast does e-register.am load?

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

Page Speed (Google PageSpeed Insights) - Desktop

86
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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)998ms 75% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 75% 20% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 20% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)4ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 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 AVERAGE 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)1.3s 69% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 69% 23% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 23% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
First Input Delay (FID)3ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.8 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.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.
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 2.3 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.8 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 - 66 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
66
Maximum DOM Depth
9
Maximum Child Elements
7
Minify JavaScript - Potential savings of 18 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://www.e-register.am/static/scripts.v09.js
42 KB10 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB8 KB
Avoid multiple page redirects - Potential savings of 420 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://e-register.am/)
0
https://www.e-register.am/
190
https://www.e-register.am/am/
230
Keep request counts low and transfer sizes small - 12 requests • 119 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
12119 KB
Script
267 KB
Image
544 KB
Stylesheet
25 KB
Document
12 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 320 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.

URL
SizePotential Savings
https://www.e-register.am/static/styles.v10.css
4 KB70
https://www.e-register.am/static/scripts.v09.js
42 KB230
https://www.e-register.am/static/date_picker/date_picker.css
1 KB150
https://www.e-register.am/static/date_picker/date_picker.js
25 KB190
Efficiently encode images - Potential savings of 4 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.e-register.am/img/ereg-front.jpg
22 KB4 KB
Enable text compression - Potential savings of 52 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.e-register.am/static/scripts.v09.js
42 KB32 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB20 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://e-register.am/
0 ms533 ms0 KB0 KB302text/html
https://www.e-register.am/
534 ms1249 ms0 KB0 KB302text/html
https://www.e-register.am/am/
1249 ms1987 ms2 KB4 KB200text/htmlDocument
https://www.e-register.am/static/styles.v10.css
1999 ms2693 ms4 KB16 KB200text/cssStylesheet
https://www.e-register.am/static/scripts.v09.js
1999 ms3029 ms42 KB42 KB200text/javascriptScript
https://www.e-register.am/static/date_picker/date_picker.css
1999 ms2709 ms1 KB1 KB200text/cssStylesheet
https://www.e-register.am/static/date_picker/date_picker.js
1999 ms2890 ms25 KB25 KB200text/javascriptScript
https://www.e-register.am/img/ereg-front.jpg
2000 ms2859 ms22 KB22 KB200image/jpegImage
https://www.e-register.am/img/eu-logo.jpg
2000 ms2698 ms6 KB5 KB200image/jpegImage
https://www.e-register.am/img/registry_am.png
2699 ms3420 ms6 KB6 KB200image/pngImage
https://www.e-register.am/img/ereg-hd-am.png
3037 ms3736 ms6 KB6 KB200image/pngImage
https://www.e-register.am/img/bullet-f.png
3037 ms3732 ms4 KB4 KB200image/pngImage
Serve static assets with an efficient cache policy - 9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.e-register.am/static/scripts.v09.js
0 ms42 KB
https://www.e-register.am/static/date_picker/date_picker.js
0 ms25 KB
https://www.e-register.am/static/styles.v10.css
0 ms4 KB
https://www.e-register.am/static/date_picker/date_picker.css
0 ms1 KB
https://www.e-register.am/img/ereg-front.jpg
2419200000 ms22 KB
https://www.e-register.am/img/ereg-hd-am.png
2419200000 ms6 KB
https://www.e-register.am/img/registry_am.png
2419200000 ms6 KB
https://www.e-register.am/img/eu-logo.jpg
2419200000 ms6 KB
https://www.e-register.am/img/bullet-f.png
2419200000 ms4 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2016 ms
7 ms
3062 ms
45 ms
JavaScript execution time - 0.0 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
92 ms4 ms2 ms
Properly size images - Potential savings of 5 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://www.e-register.am/img/eu-logo.jpg
5 KB5 KB
Avoids enormous network payloads - Total size was 119 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.e-register.am/static/scripts.v09.js
42 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB
https://www.e-register.am/img/ereg-front.jpg
22 KB
https://www.e-register.am/img/ereg-hd-am.png
6 KB
https://www.e-register.am/img/registry_am.png
6 KB
https://www.e-register.am/img/eu-logo.jpg
6 KB
https://www.e-register.am/img/bullet-f.png
4 KB
https://www.e-register.am/static/styles.v10.css
4 KB
https://www.e-register.am/am/
2 KB
https://www.e-register.am/static/date_picker/date_picker.css
1 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
Style & Layout
45 ms
Other
26 ms
Rendering
11 ms
Script Evaluation
10 ms
Parse HTML & CSS
4 ms
Script Parsing & Compilation
4 ms
Serve images in next-gen formats - Potential savings of 14 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.

URL
SizePotential Savings
https://www.e-register.am/img/ereg-front.jpg
22 KB14 KB
Avoid chaining critical requests - 4 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.

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 740 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

83
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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)1.3s 75% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 62% 32% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 32% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)277ms 1% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 97% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 97% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an AVERAGE 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)1.4s 66% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 66% 26% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 26% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)272ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 97% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 97% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

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 2.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) 5010 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.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 2.5 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 2.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.

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

Resource Type
RequestsTransfer Size
Total
12119 KB
Script
267 KB
Image
544 KB
Stylesheet
25 KB
Document
12 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 870 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.

URL
SizePotential Savings
https://www.e-register.am/static/styles.v10.css
4 KB180
https://www.e-register.am/static/scripts.v09.js
42 KB330
https://www.e-register.am/static/date_picker/date_picker.css
1 KB180
https://www.e-register.am/static/date_picker/date_picker.js
25 KB180
Efficiently encode images - Potential savings of 4 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.e-register.am/img/ereg-front.jpg
22 KB4 KB
Enable text compression - Potential savings of 52 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.e-register.am/static/scripts.v09.js
42 KB32 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB20 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://e-register.am/
0 ms538 ms0 KB0 KB302text/html
https://www.e-register.am/
539 ms1269 ms0 KB0 KB302text/html
https://www.e-register.am/am/
1269 ms1984 ms2 KB4 KB200text/htmlDocument
https://www.e-register.am/static/styles.v10.css
1996 ms2709 ms4 KB16 KB200text/cssStylesheet
https://www.e-register.am/static/scripts.v09.js
1997 ms3003 ms42 KB42 KB200text/javascriptScript
https://www.e-register.am/static/date_picker/date_picker.css
1997 ms2707 ms1 KB1 KB200text/cssStylesheet
https://www.e-register.am/static/date_picker/date_picker.js
1997 ms2865 ms25 KB25 KB200text/javascriptScript
https://www.e-register.am/img/ereg-front.jpg
1997 ms2843 ms22 KB22 KB200image/jpegImage
https://www.e-register.am/img/eu-logo.jpg
1998 ms2693 ms6 KB5 KB200image/jpegImage
https://www.e-register.am/img/registry_am.png
2694 ms3385 ms6 KB6 KB200image/pngImage
https://www.e-register.am/img/ereg-hd-am.png
3011 ms3692 ms6 KB6 KB200image/pngImage
https://www.e-register.am/img/bullet-f.png
3012 ms3722 ms4 KB4 KB200image/pngImage
Serve static assets with an efficient cache policy - 9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.e-register.am/static/scripts.v09.js
0 ms42 KB
https://www.e-register.am/static/date_picker/date_picker.js
0 ms25 KB
https://www.e-register.am/static/styles.v10.css
0 ms4 KB
https://www.e-register.am/static/date_picker/date_picker.css
0 ms1 KB
https://www.e-register.am/img/ereg-front.jpg
2419200000 ms22 KB
https://www.e-register.am/img/ereg-hd-am.png
2419200000 ms6 KB
https://www.e-register.am/img/registry_am.png
2419200000 ms6 KB
https://www.e-register.am/img/eu-logo.jpg
2419200000 ms6 KB
https://www.e-register.am/img/bullet-f.png
2419200000 ms4 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2008 ms
8 ms
3032 ms
41 ms
JavaScript execution time - 0.0 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
338 ms13 ms4 ms
Avoids enormous network payloads - Total size was 119 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.e-register.am/static/scripts.v09.js
42 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB
https://www.e-register.am/img/ereg-front.jpg
22 KB
https://www.e-register.am/img/ereg-hd-am.png
6 KB
https://www.e-register.am/img/registry_am.png
6 KB
https://www.e-register.am/img/eu-logo.jpg
6 KB
https://www.e-register.am/img/bullet-f.png
4 KB
https://www.e-register.am/static/styles.v10.css
4 KB
https://www.e-register.am/am/
2 KB
https://www.e-register.am/static/date_picker/date_picker.css
1 KB
Minimizes main-thread work - 0.4 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
167 ms
Other
100 ms
Rendering
37 ms
Script Evaluation
35 ms
Parse HTML & CSS
16 ms
Script Parsing & Compilation
14 ms
Serve images in next-gen formats - Potential savings of 14 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.

URL
SizePotential Savings
https://www.e-register.am/img/ereg-front.jpg
22 KB14 KB
Avoids an excessive DOM size - 66 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
66
Maximum DOM Depth
9
Maximum Child Elements
7
Minify JavaScript - Potential savings of 18 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://www.e-register.am/static/scripts.v09.js
42 KB10 KB
https://www.e-register.am/static/date_picker/date_picker.js
25 KB8 KB
Avoid multiple page redirects - Potential savings of 1,410 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://e-register.am/)
0
https://www.e-register.am/
630
https://www.e-register.am/am/
780
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 720 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://e-register.am/
https://www.e-register.am/
https://www.e-register.am/am/

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 52.1KiB (77% reduction).

Compressing https://www.e-register.am/static/scripts.v09.js could save 32.4KiB (76% reduction).
Compressing https://www.e-register.am/static/date_picker/date_picker.js could save 19.7KiB (79% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.e-register.am/static/date_picker/date_picker.css (expiration not specified)
https://www.e-register.am/static/date_picker/date_picker.js (expiration not specified)
https://www.e-register.am/static/scripts.v09.js (expiration not specified)
https://www.e-register.am/static/styles.v10.css (expiration not specified)

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,015 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="/am/signin">Մուտք համակարգ</a> falls outside the viewport.
The element <a href="/ru/">Rus</a> falls outside the viewport.
The element <p>Հարգելի քաղաքացիներ,</p> falls outside the viewport.
The element <p>Նոր տիպի կորոն…ցանց եղանակով:</p> falls outside the viewport.
The element <p>Այդ նպատակով Հ…այությունները՝</p> falls outside the viewport.
The element <li>անհատ ձեռնարկա…կան հաշվառում,</li> falls outside the viewport.
The element <li>անհատ ձեռնարկա…փոփոխություն,</li> falls outside the viewport.
The element <li>նմուշային ձևի…նական գրանցում</li> falls outside the viewport.
The element <li>ընկերության գո…ի փոփոխություն</li> falls outside the viewport.
The element <p>Իրավաբանական ա…նց տարբերակով:</p> falls outside the viewport.
The element <a href="mailto:info@e-register.am">info@e-register.am</a> falls outside the viewport.
The element <p>Հրատապ հարցերի…ռախոսահամարով:</p> falls outside the viewport.
The element <div></div> falls outside the viewport.
The element <img src="/img/registry_am.png"> falls outside the viewport.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 16.5KiB (45% reduction).

Compressing https://www.e-register.am/img/ereg-front.jpg could save 9.3KiB (43% reduction).
Compressing https://www.e-register.am/img/bullet-f.png could save 3.2KiB (78% reduction).
Compressing https://www.e-register.am/img/ereg-hd-am.png could save 2KiB (35% reduction).
Compressing https://www.e-register.am/img/eu-logo.jpg could save 2KiB (37% reduction).

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 7.4KiB (31% reduction).

Minifying https://www.e-register.am/static/date_picker/date_picker.js could save 7.4KiB (31% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 663B (17% reduction).

Minifying https://www.e-register.am/static/styles.v10.css could save 663B (17% reduction) after compression.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does e-register.am use compression?

e-register.am use gzip compression.
Original size: 4.37 KB
Compressed size: 1.75 KB
File reduced by: 2.62 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

e-register.am supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: www.e-gov.am
Organization:
Location:
Issuer: Sectigo RSA Extended Validation Secure Server CA
Valid from: Nov 13 00:00:00 2019 GMT
Valid until: Dec 4 23:59:59 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

e-register.am does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 27 Mar 2020 02:35:04 GMT
Server: Apache
X-Powered-By: PHP/5.5.38
Set-Cookie: EREG_LANG=am; expires=Sat, 27-Mar-2021 02:35:04 GMT; Max-Age=31536000; path=/
Location: https://www.e-register.am
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Connection: close
Content-Type: text/html; charset=UTF-8

HTTP/1.1 302 Found
Date: Fri, 27 Mar 2020 02:35:05 GMT
Server: Apache
X-Powered-By: PHP/5.5.38
Set-Cookie: EREG_LANG=am; expires=Sat, 27-Mar-2021 02:35:05 GMT; Max-Age=31536000; path=/
Location: /am/
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Connection: close
Content-Type: text/html; charset=UTF-8

HTTP/1.1 200 OK
Date: Fri, 27 Mar 2020 02:35:05 GMT
Server: Apache
X-Powered-By: PHP/5.5.38
Set-Cookie: EREG_LANG=am; expires=Sat, 27-Mar-2021 02:35:05 GMT; Max-Age=31536000; path=/
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 1788
Connection: close
Content-Type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
MX mail.e-register.am 3600
SOA 3600
Mname ns.gov.am
Rname hostmaster.gov.am
Serial Number 2020021701
Refresh 43200
Retry 3600
Expire 2419200
Minimum TTL 0
TXT 3600
A 91.221.228.249 3563
NS ns.gov.am 3563
NS ns1.gov.am 3563

+ Whois Lookup

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

whois lookup at whois.amnic.net...
%
%AM TLD whois server #1
% Please see 'whois -h whois.amnic.net help' for usage.
%

Domain name: e-register.am
Registrar: amnic
Status: active

Registrant:
Government of the Republic of Armenia
Government House 1, Republic Square
Yerevan, 0010
AM

Administrative contact:
Lilit Avagyan
The Government of the Republic of Armenia
Government House 1, Republic Square
Yerevan, 0010
AM
email
+374 10 515905

Technical contact:
Armenak Ayvazyan
The Government of the Republic of Armenia
Government House 1, Republic Square
Yerevan, 0010
AM
email
+374 10 515904

DNS servers:
ns.gov.am
ns1.gov.am

Registered: 2011-01-25
Last modified: 2019-05-30
Last update was 6 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with e-register.am in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

smarkos.blogspot.com
22 secs
zenmanga.com
28 secs
zeoarchives.net
51 secs
skstyleshop.com
1 min
instantcoins.ng
1 min
yon***.com
2 mins
shkollainformatika.com
2 mins
refer.ng
2 mins
shkoder.info
3 mins
1v1.lol
3 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!
e-register.am widget