disnorge.no Website Information
Daily Unique Visits: 1,184
Daily Page Views: 2,368
Income Per Day: $7
Estimated Value: $1,680
This website is located in Norway and is using following IP address 89.250.116.122. See the complete list of popular websites hosted in Norway.
disnorge.no is registered under .NO top-level domain. Please check other sites in .NO zone.
Website disnorge.no is using the following name servers:
- ns1.hyp.net
- ns3.hyp.net
- ns2.hyp.net
and is probably hosted by Basefarm AS. See the full list of other websites hosted by Basefarm AS.
The highest website disnorge.no position in Alexa rank database was 64999 and the lowest rank position was 984462. Current position of disnorge.no in Alexa rank database is 605624.
Desktop speed score of disnorge.no (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of disnorge.no (71/100) is better than the results of 21.61% of other sites and means that the page is not mobile-friendly.
Mobile speed score of disnorge.no (73/100) is better than the results of 81.47% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
disnorge.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.
disnorge.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...............: DIS839D-NORID
Domain Name................: disnorge.no
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSHY11H-NORID
Name Server Handle.........: NSHY46H-NORID
Name Server Handle.........: NSHY81H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 28882
Algorithm 1...........: 13
Digest Type 1...........: 2
Digest 1...........: 36e6de2247c5eabd133ef9cb400b91bbb57ce085a38837c56d7a5c2934d537ff
DS Key Tag 2...........: 28882
Algorithm 2...........: 13
Digest Type 2...........: 4
Digest 2...........: c4ea088caa247ef5c108531c0a630744f4e9a2a6d790397ca1d71cd991247f515a6d9ed400c2a5695b6eb5a0889ee8b0
Additional information:
Created: 1999-11-15
Last updated: 2023-10-18
disnorge.no server information
Servers Location
disnorge.no desktop page speed rank
Last tested: 2018-08-23
disnorge.no Desktop Speed Test Quick Summary
priority - 8Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 78.7KiB (28% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge/disweb_topp_www.jpg could save 29.4KiB (21% reduction).
Compressing http://www.disnorge.no/cms/system/files/offentlige_filer/forside.JPG could save 16.2KiB (18% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge/flag_en_40x20.png could save 713B (45% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge/flag_no_27x20.png could save 142B (35% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge//hover.png could save 108B (50% reduction).
priority - 4Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
http://www.disnorge.no/cms/modules/node/node.css?u
http://www.disnorge.no/cms/modules/system/defaults.css?u
http://www.disnorge.no/cms/modules/system/system.css?u
http://www.disnorge.no/cms/modules/system/system-menus.css?u
http://www.disnorge.no/cms/modules/user/user.css?u
http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u
http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u
http://www.disnorge.no/cms/sites/all/themes/disnorge/style.css?u
priority - 3Avoid 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://www.disnorge.no/
http://www.disnorge.no/cms/
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 20.6KiB (69% reduction).
Compressing http://www.disnorge.no/cms/modules/system/system.css?u could save 7KiB (71% reduction).
Compressing http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u could save 1.8KiB (66% reduction).
Compressing http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u could save 1.2KiB (64% reduction).
Compressing http://www.disnorge.no/cms/modules/user/user.css?u could save 634B (59% reduction).
Compressing http://www.disnorge.no/cms/modules/system/system-menus.css?u could save 547B (62% reduction).
Compressing http://www.disnorge.no/cms/modules/book/book.css?u could save 545B (58% reduction).
Compressing http://www.disnorge.no/cms/modules/node/node.css?u could save 358B (52% reduction).
Compressing http://www.disnorge.no/cms/modules/system/defaults.css?u could save 317B (46% reduction).
priority - 1Leverage 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://connect.facebook.net/en_GB/all.js (20 minutes)
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 7.9KiB (27% reduction).
Minifying http://www.disnorge.no/cms/modules/system/system.css?u could save 2.6KiB (28% reduction).
Minifying http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u could save 750B (27% reduction).
Minifying http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u could save 461B (24% reduction).
Minifying http://www.disnorge.no/cms/modules/system/defaults.css?u could save 292B (43% reduction).
Minifying http://www.disnorge.no/cms/modules/user/user.css?u could save 272B (26% reduction).
Minifying http://www.disnorge.no/cms/modules/system/system-menus.css?u could save 197B (23% reduction).
Minifying http://www.disnorge.no/cms/modules/book/book.css?u could save 149B (17% reduction).
Minifying http://www.disnorge.no/cms/modules/node/node.css?u could save 134B (20% reduction).
disnorge.no Desktop Resource Breakdown
Total Resources | 27 |
Number of Hosts | 8 |
Static Resources | 17 |
JavaScript Resources | 2 |
CSS Resources | 9 |
disnorge.no mobile page speed rank
Last tested: 2018-01-27
disnorge.no Mobile Speed Test Quick Summary
priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 9 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
http://www.disnorge.no/cms/modules/node/node.css?u
http://www.disnorge.no/cms/modules/system/defaults.css?u
http://www.disnorge.no/cms/modules/system/system.css?u
http://www.disnorge.no/cms/modules/system/system-menus.css?u
http://www.disnorge.no/cms/modules/user/user.css?u
http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u
http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u
http://www.disnorge.no/cms/sites/all/themes/disnorge/style.css?u
priority - 10Avoid 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://www.disnorge.no/
http://www.disnorge.no/cms/
priority - 6Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 57.7KiB (22% reduction).
Compressing http://www.disnorge.no/cms/system/files/offentlige_filer/forside.JPG could save 16.2KiB (18% reduction).
Compressing https://vht.tradedoubler.com/file/200316/2016-09-0…dlibris_DIY160x600.jpg could save 11.2KiB (32% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge/flag_en_40x20.png could save 713B (45% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge/flag_no_27x20.png could save 142B (35% reduction).
Compressing http://www.disnorge.no/cms/sites/all/themes/disnorge//hover.png could save 108B (50% 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 20.6KiB (69% reduction).
Compressing http://www.disnorge.no/cms/modules/system/system.css?u could save 7KiB (71% reduction).
Compressing http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u could save 1.8KiB (66% reduction).
Compressing http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u could save 1.2KiB (64% reduction).
Compressing http://www.disnorge.no/cms/modules/user/user.css?u could save 634B (59% reduction).
Compressing http://www.disnorge.no/cms/modules/system/system-menus.css?u could save 547B (62% reduction).
Compressing http://www.disnorge.no/cms/modules/book/book.css?u could save 545B (58% reduction).
Compressing http://www.disnorge.no/cms/modules/node/node.css?u could save 358B (52% reduction).
Compressing http://www.disnorge.no/cms/modules/system/defaults.css?u could save 317B (46% reduction).
priority - 1Leverage 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://connect.facebook.net/en_GB/all.js (20 minutes)
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 7.9KiB (27% reduction).
Minifying http://www.disnorge.no/cms/modules/system/system.css?u could save 2.6KiB (28% reduction).
Minifying http://www.disnorge.no/cms/sites/all/modules/ckeditor/ckeditor.css?u could save 750B (27% reduction).
Minifying http://www.disnorge.no/cms/sites/all/modules/views/css/views.css?u could save 461B (24% reduction).
Minifying http://www.disnorge.no/cms/modules/system/defaults.css?u could save 292B (43% reduction).
Minifying http://www.disnorge.no/cms/modules/user/user.css?u could save 272B (26% reduction).
Minifying http://www.disnorge.no/cms/modules/system/system-menus.css?u could save 197B (23% reduction).
Minifying http://www.disnorge.no/cms/modules/book/book.css?u could save 149B (17% reduction).
Minifying http://www.disnorge.no/cms/modules/node/node.css?u could save 134B (20% reduction).
disnorge.no Mobile Resource Breakdown
Total Resources | 29 |
Number of Hosts | 9 |
Static Resources | 17 |
JavaScript Resources | 2 |
CSS Resources | 9 |
disnorge.no mobile page usability
Last tested: 2018-01-27
disnorge.no Mobile Usability Test Quick Summary
priority - 21Size 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,840 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<h2 class="title">.</h2>
falls outside the viewport.The element
<p></p>
falls outside the viewport.The element
<a href="https://slektogdata.no">www.slektogdata.no</a>
falls outside the viewport.The element
<img src="/cms/system/fi…er/forside.JPG">
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
<div class="skille"></div>
falls outside the viewport.The element
<hr>
falls outside the viewport.priority - 10Configure 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.
priority - 5Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Pålogging
renders only 6 pixels tall (15 CSS pixels).Brukernavn:
and 1 others render only 5 pixels tall (13 CSS pixels).*
and 1 others render only 5 pixels tall (13 CSS pixels).Les mer om
renders only 5 pixels tall (13 CSS pixels).Gravminner og Paypal >>
renders only 5 pixels tall (13 CSS pixels)..
renders only 7 pixels tall (18 CSS pixels).Lagt inn av , 27.jun 2017
renders only 4 pixels tall (10 CSS pixels).© 1999-2018, DIS-Norge
renders only 4 pixels tall (10 CSS pixels).webmaster@disnorge.no
renders only 4 pixels tall (10 CSS pixels).priority - 5Size 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="/cms/en/eng/english-pages"></a>
and 1 others are close to other tap targets.<input id="edit-name" type="text" name="name" class="form-text required">
and 1 others are close to other tap targets.<label for="edit-pass">Passord: *</label>
is close to 1 other tap targets.<input id="edit-submit" type="submit" name="op" class="form-submit">
is close to 1 other tap targets.<a href="https://slektogdata.no">www.slektogdata.no</a>
is close to 1 other tap targets.disnorge.no HTML validation
Errors
Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.
"...<html> <head..."
Bad value “0;url=http://www.disnorge.no/cms/” for attribute “content” on element “meta”: Expected a space character, but saw “u” instead.
"...g</title> <meta http-equiv="refresh" content="0;url=http://www.disnorge.no/cms/"> </bod..."
disnorge.no similar domains
www.disnorge.net
www.disnorge.org
www.disnorge.info
www.disnorge.biz
www.disnorge.us
www.disnorge.mobi
www.isnorge.no
www.disnorge.no
www.xisnorge.no
www.dxisnorge.no
www.xdisnorge.no
www.sisnorge.no
www.dsisnorge.no
www.sdisnorge.no
www.eisnorge.no
www.deisnorge.no
www.edisnorge.no
www.risnorge.no
www.drisnorge.no
www.rdisnorge.no
www.fisnorge.no
www.dfisnorge.no
www.fdisnorge.no
www.cisnorge.no
www.dcisnorge.no
www.cdisnorge.no
www.dsnorge.no
www.dusnorge.no
www.diusnorge.no
www.duisnorge.no
www.djsnorge.no
www.dijsnorge.no
www.djisnorge.no
www.dksnorge.no
www.diksnorge.no
www.dkisnorge.no
www.dosnorge.no
www.diosnorge.no
www.doisnorge.no
www.dinorge.no
www.diwnorge.no
www.diswnorge.no
www.diwsnorge.no
www.dienorge.no
www.disenorge.no
www.diesnorge.no
www.didnorge.no
www.disdnorge.no
www.didsnorge.no
www.diznorge.no
www.disznorge.no
www.dizsnorge.no
www.dixnorge.no
www.disxnorge.no
www.dixsnorge.no
www.dianorge.no
www.disanorge.no
www.diasnorge.no
www.disorge.no
www.disborge.no
www.disnborge.no
www.disbnorge.no
www.dishorge.no
www.disnhorge.no
www.dishnorge.no
www.disjorge.no
www.disnjorge.no
www.disjnorge.no
www.dismorge.no
www.disnmorge.no
www.dismnorge.no
www.disnrge.no
www.disnirge.no
www.disnoirge.no
www.disniorge.no
www.disnkrge.no
www.disnokrge.no
www.disnkorge.no
www.disnlrge.no
www.disnolrge.no
www.disnlorge.no
www.disnprge.no
www.disnoprge.no
www.disnporge.no
www.disnoge.no
www.disnoege.no
www.disnorege.no
www.disnoerge.no
www.disnodge.no
www.disnordge.no
www.disnodrge.no
www.disnofge.no
www.disnorfge.no
www.disnofrge.no
www.disnotge.no
www.disnortge.no
www.disnotrge.no
www.disnore.no
www.disnorfe.no
www.disnorgfe.no
www.disnorve.no
www.disnorgve.no
www.disnorvge.no
www.disnorte.no
www.disnorgte.no
www.disnorbe.no
www.disnorgbe.no
www.disnorbge.no
www.disnorye.no
www.disnorgye.no
www.disnoryge.no
www.disnorhe.no
www.disnorghe.no
www.disnorhge.no
www.disnorg.no
www.disnorgw.no
www.disnorgew.no
www.disnorgwe.no
www.disnorgs.no
www.disnorges.no
www.disnorgse.no
www.disnorgd.no
www.disnorged.no
www.disnorgde.no
www.disnorgr.no
www.disnorger.no
www.disnorgre.no
disnorge.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.
disnorge.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.