NDLA.NO Nasjonal digital læringsarena -


ndla.no website information.

ndla.no domain name is registered by .NO top-level domain registry. See the other sites registred in .NO domain zone.

Following name servers are specified for ndla.no domain:

  • ns-1140.awsdns-14.org
  • ns-16.awsdns-02.com
  • ns-1881.awsdns-43.co.uk
  • ns-770.awsdns-32.net

and probably website ndla.no is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.

According to Alexa traffic rank the highest website ndla.no position was 113949 (in the world). The lowest Alexa rank position was 119403. Now website ndla.no ranked in Alexa database as number 119403 (in the world).

Website ndla.no Desktop speed measurement score (81/100) is better than the results of 71.91% of other sites and shows that the page is performing great on desktop computers.

ndla.no Mobile usability score (62/100) is better than the results of 7.29% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of ndla.no (64/100) is better than the results of 64.03% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-18-2024 119,403-1,894
Nov-17-2024 117,509-1,048
Nov-16-2024 116,46163
Nov-15-2024 116,5242,339
Nov-14-2024 118,863-2,603
Nov-13-2024 116,2600
Nov-12-2024 116,2600

Advertisement

ndla.no 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.



ndla.no 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.


% By looking up information in the domain registration directory
% 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...............: NDL33D-NORID
Domain Name................: ndla.no
Registrar Handle...........: REG910-NORID
Tech-c Handle..............: ESBH70R-NORID
Name Server Handle.........: NSAW16068H-NORID
Name Server Handle.........: NSAW16069H-NORID
Name Server Handle.........: NSAW16070H-NORID
Name Server Handle.........: NSAW16071H-NORID

Additional information:
Created: 2020-08-05
Last updated: 2024-08-05

ndla.no server information

Servers Location

IP Address
18.195.243.98
18.194.206.149
Region
Hessen
Hessen
City
Frankfurt am Main
Frankfurt am Main

ndla.no desktop page speed rank

Last tested: 2018-02-07


Desktop Speed Medium
81/100

ndla.no Desktop Speed Test Quick Summary


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

Your page has 1 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://cdn-b.ndla.no/sites/default/files/js/js_f6…83923203184d8.jsmin.js

Optimize CSS Delivery of the following:

https://cdn-b.ndla.no/sites/all/modules/ndla_fag_tabs/ndla_fag_tabs.css?k
https://cdn-a.ndla.no/sites/default/files/css/css_…91aaaf92937c458804.css
https://fonts.googleapis.com/css?family=Open+Sans:400,600

priority - 3 Optimize images

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

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

Compressing https://cdn-a.ndla.no/sites/all/themes/ndla2010/img/footer_bg.jpg could save 8.6KiB (43% reduction).
Compressing https://cdn-a.ndla.no/sites/all/themes/ndla2010/img/header_bg.jpg could save 3.2KiB (38% reduction).
Compressing https://cdn-c.ndla.no/sites/default/files/ndlafilm_128.png could save 2.5KiB (50% reduction).
Compressing and resizing https://ndla.no/sites/all/modules/ndla_utils/images/disp/close-cross.png could save 2.4KiB (74% reduction).
Compressing https://cdn-a.ndla.no/sites/default/files/fyr_128.png could save 2.1KiB (44% reduction).
Compressing https://cdn-b.ndla.no/sites/default/files/omndla_128.png could save 1.9KiB (45% reduction).
Compressing https://cdn-a.ndla.no/sites/default/files/eu_128.png could save 1.9KiB (42% reduction).
Compressing https://cdn-c.ndla.no/sites/default/files/dk_128.png could save 1.8KiB (45% reduction).
Compressing https://cdn-b.ndla.no/sites/default/files/deling_128.png could save 1.6KiB (36% reduction).
Compressing https://cdn-b.ndla.no/sites/default/files/samskrive_128.png could save 1.6KiB (54% reduction).
Compressing https://cdn-c.ndla.no/sites/default/files/youtube_128.png could save 1.5KiB (55% reduction).
Compressing https://cdn-b.ndla.no/sites/default/files/follow_128.png could save 1.5KiB (42% reduction).
Compressing https://cdn-c.ndla.no/sites/all/themes/ndla2010/logo.png could save 513B (33% reduction).
Compressing https://cdn-a.ndla.no/sites/all/themes/ndla2010/img/topbar_bg.png could save 318B (23% reduction).

priority - 3 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://alerter.ndla.no/files/dyn/outboard/alerter…dedCallback&r=25299762 (5 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P5SK7W (15 minutes)
https://connect.facebook.net/en_GB/all.js (20 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 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 19.2KiB (16% reduction).

Minifying https://cdn-b.ndla.no/sites/default/files/js/js_f6…83923203184d8.jsmin.js could save 19.1KiB (16% reduction) after compression.
Minifying https://cdn-c.ndla.no/sites/default/files/js/js_89…fccec9bc857db.jsmin.js could save 120B (25% reduction) after compression.

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 300B (41% reduction).

Compressing https://www.youtube.com/iframe_api could save 300B (41% reduction).

ndla.no Desktop Resources

Total Resources46
Number of Hosts19
Static Resources30
JavaScript Resources14
CSS Resources3

ndla.no Desktop Resource Breakdown

ndla.no mobile page speed rank

Last tested: 2017-05-13


Mobile Speed Bad
64/100

ndla.no 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 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:

http://cdn-a.ndlap3.seria.net/sites/default/files/…84d81465647f1.jsmin.js

Optimize CSS Delivery of the following:

http://cdn-c.ndlap3.seria.net/sites/all/modules/nd…bs/ndla_fag_tabs.css?7
http://cdn-b.ndlap3.seria.net/sites/default/files/…17334a49f6f19bfcee.css
https://fonts.googleapis.com/css?family=Open+Sans:400,600

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://ndla.tns-cs.net/blank.gif (expiration not specified)
https://alerter.ndla.no/files/dyn/outboard/alerter…dedCallback&r=24911894 (5 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-P5SK7W (15 minutes)
http://connect.facebook.net/en_GB/all.js (20 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
https://js-agent.newrelic.com/nr-1026.min.js (2 hours)

priority - 3 Optimize images

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

Optimize the following images to reduce their size by 29.5KiB (43% reduction).

Compressing http://cdn-b.ndlap3.seria.net/sites/all/themes/ndla2010/img/footer_bg.jpg could save 8.6KiB (43% reduction).
Compressing http://cdn-b.ndlap3.seria.net/sites/all/themes/ndla2010/img/header_bg.jpg could save 3.2KiB (38% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/ndlafilm_128.png could save 2.5KiB (50% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/fyr_128.png could save 2.1KiB (44% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/omndla_128.png could save 1.9KiB (45% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/eu_128.png could save 1.9KiB (42% reduction).
Compressing http://cdn-c.ndlap3.seria.net/sites/default/files/dk_128.png could save 1.8KiB (45% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/deling_128.png could save 1.6KiB (36% reduction).
Compressing http://cdn-b.ndlap3.seria.net/sites/default/files/samskrive_128.png could save 1.6KiB (54% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/youtube_128.png could save 1.5KiB (55% reduction).
Compressing http://cdn-a.ndlap3.seria.net/sites/default/files/follow_128.png could save 1.5KiB (42% reduction).
Compressing http://ndla.no/sites/all/modules/ndla_utils/images/disp/close-cross.png could save 1,020B (31% reduction).
Compressing http://cdn-b.ndlap3.seria.net/sites/all/themes/ndla2010/logo.png could save 513B (33% reduction).

priority - 2 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 19KiB (16% reduction).

Minifying http://cdn-a.ndlap3.seria.net/sites/default/files/…84d81465647f1.jsmin.js could save 19KiB (16% reduction) after compression.

ndla.no Mobile Resources

Total Resources47
Number of Hosts20
Static Resources31
JavaScript Resources14
CSS Resources3

ndla.no Mobile Resource Breakdown

ndla.no mobile page usability

Last tested: 2017-05-13


Mobile Usability Bad
62/100

ndla.no Mobile Usability Test Quick Summary


priority - 40 Use 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.

English and 1 others render only 5 pixels tall (12 CSS pixels).

| renders only 5 pixels tall (12 CSS pixels).

Open Education…ondary Schools renders only 6 pixels tall (15 CSS pixels).

Resource map renders only 5 pixels tall (12 CSS pixels).

Studiespesialisering and 2 others render only 7 pixels tall (18 CSS pixels).

Sørsamisk som…språk YF og SF and 45 others render only 5 pixels tall (13 CSS pixels).

BETA and 5 others render only 4 pixels tall (10 CSS pixels).

About NDLA and 3 others render only 5 pixels tall (13 CSS pixels).

as an open sou…ject, based on and 3 others render only 5 pixels tall (12 CSS pixels).

Drupal and 1 others render only 5 pixels tall (12 CSS pixels).

Contact us renders only 5 pixels tall (14 CSS pixels).

ndla.no uses c…this website. renders only 5 pixels tall (14 CSS pixels).

Read more abou…se of cookies. renders only 5 pixels tall (14 CSS pixels).

priority - 15 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="#" class="language js">English</a> is close to 1 other tap targets.

The tap target <a href="/en/node/42" class="subject_link nid-42">Engelsk</a> and 44 others are close to other tap targets.

The tap target <a href="/nb/node/137414" class="subject_link nid-137414">Brønnteknikk Vg2Beta</a> and 1 others are close to other tap targets.

The tap target <a href="/en/node/59982">Help</a> and 2 others are close to other tap targets.

The tap target <a href="http://om.ndla.no">NDLA</a> and 1 others are close to other tap targets.

The tap target <a href="https://www.fa…ok.com/ndla.no" class="fa-stack fa-lg"></a> and 2 others are close to other tap targets.

The tap target <a href="https://www.fa…ok.com/ndla.no" class="fa-stack fa-lg"></a> is close to 2 other tap targets.

The tap target <a href="https://twitter.com/ndla_no" class="fa-stack fa-lg"></a> is close to 4 other tap targets.

The tap target <a href="https://plus.g…le.com/+ndlano" class="fa-stack fa-lg"></a> is close to 2 other tap targets.

priority - 10 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.

ndla.no similar domains

Similar domains:
www.ndla.com
www.ndla.net
www.ndla.org
www.ndla.info
www.ndla.biz
www.ndla.us
www.ndla.mobi
www.dla.no
www.ndla.no
www.bdla.no
www.nbdla.no
www.bndla.no
www.hdla.no
www.nhdla.no
www.hndla.no
www.jdla.no
www.njdla.no
www.jndla.no
www.mdla.no
www.nmdla.no
www.mndla.no
www.nla.no
www.nxla.no
www.ndxla.no
www.nxdla.no
www.nsla.no
www.ndsla.no
www.nsdla.no
www.nela.no
www.ndela.no
www.nedla.no
www.nrla.no
www.ndrla.no
www.nrdla.no
www.nfla.no
www.ndfla.no
www.nfdla.no
www.ncla.no
www.ndcla.no
www.ncdla.no
www.nda.no
www.ndpa.no
www.ndlpa.no
www.ndpla.no
www.ndoa.no
www.ndloa.no
www.ndola.no
www.ndka.no
www.ndlka.no
www.ndkla.no
www.ndl.no
www.ndlq.no
www.ndlaq.no
www.ndlqa.no
www.ndlw.no
www.ndlaw.no
www.ndlwa.no
www.ndls.no
www.ndlas.no
www.ndlsa.no
www.ndlz.no
www.ndlaz.no
www.ndlza.no

ndla.no 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.


ndla.no 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.