E24.NO E24 - Først med økonominyhetene


e24.no website information.

e24.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 e24.no domain:

  • ns-foo.linpro.net
  • ns-zoo.linpro.net
  • ns-bar.linpro.net

and probably website e24.no is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.

According to Alexa traffic rank the highest website e24.no position was 3544 (in the world). The lowest Alexa rank position was 364230. Now website e24.no ranked in Alexa database as number 55956 (in the world).

Website e24.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.

e24.no Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

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

Weekly Rank Report

DateRankChange
Oct-24-2021 55,956-27,933
Oct-23-2021 28,023-23,741
Oct-22-2021 4,28224,795
Oct-21-2021 29,077-23,741
Oct-20-2021 5,336400
Oct-19-2021 5,736140,130
Oct-18-2021 145,86644,044

Advertisement

e24.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.



e24.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...............: E1289D-NORID
Domain Name................: e24.no
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSBA40H-NORID
Name Server Handle.........: NSFO5H-NORID
Name Server Handle.........: NSZO40H-NORID

Additional information:
Created: 2004-09-10
Last updated: 2020-08-12

e24.no server information

Servers Location

IP Address
195.88.55.47
Country
Norway
Region
Oslo
City
Oslo

e24.no desktop page speed rank

Last tested: 2019-12-02


Desktop Speed Medium
81/100

e24.no Desktop Speed Test Quick Summary


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

Your page has 1 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.

Optimize CSS Delivery of the following:

https://e24-3.vgc.no/e24-no/production/css/style.css?20191121125552

priority - 5 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://d33s3ffr7fotas.cloudfront.net/ad-takeover/3.1.2/ad-takeover.js (expiration not specified)
https://logs1189.xiti.com/hit.xiti (expiration not specified)
https://sdk.pulse.schibsted.com/gdpr-transparency-…/latest/gdpr-bundle.js (expiration not specified)
https://sdk.pulse.schibsted.com/plugins/activity-pings/plugin.js (expiration not specified)
https://sdk.pulse.schibsted.com/plugins/local-history/plugin.js (expiration not specified)
https://1.vgc.no/stats/linkpulse/linkpulse.js (60 minutes)
https://sdk.pulse.schibsted.com/loader.min.js (60 minutes)
https://sdk.pulse.schibsted.com/plugins/populate-d…ngage-values/plugin.js (60 minutes)
https://sdk.pulse.schibsted.com/pulse.min.js (60 minutes)
https://js-agent.newrelic.com/nr-1153.min.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 20.6KiB (49% reduction).

Minifying https://cdn.polyfill.io/v3/polyfill.js?features=Pr…aceWith,ResizeObserver could save 12.6KiB (50% reduction) after compression.
Minifying https://cdn.vgc.no/js/libs/intersection-observer/intersection-observer.js could save 3.5KiB (55% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/activity-pings/plugin.js could save 2.9KiB (51% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/local-history/plugin.js could save 1.5KiB (30% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/populate-d…ngage-values/plugin.js could save 173B (18% reduction) after compression.

priority - 1 Optimize images

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

Optimize the following images to reduce their size by 12KiB (25% reduction).

Compressing https://e24.vgc.no/sprites/dist/spritev2.png?545747265 could save 8KiB (36% reduction).
Compressing https://e24.vgc.no/drfront/images/2018/10/04/c=201…;w=234;h=210;97467.jpg could save 2.8KiB (15% reduction).
Compressing https://e24.vgc.no/drfront/images/2016/01/20/c=164…;w=234;h=186;68955.jpg could save 1.2KiB (19% reduction).

priority - 1 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 9.5KiB (64% reduction).

Compressing https://d33s3ffr7fotas.cloudfront.net/ad-takeover/3.1.2/ad-takeover.js could save 9.4KiB (65% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…np_1575311880170_26636 could save 123B (30% reduction).

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 3.6KiB (13% reduction).

Minifying https://e24.no/ could save 3.6KiB (13% reduction) after compression.

e24.no Desktop Resources

Total Resources60
Number of Hosts26
Static Resources39
JavaScript Resources28
CSS Resources4

e24.no Desktop Resource Breakdown

e24.no mobile page speed rank

Last tested: 2019-12-02


Mobile Speed Bad
63/100

e24.no Mobile Speed Test Quick Summary


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

Your page has 3 blocking script resources and 2 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.vgc.no/js/libs/intersection-observer/intersection-observer.js
https://e24-3.vgc.no/e24-no/production/bower_compo…-ably/dist/ably.min.js
https://e24-1.vgc.no/e24-no/production/js-next/mai…ndle.js?20191121125552

Optimize CSS Delivery of the following:

https://e24-3.vgc.no/e24-no/production/css/mobile.css?20191121125552
https://api.e24.no/parts/assets/styles.ca6bb461.css

priority - 7 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://d33s3ffr7fotas.cloudfront.net/ad-takeover/3.1.2/ad-takeover.js (expiration not specified)
https://logs1189.xiti.com/hit.xiti (expiration not specified)
https://sdk.pulse.schibsted.com/gdpr-transparency-…/latest/gdpr-bundle.js (expiration not specified)
https://sdk.pulse.schibsted.com/plugins/activity-pings/plugin.js (expiration not specified)
https://sdk.pulse.schibsted.com/plugins/local-history/plugin.js (expiration not specified)
https://1.vgc.no/stats/linkpulse/linkpulse.js (60 minutes)
https://sdk.pulse.schibsted.com/loader.min.js (60 minutes)
https://sdk.pulse.schibsted.com/plugins/populate-d…ngage-values/plugin.js (60 minutes)
https://sdk.pulse.schibsted.com/pulse.min.js (60 minutes)
https://js-agent.newrelic.com/nr-1153.min.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 20.6KiB (49% reduction).

Minifying https://cdn.polyfill.io/v3/polyfill.js?features=Pr…aceWith,ResizeObserver could save 12.6KiB (50% reduction) after compression.
Minifying https://cdn.vgc.no/js/libs/intersection-observer/intersection-observer.js could save 3.5KiB (55% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/activity-pings/plugin.js could save 2.9KiB (51% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/local-history/plugin.js could save 1.5KiB (30% reduction) after compression.
Minifying https://sdk.pulse.schibsted.com/plugins/populate-d…ngage-values/plugin.js could save 173B (18% reduction) after compression.

priority - 2 Optimize images

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

Optimize the following images to reduce their size by 17.1KiB (25% reduction).

Compressing https://e24.vgc.no/sprites/dist/sprite-mini@2x.png?551751731 could save 10.4KiB (32% reduction).
Compressing https://e24.vgc.no/sprites/dist/spritev2@2x.png?545747265 could save 5.7KiB (19% reduction).
Compressing https://e24.vgc.no/drfront/images/2016/01/20/c=175…;w=234;h=162;68955.jpg could save 1.1KiB (18% reduction).

priority - 1 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 9.5KiB (64% reduction).

Compressing https://d33s3ffr7fotas.cloudfront.net/ad-takeover/3.1.2/ad-takeover.js could save 9.4KiB (65% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…np_1575316889847_39123 could save 122B (30% reduction).

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 3.5KiB (14% reduction).

Minifying https://e24.no/ could save 3.5KiB (14% reduction) after compression.

e24.no Mobile Resources

Total Resources60
Number of Hosts26
Static Resources40
JavaScript Resources28
CSS Resources4

e24.no Mobile Resource Breakdown

e24.no mobile page usability

Last tested: 2019-12-02


Mobile Usability Good
99/100

e24.no Mobile Usability Test Quick Summary


priority - 0 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 <button type="button" class="PXRrU">Vis mer</button> is close to 1 other tap targets.

The tap target <a href="https://e24.no" class="_1yIQv"></a> is close to 1 other tap targets.

The tap target <a href="https://e24.no/pluss/" class="_2_Rxf">E24+</a> and 1 others are close to other tap targets.

The tap target <button type="button" class="_3DNWO">Søk</button> is close to 1 other tap targets.

The tap target <button type="button" class="IeXdS">MENYLUKK</button> is close to 1 other tap targets.

e24.no similar domains

Similar domains:
www.e24.com
www.e24.net
www.e24.org
www.e24.info
www.e24.biz
www.e24.us
www.e24.mobi
www.24.no
www.e24.no
www.w24.no
www.ew24.no
www.we24.no
www.s24.no
www.es24.no
www.se24.no
www.d24.no
www.ed24.no
www.de24.no
www.r24.no
www.er24.no
www.re24.no
www.e4.no
www.e2.no

e24.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.


e24.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.