HAAPSALU.EE Üldinfo - Haapsalu Linnavalitsus


haapsalu.ee website information.

haapsalu.ee domain name is registered by .EE top-level domain registry. See the other sites registred in .EE domain zone.

Following name servers are specified for haapsalu.ee domain:

  • ns2.elion.ee
  • ns.elion.ee

and probably website haapsalu.ee is hosted by TIGGEE - Tiggee LLC, US web hosting company. Check the complete list of other most popular websites hosted by TIGGEE - Tiggee LLC, US hosting company.

According to Alexa traffic rank the highest website haapsalu.ee position was 46218 (in the world). The lowest Alexa rank position was 999435. Now website haapsalu.ee ranked in Alexa database as number 874453 (in the world).

Website haapsalu.ee Desktop speed measurement score (26/100) is better than the results of 6.47% of other sites shows that the page desktop performance can be improved.

haapsalu.ee Mobile usability score (90/100) is better than the results of 31.63% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of haapsalu.ee (28/100) is better than the results of 8.55% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Sep-22-2024 874,45312,192
Sep-21-2024 886,645-1,340
Sep-20-2024 885,30517,818
Sep-19-2024 903,1233,925
Sep-18-2024 907,048-9,158
Sep-17-2024 897,89021,055
Sep-16-2024 918,945-4,709

Advertisement

haapsalu.ee Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



haapsalu.ee whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Search results may not be used for commercial, advertising, recompilation,
repackaging, redistribution, reuse, obscuring or other similar activities.

Estonia .ee Top Level Domain WHOIS server

Domain:
name: haapsalu.ee
status: ok (paid and in zone)
registered: 2010-07-04 04:12:32 +03:00
changed: 2021-10-29 01:00:47 +03:00
expire: 2022-11-05
outzone:
delete:

Registrant:
name: HAAPSALU LINNAVALITSUS
org id: 75012802
country: EE
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: 2021-10-29 01:00:47 +03:00

Administrative contact:
name: Not Disclosed - Visit www.internet.ee for webbased WHOIS
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed - Visit www.internet.ee for webbased WHOIS

Technical contact:
name: Not Disclosed - Visit www.internet.ee for webbased WHOIS
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed - Visit www.internet.ee for webbased WHOIS

Registrar:
name: Telia Eesti AS
url: http://www.telia.ee
phone: +372 655 9188
changed: 2022-03-02 14:12:08 +02:00

Name servers:
nserver: cns2.estpak.ee
nserver: cns1.estpak.ee
changed: 2021-01-22 16:03:24 +02:00

Estonia .ee Top Level Domain WHOIS server
More information at http://internet.ee

haapsalu.ee server information

Servers Location

IP Address
195.80.124.7
Country
Estonia
Region
Harjumaa
City
Tallinn

haapsalu.ee desktop page speed rank

Last tested: 2019-10-31


Desktop Speed Bad
26/100

haapsalu.ee Desktop Speed Test Quick Summary


priority - 239 Optimize images

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

Optimize the following images to reduce their size by 2.3MiB (93% reduction).

Compressing https://www.haapsalu.ee/documents/377453/0/ban_336…ccd48b?t=1570707819627 could save 1.8MiB (99% reduction).
Compressing and resizing https://www.haapsalu.ee/documents/377464/22812011/…b865dd?t=1550492422179 could save 171.7KiB (94% reduction).
Compressing and resizing https://www.haapsalu.ee/documents/377464/20503601/…7cbadc?t=1570088859825 could save 122.7KiB (85% reduction).
Compressing and resizing https://www.haapsalu.ee/documents/377464/19659295/…1ebf5d?t=1566975888842 could save 86.5KiB (89% reduction).
Compressing https://www.haapsalu.ee/image/company_logo?img_id=551841&t=1572500007315 could save 70.4KiB (79% reduction).
Compressing https://www.haapsalu.ee/documents/377464/20206570/…c40d4c?t=1571990229712 could save 10.6KiB (19% reduction).
Compressing https://www.haapsalu.ee/documents/377464/25312615/…b2ce62?t=1571137075316 could save 7.8KiB (37% reduction).
Compressing https://www.haapsalu.ee/documents/377464/24018115/…4bde13?t=1560230657317 could save 2.4KiB (13% reduction).
Compressing https://www.haapsalu.ee/kovtp-2016-theme/images/custom/euroopa-liit.jpg could save 1.9KiB (46% reduction).
Compressing https://yt3.ggpht.com/-Jqq7NZ-te58/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 1.2KiB (42% reduction).

priority - 23 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 226.8KiB (67% reduction).

Compressing https://www.haapsalu.ee/html/js/barebone.jsp?brows…b=6102&t=1572259754000 could save 223.1KiB (67% reduction).
Compressing https://www.haapsalu.ee/kovtp-2016-theme/js/main.j…b=6102&t=1530524168000 could save 2.3KiB (74% reduction).
Compressing https://www.haapsalu.ee/combo/?browserId=other&min…uild/base-build-min.js could save 1.2KiB (50% reduction).
Compressing https://www.haapsalu.ee/combo/?browserId=other&min…m=/liferay/language.js could save 137B (31% reduction).
Compressing https://www.haapsalu.ee/html/js/liferay/available_…b=6102&t=1572259754000 could save 133B (41% reduction).

priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.haapsalu.ee/kovtp-2016-theme/js/jquery-1.10.2.min.js
https://www.haapsalu.ee/kovtp-2016-theme/js/myjs.js
https://www.google.com/recaptcha/api.js?render=explicit
https://www.haapsalu.ee/html/js/barebone.jsp?brows…b=6102&t=1572259754000

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Roboto+Sla…n+Sans:400,300,600,700
https://www.haapsalu.ee/html/css/main.css?browserI…b=6102&t=1376376222000
https://www.haapsalu.ee/kovtp-statistics-portlet/c…b=6102&t=1572259670000
https://www.haapsalu.ee/kovtp-important-links-port…b=6102&t=1572259624000
https://www.haapsalu.ee/html/portlet/journal_conte…b=6102&t=1572259385000
https://www.haapsalu.ee/kovtp-2016-theme/css/main.…b=6102&t=1530524168000

priority - 1 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.google.com/recaptcha/api.js?render=explicit (5 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)

haapsalu.ee Desktop Resources

Total Resources60
Number of Hosts12
Static Resources31
JavaScript Resources18
CSS Resources9

haapsalu.ee Desktop Resource Breakdown

haapsalu.ee mobile page speed rank

Last tested: 2018-05-21


Mobile Speed Bad
28/100

haapsalu.ee Mobile Speed Test Quick Summary


priority - 217 Optimize images

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

Optimize the following images to reduce their size by 2.1MiB (73% reduction).

Compressing and resizing http://www.haapsalu.ee/documents/377453/2568019/ve…ac850c?t=1524635796030 could save 2MiB (99% reduction).
Compressing http://www.haapsalu.ee/documents/377464/0/suvi_201…1b04a4?t=1526475869813 could save 84.9KiB (11% reduction).
Compressing http://www.haapsalu.ee/kovtp-new-theme/images/cust…lareng_horisontaal.jpg could save 16.3KiB (79% reduction).
Compressing http://www.haapsalu.ee/documents/377453/0/arenguko…74704a?t=1477459231905 could save 3.6KiB (50% reduction).
Compressing http://www.haapsalu.ee/kovtp-new-theme/images/custom/lock.png could save 2.7KiB (87% reduction).
Compressing http://www.haapsalu.ee/kovtp-new-theme/images/custom/icons.png could save 2.7KiB (46% reduction).
Compressing http://www.haapsalu.ee/documents/377453/0/Allalaad…c16919?t=1453296202996 could save 1.5KiB (12% reduction).
Compressing http://www.kultuurikava.ee/img/kultuurikava_150.png?9f2420dd could save 796B (15% reduction).
Compressing http://www.kultuurikava.ee/img/embed_arrow_right.png?bf44a565 could save 110B (35% reduction).
Compressing http://www.kultuurikava.ee/img/embed_arrow_left.png?86ba5070 could save 103B (33% reduction).

priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://www.haapsalu.ee/kovtp-new-theme/js/jquery-1.10.2.min.js
http://www.haapsalu.ee/html/js/barebone.jsp?browse…b=6102&t=1526558053000

Optimize CSS Delivery of the following:

http://www.haapsalu.ee/html/css/main.css?browserId…b=6102&t=1376376222000
http://www.haapsalu.ee/kovtp-important-links-portl…b=6102&t=1526558096000
http://www.haapsalu.ee/html/portlet/journal_conten…b=6102&t=1526557834000
http://www.haapsalu.ee/kovtp-statistics-portlet/cs…b=6102&t=1526558033000
http://www.haapsalu.ee/kovtp-new-theme/css/main.cs…b=6102&t=1426025880000

priority - 4 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:

http://www.haapsalu.ee/kovtp-new-theme/css/oswald.woff (expiration not specified)
http://www.kultuurikava.ee/js/embed.js (expiration not specified)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
http://maps.googleapis.com/maps/api/js?sensor=fals…218404864af3551e4.init (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 2 Reduce server response time

In our test, your server responded in 0.33 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.7KiB (17% reduction).

Minifying http://www.haapsalu.ee/ could save 1.7KiB (17% reduction) after compression.

priority - 0 Minify JavaScript

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

Minify JavaScript for the following resources to reduce their size by 121B (11% reduction).

Minifying http://www.haapsalu.ee/combo/?browserId=other&mini…uild/base-build-min.js could save 121B (11% reduction) after compression.

haapsalu.ee Mobile Resources

Total Resources72
Number of Hosts12
Static Resources50
JavaScript Resources25
CSS Resources11

haapsalu.ee Mobile Resource Breakdown

haapsalu.ee mobile page usability

Last tested: 2018-05-21


Mobile Usability Good
90/100

haapsalu.ee Mobile Usability Test Quick Summary


priority - 5 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://haapsal…/linnavalitsus">Linnavalitsus</a> and 4 others are close to other tap targets.
The tap target <div class="weekday">1</div> and 29 others are close to other tap targets.
The tap target <div class="weekday today">21</div> is close to 2 other tap targets.
The tap target <a href="mailto:hlv@haapsalulv.ee">hlv@haapsalulv.ee</a> and 1 others are close to other tap targets.

priority - 5 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 500 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <div class="col-md-6">toggle-navigation</div> falls outside the viewport.
The element <div class="col-md-6"></div> falls outside the viewport.
The element <img src="/documents/377…=1526475869813"> falls outside the viewport.
The element <iframe src="//www.youtube.…0600hX1g?rel=0"> falls outside the viewport.

haapsalu.ee similar domains

Similar domains:
www.haapsalu.com
www.haapsalu.net
www.haapsalu.org
www.haapsalu.info
www.haapsalu.biz
www.haapsalu.us
www.haapsalu.mobi
www.aapsalu.ee
www.haapsalu.ee
www.baapsalu.ee
www.hbaapsalu.ee
www.bhaapsalu.ee
www.gaapsalu.ee
www.hgaapsalu.ee
www.ghaapsalu.ee
www.yaapsalu.ee
www.hyaapsalu.ee
www.yhaapsalu.ee
www.uaapsalu.ee
www.huaapsalu.ee
www.uhaapsalu.ee
www.jaapsalu.ee
www.hjaapsalu.ee
www.jhaapsalu.ee
www.naapsalu.ee
www.hnaapsalu.ee
www.nhaapsalu.ee
www.hapsalu.ee
www.hqapsalu.ee
www.haqapsalu.ee
www.hqaapsalu.ee
www.hwapsalu.ee
www.hawapsalu.ee
www.hwaapsalu.ee
www.hsapsalu.ee
www.hasapsalu.ee
www.hsaapsalu.ee
www.hzapsalu.ee
www.hazapsalu.ee
www.hzaapsalu.ee
www.haqpsalu.ee
www.haaqpsalu.ee
www.hawpsalu.ee
www.haawpsalu.ee
www.haspsalu.ee
www.haaspsalu.ee
www.hazpsalu.ee
www.haazpsalu.ee
www.haasalu.ee
www.haaosalu.ee
www.haaposalu.ee
www.haaopsalu.ee
www.haalsalu.ee
www.haaplsalu.ee
www.haalpsalu.ee
www.haapalu.ee
www.haapwalu.ee
www.haapswalu.ee
www.haapwsalu.ee
www.haapealu.ee
www.haapsealu.ee
www.haapesalu.ee
www.haapdalu.ee
www.haapsdalu.ee
www.haapdsalu.ee
www.haapzalu.ee
www.haapszalu.ee
www.haapzsalu.ee
www.haapxalu.ee
www.haapsxalu.ee
www.haapxsalu.ee
www.haapaalu.ee
www.haapsaalu.ee
www.haapasalu.ee
www.haapslu.ee
www.haapsqlu.ee
www.haapsaqlu.ee
www.haapsqalu.ee
www.haapswlu.ee
www.haapsawlu.ee
www.haapsslu.ee
www.haapsaslu.ee
www.haapssalu.ee
www.haapszlu.ee
www.haapsazlu.ee
www.haapsau.ee
www.haapsapu.ee
www.haapsalpu.ee
www.haapsaplu.ee
www.haapsaou.ee
www.haapsalou.ee
www.haapsaolu.ee
www.haapsaku.ee
www.haapsalku.ee
www.haapsaklu.ee
www.haapsal.ee
www.haapsaly.ee
www.haapsaluy.ee
www.haapsalyu.ee
www.haapsalh.ee
www.haapsaluh.ee
www.haapsalhu.ee
www.haapsalj.ee
www.haapsaluj.ee
www.haapsalju.ee
www.haapsali.ee
www.haapsalui.ee
www.haapsaliu.ee

haapsalu.ee Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


haapsalu.ee TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.