VG.NO Forsiden - VG


vg.no website information.

vg.no website servers are located in Norway and are responding from following IP address 195.88.55.16. Check the full list of most visited websites located in Norway.

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

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

and probably website vg.no is hosted by linpro.net web hosting company. Check the complete list of other most popular websites hosted by linpro.net hosting company.

According to Alexa traffic rank the highest website vg.no position was 893 (in the world). The lowest Alexa rank position was 6788. Now website vg.no ranked in Alexa database as number 1631 (in the world).

Website vg.no Desktop speed measurement score (67/100) is better than the results of 46.16% of other sites shows that the page desktop performance can be improved.

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

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

Weekly Rank Report

DateRankChange
Sep-21-2019 N/AN/A
Sep-20-2019 1,6311,953
Sep-19-2019 3,584-1,909
Sep-18-2019 1,675-438
Sep-17-2019 1,237349
Sep-16-2019 1,586-331
Sep-15-2019 1,2551,702

Advertisement

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


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


% Kopibeskyttet, se http://www.norid.no/domenenavnbaser/whois/kopirett.html
% Rights restricted by copyright. See http://www.norid.no/domenenavnbaser/whois/kopirett.en.html

Domain Information

NORID Handle...............: VG33D-NORID
Domain Name................: vg.no
Domain Holder Handle.......: VGA154O-NORID
Registrar Handle...........: REG271-NORID
Legal-c Handle.............: AY148P-NORID
Tech-c Handle..............: AY148P-NORID
Name Server Handle.........: NSBA39H-NORID
Name Server Handle.........: NSFO4H-NORID
Name Server Handle.........: NSZO39H-NORID

Additional information:
Created: 2011-06-10
Last updated: 2017-06-10

NORID Handle...............: VGA154O-NORID
Type.......................: organization
Name.......................: VERDENS GANG AS
Id Type....................: organization_number
Id Number..................: 950588063
Registrar Handle...........: REG271-NORID
Post Address...............: Postboks 1185 Sentrum
Postal Code................: NO-0107
Postal Area................: OSLO
Country....................: NO
Phone Number...............: +47.22000000
Fax Number.................: +47.22000305
Email Address..............: vg@vg.no

Additional information:
Created: 2011-06-10
Last updated: 2011-06-10

vg.no server information

Servers Location

vg.no desktop page speed rank

Last tested: 2018-01-29


Desktop Speed Medium
67/100

vg.no Desktop Speed Test Quick Summary


priority - 15 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 147.3KiB (83% reduction).

Compressing https://vgc.no/vgnett-prod/css/desktop.css?543e06c1296d58dc3c5039b5c92d1f95 could save 141.6KiB (85% reduction).
Compressing https://api.vg.no/front-service/api/front/vgpluss/articles/list/ could save 3.7KiB (77% reduction).
Compressing https://d57hyau7p492u.cloudfront.net/autoSegment.min.js could save 1.1KiB (50% reduction).
Compressing https://api.vg.no/front-service/api/front/vgpluss/…es/one/df-173-h910bed7 could save 567B (56% reduction).
Compressing https://cis.schibsted.com/api/v1/identify could save 151B (20% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…70a7cee962dd83650f0000 could save 123B (28% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…70a7cee962dd83650f0000 could save 120B (28% reduction).

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

Your page has 1 blocking script resources and 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.

Remove render-blocking JavaScript:

https://vgc.no/vgnett-prod/js/ably.min.js?v=2.0.3

Optimize CSS Delivery of the following:

https://vgc.no/vgnett-prod/css/desktop.css?543e06c1296d58dc3c5039b5c92d1f95

priority - 13 Optimize images

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

Optimize the following images to reduce their size by 124.9KiB (28% reduction).

Compressing https://vcdn.adnxs.com/p/creative-image/3b/93/d9/f…-bd16-6e868012e8ea.jpg could save 28KiB (34% reduction).
Compressing https://imbo.vgc.no/users/livestudio/images/8f7e83…25668b4de1c8314d0c0d88 could save 23.5KiB (55% reduction).
Compressing https://s2.adform.net/Banners/21638192/21638192.jpg?bv=0 could save 23.4KiB (47% reduction).
Compressing https://vgc.no/drfront/gfx/overlay-sprite-desktop.png?20150630-01 could save 8.9KiB (28% reduction).
Compressing https://vgc.no/drfront/gfx/overlay-sprite-desktop.png?20170802-01 could save 8.9KiB (28% reduction).
Compressing https://vgc.no/drfront/images/2018/01/29/c=0,79,36…w=654;h=419;382106.jpg could save 8.4KiB (13% reduction).
Compressing https://vgc.no/drfront/images/2018/01/25/c=2,649,1…w=654;h=363;381439.jpg could save 8.1KiB (20% reduction).
Compressing https://1.vgc.no/pustehullet/betting-header.png could save 4.2KiB (31% reduction).
Compressing https://vgc.no/drfront/images/2018/01/25/c=359,68,…w=318;h=318;381431.jpg could save 3.9KiB (15% reduction).
Compressing https://vgc.no/drfront/images/2018/01/29/w=318;h=216;382043.jpg could save 2.8KiB (14% reduction).
Compressing https://vgc.no/drfront/images/2018/01/29/c=189,24,…w=262;h=201;382110.jpg could save 1.9KiB (12% reduction).
Compressing https://vgc.no/drfront/images/2018/01/29/c=253,145…w=262;h=259;382109.jpg could save 1.6KiB (11% reduction).
Compressing https://vgc.no/vgnett-prod/img/menu/brand-icons-sb36c2922c6.png could save 1.3KiB (26% reduction).

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://api.vg.no/front-service/api/front/vgpluss/articles/list/ (expiration not specified)
https://api.vg.no/front-service/api/front/vgpluss/…es/one/df-173-h910bed7 (expiration not specified)
https://d57hyau7p492u.cloudfront.net/autoSegment.min.js (expiration not specified)
https://ssl-vg.tns-cs.net/blank.gif (expiration not specified)
https://api.vg.no/siteadmin/v1/sites/1/config?page…esktop&callback=config (10 seconds)
https://direkte.vg.no/feed-module/536f61035152f731…twitter,photo&limit=20 (10 seconds)
https://static.finncdn.no/_c/distribution-fixed/FINNExternalDistribution.js (30 seconds)
https://www.vg.no/api/weather/forecast?location=Os…at=59.9127&lon=10.7461 (5 minutes)
https://jssdk.pulse.schibsted.com/autoTrackerVg.with-engage.min.js (15 minutes)
https://jssdk.touchpoints.schibsted.media/v1/touchpoints.sdk.vanilla.js (60 minutes)
https://vgc.no/stats/linkpulse/linkpulse.js?2017-12-20-2 (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://s2.adform.net/Banners/21638192/21638192.jpg?bv=0 (3.7 hours)
https://s372.mxcdn.net/bb-mx/serve/mtrcs_164235.js (10.2 hours)

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.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 53% of the final above-the-fold content could be rendered with the full HTML response.

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 4.1KiB (50% reduction).

Minifying https://cdn.vgc.no/js/libs/intersection-observer/intersection-observer.js could save 3.6KiB (57% reduction) after compression.
Minifying https://cdn.vgc.no/js/libs/spid/spid-uri-2.6.0-var.js could save 472B (25% reduction) after compression.

vg.no Desktop Resources

Total Resources111
Number of Hosts38
Static Resources72
JavaScript Resources47
CSS Resources2

vg.no Desktop Resource Breakdown

vg.no mobile page speed rank

Last tested: 2018-06-09


Mobile Speed Bad
58/100

vg.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 14 blocking CSS resources. This causes a delay in rendering your page.

Approximately 44% 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://vgc.no/vgnett-prod/js/ably.min.js?v=2.0.3

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500,700&subset=latin-ext

priority - 12 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://api.vg.no/front-service/api/front/vgtv/articles/list/ (expiration not specified)
https://api.vg.no/front-service/api/front/vgtv/articles/one/df-178-c5c55fc3 (expiration not specified)
https://d57hyau7p492u.cloudfront.net/autoSegment.min.js (expiration not specified)
https://sdk.pulse.schibsted.com/gdpr-transparency-…/latest/gdpr-bundle.js (expiration not specified)
https://api.vg.no/siteadmin/v1/sites/1/config?page…mobile&callback=config (10 seconds)
https://static.finncdn.no/_c/distribution-fixed/FINNExternalDistribution.js (30 seconds)
https://jssdk.pulse.schibsted.com/autoTrackerVg.with-engage.min.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://1.vgc.no/stats/linkpulse/linkpulse.js (60 minutes)
https://jssdk.touchpoints.schibsted.media/v1/touchpoints.sdk.vanilla.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/js/lidar.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://vgc.no/stats/linkpulse/linkpulse.js?2017-12-20-2 (60 minutes)
https://vgc.no/vgtv-autoplay/autoplay-latest.js (60 minutes)
https://vgc.no/vgtv/web/js/embed-latest.js (60 minutes)
https://www.googletagservices.com/dcm/dcmads.js (60 minutes)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)

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

71.3KiB 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.

Only about 44% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.
Click to see the screenshot with 2 round trips:

priority - 6 Optimize images

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

Optimize the following images to reduce their size by 61.5KiB (19% reduction).

Compressing https://vgc.no/drfront3/images/f15b34b54243d632365146b0ba2add2e.jpg could save 9.6KiB (20% reduction).
Compressing https://vgc.no/drfront/gfx/overlay-sprite-desktop.png?20150630-01 could save 8.9KiB (28% reduction).
Compressing https://vgc.no/drfront/gfx/overlay-sprite-desktop.png?20170802-01 could save 8.9KiB (28% reduction).
Compressing https://vgc.no/drfront/images/2018/06/05/c=1244,23…w=318;h=205;406657.jpg could save 6KiB (25% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=240,0,1…w=318;h=218;407462.jpg could save 4.2KiB (14% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=0,0,190…w=318;h=201;407453.jpg could save 4KiB (16% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=136,38,…w=318;h=224;407455.jpg could save 2.8KiB (12% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=129,32,…w=318;h=203;407464.jpg could save 2.8KiB (16% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=129,32,…w=318;h=180;407464.jpg could save 2.6KiB (16% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=0,0,128…w=318;h=164;407461.jpg could save 2.5KiB (14% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=60,149,…w=318;h=133;407464.jpg could save 1.9KiB (15% reduction).
Compressing https://vgc.no/drfront3/images/dda5adc57a2c4f2ec8a6927d7b941811.jpg could save 1.7KiB (20% reduction).
Compressing https://vgc.no/drfront/images/2018/06/09/c=449,168…w=318;h=187;407448.jpg could save 1.6KiB (14% reduction).
Compressing https://vgc.no/drfront/gfx/icon-innsiden.png could save 1.3KiB (13% reduction).
Compressing https://vgc.no/drfront/images/2018/06/08/w=654;h=55;407342.jpg could save 1.2KiB (19% reduction).
Compressing https://vgc.no/drfront/gfx/tips-icons.png could save 973B (74% reduction).
Compressing https://static.vg.no/app-snarvei/images/app-icon.png could save 431B (40% reduction).

priority - 3 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 26KiB (65% reduction).

Compressing https://sdk.pulse.schibsted.com/gdpr-transparency-…/latest/gdpr-bundle.js could save 23.2KiB (68% reduction).
Compressing https://d57hyau7p492u.cloudfront.net/autoSegment.min.js could save 1.1KiB (50% reduction).
Compressing https://api.vg.no/front-service/api/front/vgtv/articles/one/df-178-c5c55fc3 could save 702B (55% reduction).
Compressing https://api.vg.no/front-service/api/front/vgtv/articles/list/ could save 667B (64% reduction).
Compressing https://cis.schibsted.com/api/v1/identify could save 150B (20% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…f1cfb0e962dd2e0d8d0000 could save 124B (28% reduction).
Compressing https://session.payment.schibsted.no/rpc/hasSessio…f1cfb0e962dd2e0d8d0000 could save 121B (28% reduction).

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

Minifying https://cdn.vgc.no/js/libs/intersection-observer/intersection-observer.js could save 3.6KiB (57% reduction) after compression.

vg.no Mobile Resources

Total Resources162
Number of Hosts56
Static Resources86
JavaScript Resources64
CSS Resources5

vg.no Mobile Resource Breakdown

vg.no mobile page usability

Last tested: 2018-06-09


Mobile Usability Good
99/100

vg.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 <a href="https://e24.no…o-det/24356874"></a> and 12 others are close to other tap targets.
The tap target <a href="https://www.vg…aler-edvartsen">NFF</a> and 1 others are close to other tap targets.
The tap target <a href="https://www.vg…content=row-14">sex av elevene</a> is close to 1 other tap targets.
The tap target <a href="https://www.vg…content=row-14">Se hele serien her</a> is close to 1 other tap targets.
The tap target <a href="http://direkte…52f77e77d423af">presidenten</a> is close to 1 other tap targets.
The tap target <a href="http://direkte…udio/vgsporten">Sportsdøgnet</a> is close to 1 other tap targets.
The tap target <a href="mailto:Gard.Steiro@vg.no">Gard Steiro</a> and 4 others are close to other tap targets.

vg.no Mobile Resources

Total Resources162
Number of Hosts56
Static Resources86
JavaScript Resources64
CSS Resources5

vg.no Mobile Resource Breakdown

vg.no similar domains

Similar domains:
www.vg.com
www.vg.net
www.vg.org
www.vg.info
www.vg.biz
www.vg.us
www.vg.mobi
www.g.no
www.vg.no
www.cg.no
www.vcg.no
www.cvg.no
www.fg.no
www.vfg.no
www.fvg.no
www.gg.no
www.vgg.no
www.gvg.no
www.bg.no
www.vbg.no
www.bvg.no
www.v.no
www.vf.no
www.vgf.no
www.vv.no
www.vgv.no
www.vvg.no
www.vt.no
www.vgt.no
www.vtg.no
www.vb.no
www.vgb.no
www.vy.no
www.vgy.no
www.vyg.no
www.vh.no
www.vgh.no
www.vhg.no

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


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