220.lv website information.
220.lv domain name is registered by .LV top-level domain registry. See the other sites registred in .LV domain zone.
Following name servers are specified for 220.lv domain:
- eric.ns.cloudflare.com
- roxy.ns.cloudflare.com
and probably website 220.lv is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.
According to Alexa traffic rank the highest website 220.lv position was 119995 (in the world). The lowest Alexa rank position was 258427. Now website 220.lv ranked in Alexa database as number 154562 (in the world).
Website 220.lv Desktop speed measurement score (62/100) is better than the results of 38.44% of other sites shows that the page desktop performance can be improved.
220.lv Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of 220.lv (54/100) is better than the results of 41.82% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-17-2024 | 154,562 | 6,513 |
| Nov-16-2024 | 161,075 | 84 |
| Nov-15-2024 | 161,159 | 6,951 |
| Nov-14-2024 | 168,110 | -14,442 |
| Nov-13-2024 | 153,668 | 0 |
| Nov-12-2024 | 153,668 | 0 |
| Nov-11-2024 | 153,668 | 0 |
Advertisement
220.lv 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.
220.lv 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.
[Domain]
Domain: 220.lv
Status: active
[Holder]
Type: Legal person
Name: SIA "Pigu Latvia"
Address: Krasta iela 52, Riga, LV-1003, Latvija
RegNr: 43603025092
Visit: https://www.nic.lv/whois/contact/220.lv to contact.
[Tech]
Type: Natural person
Visit: https://www.nic.lv/whois/contact/220.lv to contact.
[Nservers]
Nserver: eric.ns.cloudflare.com
Nserver: roxy.ns.cloudflare.com
[Whois]
Updated: 2024-09-11T23:12:28.076617+00:00
[Disclaimer]
% The WHOIS service is provided solely for informational purposes.
%
% It is permitted to use the WHOIS service only for technical or administrative
% needs associated with the operation of the Internet or in order to contact
% the domain name holder over legal problems.
%
% Requestor will not use information obtained using WHOIS:
% * To allow, enable or in any other way to support sending of unsolicited mails (spam)
% * for any kind of advertising
% * to disrupt Internet stability and security
%
% It is not permitted to obtain (including copying) or re-use in any form or
% by any means all or quantitatively or qualitatively significant part
% of the WHOIS without NIC's express permission.
220.lv server information
220.lv desktop page speed rank
Last tested: 2019-12-11
220.lv Desktop Speed Test Quick Summary
priority - 39 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 384.8KiB (82% reduction).
Compressing and resizing https://lv1.pigugroup.eu/oxi/28dfbad4e55cc86c5840e39b64322de1.jpg could save 126.6KiB (92% reduction).
Compressing https://tpc.googlesyndication.com/simgad/16882166551339965438 could save 37KiB (60% reduction).
Compressing https://tpc.googlesyndication.com/simgad/1524307837187458308 could save 36.5KiB (71% reduction).
Compressing https://tpc.googlesyndication.com/simgad/3937862593083886074 could save 28.3KiB (69% reduction).
Compressing https://tpc.googlesyndication.com/simgad/15934493119852096397 could save 24.5KiB (69% reduction).
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 3 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://lv2.pigugroup.eu/static/facelift/build/header.min.js?r=14355
https://lv2.pigugroup.eu/static/assets/vanilla-slider.min.js?r=14355
https://lv3.pigugroup.eu/static/facelift/build/thi…ombined.min.js?r=14355
https://lv1.pigugroup.eu/static/facelift/build/app.min.js?r=14355
Optimize CSS Delivery of the following:
https://lv2.pigugroup.eu/static/facelift/build/styles.min.css?r=14355
https://lv3.pigugroup.eu/static/facelift/build/sty…extend.min.css?r=14355
priority - 6 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://ingest.exacaster.com/220lv/ (expiration not specified)
https://www.googletagmanager.com/gtm.js?id=GTM-KW79MM (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/lv_LV/all.js (20 minutes)
https://connect.facebook.net/signals/config/1528495217369370?v=2.8.1 (20 minutes)
https://connect.facebook.net/signals/config/942163432533482?v=2.8.1 (20 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 5 Reduce server response time
In our test, your server responded in 0.24 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 - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
76.4KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.
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 2.8KiB (22% reduction).
220.lv Desktop Resources
| Total Resources | 102 |
| Number of Hosts | 31 |
| Static Resources | 58 |
| JavaScript Resources | 31 |
| CSS Resources | 3 |
220.lv Desktop Resource Breakdown
220.lv mobile page speed rank
Last tested: 2017-11-18
220.lv Mobile Speed Test Quick Summary
priority - 48 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 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:
Optimize CSS Delivery of the following:
https://lv2.pigugroup.eu/assets/app/pigu-icons.min.css?r=14355
https://lv2.pigugroup.eu/jscript/third_party/font-…s/font-awesome.min.css
https://lv2.pigugroup.eu/assets/app/app.css?r=14355
https://fonts.googleapis.com/css?family=Open+Sans:…subset=latin,latin-ext
priority - 34 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.
https://220.lv/lv/
https://mobile.220.lv/lv/
priority - 8 Reduce server response time
In our test, your server responded in 0.34 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 - 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:
https://www.googletagmanager.com/gtm.js?id=GTM-KW79MM (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/942163432533482?v=2.8.1 (20 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0 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 650B (50% reduction).
220.lv Mobile Resources
| Total Resources | 83 |
| Number of Hosts | 27 |
| Static Resources | 53 |
| JavaScript Resources | 19 |
| CSS Resources | 5 |
220.lv Mobile Resource Breakdown
220.lv mobile page usability
Last tested: 2017-11-18
220.lv similar domains
www.220.net
www.220.org
www.220.info
www.220.biz
www.220.us
www.220.mobi
www.20.lv
www.220.lv
www.22.lv
220.lv 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.
220.lv 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.