lhl.no Website Information
Daily Unique Visits: 3,886
Daily Page Views: 15,544
Income Per Day: $44
Estimated Value: $23,760
This website is located in Norway and is using following IP address 137.221.28.204. See the complete list of popular websites hosted in Norway.
lhl.no is registered under .NO top-level domain. Please check other sites in .NO zone.
Website lhl.no is using the following name servers:
- ns1.hyp.net
- ns2.hyp.net
- ns3.hyp.net
and is probably hosted by EPiServer AB. See the full list of other websites hosted by EPiServer AB.
The highest website lhl.no position in Alexa rank database was 31613 and the lowest rank position was 995369. Current position of lhl.no in Alexa rank database is 322921.
Desktop speed score of lhl.no (74/100) is better than the results of 57.94% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of lhl.no (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed score of lhl.no (55/100) is better than the results of 43.86% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
lhl.no Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
lhl.no whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
% service, you confirm that you accept the terms and conditions of the
% service:
% https://www.norid.no/en/domeneoppslag/vilkar/
%
% Norid AS holds the copyright to the lookup service, content,
% layout and the underlying collections of information used in the
% service (cf. the Act on Intellectual Property of May 2, 1961, No.
% 2). Any commercial use of information from the service, including
% targeted marketing, is prohibited. Using information from the domain
% registration directory service in violation of the terms and
% conditions may result in legal prosecution.
%
% The whois service at port 43 is intended to contribute to resolving
% technical problems where individual domains threaten the
% functionality, security and stability of other domains or the
% internet as an infrastructure. It does not give any information
% about who the holder of a domain is. To find information about a
% domain holder, please visit our website:
% https://www.norid.no/en/domeneoppslag/
Domain Information
NORID Handle...............: LHL30D-NORID
Domain Name................: lhl.no
Registrar Handle...........: REG908-NORID
Tech-c Handle..............: NH112R-NORID
Name Server Handle.........: NSNI246H-NORID
Name Server Handle.........: NSNI247H-NORID
Name Server Handle.........: NSNI248H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 14647
Algorithm 1...........: 13
Digest Type 1...........: 2
Digest 1...........: 6caab73347823fdb3ec1aece6dd1b053bd126bb6e8148e7b32694be6de4b1245
DS Key Tag 2...........: 14647
Algorithm 2...........: 13
Digest Type 2...........: 4
Digest 2...........: c060feeb44828cdc7697a9b569e3db11815286d1ae7594d7a9b91994e996cf8dae7a0ddb8a340d404fe7e619f1ec8baa
Additional information:
Created: 1999-11-15
Last updated: 2021-11-15
lhl.no server information
Servers Location
lhl.no desktop page speed rank
Last tested: 2017-05-31
lhl.no Desktop Speed Test Quick Summary
priority - 9Avoid 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://lhl.no/
https://www.lhl.no/
priority - 8Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 72.3KiB (29% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/yOZ_HXkNWEI.png could save 14.6KiB (24% reduction).
Compressing https://www.lhl.no/globalassets/forside-lhl.no/pas…d/klinikk_4_44x550.jpg could save 12.7KiB (22% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/tYsG6g3XVvj.png could save 4.2KiB (22% reduction).
Compressing https://www.lhl.no/globalassets/logo1.png could save 1.4KiB (16% reduction).
Compressing https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x…667edf1ea3&oe=59E2D724 could save 573B (14% reduction).
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.lhl.no/ui/css-responsive?v=Jvqy8hHKDH8…kplmrGgtyc9ybIZh-EM_U1
priority - 8Leverage 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://use.typekit.net/ulu5ocw.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TBPQSN (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/nb_NO/all.js (20 minutes)
https://connect.facebook.net/signals/config/1720395204862000?v=2.7.12 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://siteimproveanalytics.com/js/siteanalyze_6078482.js (4 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_2_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_3_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…ud/klinikk_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…d/klinikk_4_44x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_5_440x550.jpg (12 hours)
https://www.lhl.no/globalassets/logo1.png (12 hours)
https://www.lhl.no/Styles/gfx/embed/bgLeftside.png (24 hours)
https://www.lhl.no/Styles/gfx/printLogo.png (24 hours)
priority - 2Enable 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 15.2KiB (65% reduction).
lhl.no Desktop Resource Breakdown
Total Resources | 149 |
Number of Hosts | 24 |
Static Resources | 108 |
JavaScript Resources | 49 |
CSS Resources | 14 |
lhl.no mobile page speed rank
Last tested: 2017-05-31
lhl.no Mobile Speed Test Quick Summary
priority - 34Avoid 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://lhl.no/
https://www.lhl.no/
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.lhl.no/ui/css-responsive?v=Jvqy8hHKDH8…kplmrGgtyc9ybIZh-EM_U1
priority - 12Leverage 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://use.typekit.net/ulu5ocw.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-TBPQSN (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/nb_NO/all.js (20 minutes)
https://connect.facebook.net/signals/config/1720395204862000?v=2.7.12 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://siteimproveanalytics.com/js/siteanalyze_6078482.js (4 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_3_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_5_440x550.jpg (12 hours)
https://www.lhl.no/globalassets/logo1.png (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…/klinikk_2_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…ud/klinikk_400x550.jpg (12 hours)
https://www.lhl.no/globalassets/forside-lhl.no/pas…d/klinikk_4_44x550.jpg (12 hours)
https://www.lhl.no/Styles/gfx/embed/icMenuTrigger.png (24 hours)
https://www.lhl.no/Styles/gfx/embed/icSearchTrigger.png (24 hours)
https://www.lhl.no/Styles/gfx/printLogo.png (24 hours)
priority - 8Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 73.2KiB (29% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/yOZ_HXkNWEI.png could save 14.6KiB (24% reduction).
Compressing https://www.lhl.no/globalassets/forside-lhl.no/pas…d/klinikk_4_44x550.jpg could save 12.7KiB (22% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/tYsG6g3XVvj.png could save 4.2KiB (22% reduction).
Compressing https://www.lhl.no/globalassets/logo1.png could save 1.4KiB (16% reduction).
Compressing https://external-atl3-1.xx.fbcdn.net/safe_image.ph…_hash=AQD7Lgs0t3qDd0ju could save 902B (11% reduction).
Compressing https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x…667edf1ea3&oe=59E2D724 could save 573B (14% reduction).
priority - 2Enable 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 15.2KiB (65% reduction).
lhl.no Mobile Resource Breakdown
Total Resources | 144 |
Number of Hosts | 25 |
Static Resources | 103 |
JavaScript Resources | 49 |
CSS Resources | 14 |
lhl.no mobile page usability
Last tested: 2017-05-31
lhl.no Mobile Usability Test Quick Summary
priority - 0Size 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.
<a href="https://m.face…Fwww.lhl.no%2F">LHL, Landsfore…- og lungesyke</a>
is close to 1 other tap targets.The tap target
<a href="https://m.face…Fwww.lhl.no%2F" class="_5pcq">23. mai kl. 04:24</a>
is close to 1 other tap targets.The tap target
<a href="mailto:post@lhl.no">post@lhl.no</a>
and 3 others are close to other tap targets.lhl.no HTML validation
lhl.no similar domains
www.lhl.net
www.lhl.org
www.lhl.info
www.lhl.biz
www.lhl.us
www.lhl.mobi
www.hl.no
www.lhl.no
www.phl.no
www.lphl.no
www.plhl.no
www.ohl.no
www.lohl.no
www.olhl.no
www.khl.no
www.lkhl.no
www.klhl.no
www.ll.no
www.lbl.no
www.lhbl.no
www.lbhl.no
www.lgl.no
www.lhgl.no
www.lghl.no
www.lyl.no
www.lhyl.no
www.lyhl.no
www.lul.no
www.lhul.no
www.luhl.no
www.ljl.no
www.lhjl.no
www.ljhl.no
www.lnl.no
www.lhnl.no
www.lnhl.no
www.lh.no
www.lhp.no
www.lhlp.no
www.lhpl.no
www.lho.no
www.lhlo.no
www.lhol.no
www.lhk.no
www.lhlk.no
www.lhkl.no
lhl.no Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
lhl.no TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.