Nsb.No nsb.no

Pers.Nsb.No

pers.nsb.no receives about 3,733 unique visitors and 7,466 (2.00 per visitor) page views per day which should earn about $39.57/day from advertising revenue. Estimated site value is $28,884.32. According to Alexa Traffic Rank pers.nsb.no is ranked number 274,033 in the world and 0.00022% of global Internet users visit it. Site is hosted in Stabekk, Akershus, 1369, Norway and links to network IP address 138.62.101.15. This server supports HTTPS and doesn't support HTTP/2.

About - pers.nsb.no


Technologies used on Website

Analytics
Google Analytics

pers.nsb.no Profile

Title: pers.nsb.no
Description: Med priser, rutetider og reiseplanlegger for tog i Norge. Mulighet for bestilling av billetter på nettet.
Last update was 1 day ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with nsb.no in any way. Only publicly available statistics data are displayed.

How popular is pers.nsb.no?

3.7K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
3,733
Monthly Unique Visitors:
89,592
Pages per Visit:
2.00
Daily Pageviews:
7,466
Alexa Rank:
274,033 visit alexa
Alexa Reach:
0.00022%   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Norway 100.0%100.0%1339

Where do visitors go on this site?

Reach%Pageviews%PerUser
interaktiv.nsb.no
100.00%100.00%2

Competitive Data

SEMrush
Domain:
  pers.nsb.no
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is pers.nsb.no?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
nsb.no
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:28
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
nsb.no
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Passing

+ How much pers.nsb.no can earn?

Daily Revenue:
$39.57
Monthly Revenue:
$1,187.10
Yearly Revenue:
$14,443.05
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Norway 7,466$39.57

How much money do pers.nsb.no lose due to Adblock?

Daily Revenue Loss:
$7.91
Monthly Revenue Loss:
$237.42
Yearly Revenue Loss:
$2,888.60
Daily Pageviews Blocked:
1,493
Monthly Pageviews Blocked:
44,796
Yearly Pageviews Blocked:
545,018
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Norway 1,493$7.91

How much is pers.nsb.no worth?

Website Value:
$28,884.32

+ Where is pers.nsb.no hosted?

Server IP:
138.62.101.15
ASN:
AS3292 
ISP:
Tele Danmark 
Server Location:
Stabekk
Akershus, 02
1369
Norway, NO
 

Other sites hosted on 138.62.101.15

+ How fast does pers.nsb.no load?

Average Load Time:
(1095 ms) 76 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoid multiple page redirects - Potential savings of 260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://pers.nsb.no/)
0
http://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
190
https://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
70
Keep request counts low and transfer sizes small - 11 requests • 31 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
1131 KB
Script
220 KB
Image
47 KB
Stylesheet
12 KB
Document
11 KB
Other
31 KB
Media
00 KB
Font
00 KB
Third-party
319 KB
Eliminate render-blocking resources - Potential savings of 140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://pers.nsb.no/css/main.css?v=2
2 KB70
https://pers.nsb.no/js/main.js
2 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pers.nsb.no/
0 ms251 ms0 KB0 KB302text/plain
http://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
252 ms494 ms0 KB0 KB302text/plain
https://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
494 ms990 ms1 KB2 KB200text/htmlDocument
https://pers.nsb.no/css/main.css?v=2
1002 ms1125 ms2 KB4 KB200text/cssStylesheet
https://pers.nsb.no/js/main.js
1002 ms1500 ms2 KB3 KB200application/javascriptScript
https://pers.nsb.no/images/vy-logo-final-primary.svg
1003 ms1500 ms5 KB5 KB200image/svg+xmlImage
https://pers.nsb.no/images/button_log_in.png
1003 ms1006 ms0 KB0 KB-1Image
https://www.google-analytics.com/analytics.js
1512 ms1519 ms18 KB43 KB200text/javascriptScript
https://pers.nsb.no/images/button_log_in.png
1537 ms1662 ms2 KB1 KB200image/pngImage
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1309463976&t=pageview&_s=1&dl=https%3A%2F%2Fpers.nsb.no%2Flogin%3Bjsessionid%3D120800EEE016D438BDC67313E33A70C3&ul=en-us&de=UTF-8&dt=pers.nsb.no&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=740327135&gjid=729351826&cid=390120098.1571418442&tid=UA-16020899-3&_gid=219192633.1571418442&_r=1&z=1222859934
1581 ms1586 ms1 KB0 KB302text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-16020899-3&cid=390120098.1571418442&jid=740327135&_gid=219192633.1571418442&gjid=729351826&_v=j79&z=1222859934
1586 ms1588 ms0 KB0 KB-1Image
Uses efficient cache policy on static assets - 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://pers.nsb.no/images/vy-logo-final-primary.svg
0 ms5 KB
https://pers.nsb.no/js/main.js
0 ms2 KB
https://pers.nsb.no/css/main.css?v=2
0 ms2 KB
https://pers.nsb.no/images/button_log_in.png
0 ms2 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1019 ms
8 ms
1528 ms
7 ms
1535 ms
5 ms
1540 ms
20 ms
1572 ms
36 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
60 ms4 ms1 ms
Avoids enormous network payloads - Total size was 31 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google-analytics.com/analytics.js
18 KB
https://pers.nsb.no/images/vy-logo-final-primary.svg
5 KB
https://pers.nsb.no/js/main.js
2 KB
https://pers.nsb.no/css/main.css?v=2
2 KB
https://pers.nsb.no/images/button_log_in.png
2 KB
https://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
1 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1309463976&t=pageview&_s=1&dl=https%3A%2F%2Fpers.nsb.no%2Flogin%3Bjsessionid%3D120800EEE016D438BDC67313E33A70C3&ul=en-us&de=UTF-8&dt=pers.nsb.no&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=740327135&gjid=729351826&cid=390120098.1571418442&tid=UA-16020899-3&_gid=219192633.1571418442&_r=1&z=1222859934
1 KB
http://pers.nsb.no/
0 KB
http://pers.nsb.no/login;jsessionid=120800EEE016D438BDC67313E33A70C3
0 KB
https://pers.nsb.no/images/button_log_in.png
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
42 ms
Other
27 ms
Style & Layout
20 ms
Rendering
5 ms
Parse HTML & CSS
4 ms
Script Parsing & Compilation
3 ms
Avoids an excessive DOM size - 34 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
34
Maximum DOM Depth
8
Maximum Child Elements
8
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 500 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

97
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Total Blocking Time 150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 3150 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
358 ms15 ms5 ms
https://www.google-analytics.com/analytics.js
198 ms192 ms6 ms
Avoids enormous network payloads - Total size was 32 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google-analytics.com/analytics.js
18 KB
https://pers.nsb.no/images/vy-logo-final-primary.svg
5 KB
https://pers.nsb.no/js/main.js
2 KB
https://pers.nsb.no/css/main.css?v=2
2 KB
https://pers.nsb.no/images/button_log_in.png
2 KB
https://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
1 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=625106716&t=pageview&_s=1&dl=https%3A%2F%2Fpers.nsb.no%2Flogin%3Bjsessionid%3D633078DA3CB8EFEDC218461118C412CE&ul=en-us&de=UTF-8&dt=pers.nsb.no&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAEAB~&jid=721464963&gjid=1196321682&cid=1850317318.1571418436&tid=UA-16020899-3&_gid=1162439559.1571418436&_r=1&z=2127607840
1 KB
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-16020899-3&cid=1850317318.1571418436&jid=721464963&_gid=1162439559.1571418436&gjid=1196321682&_v=j79&z=2127607840
1 KB
http://pers.nsb.no/
0 KB
http://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
0 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
230 ms
Other
179 ms
Style & Layout
118 ms
Parse HTML & CSS
27 ms
Rendering
17 ms
Script Parsing & Compilation
14 ms
Avoids an excessive DOM size - 34 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
34
Maximum DOM Depth
8
Maximum Child Elements
8
Avoid multiple page redirects - Potential savings of 810 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://pers.nsb.no/)
0
http://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
630
https://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
180
Keep request counts low and transfer sizes small - 10 requests • 32 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
1032 KB
Script
220 KB
Image
37 KB
Stylesheet
12 KB
Document
11 KB
Other
31 KB
Media
00 KB
Font
00 KB
Third-party
319 KB
Eliminate render-blocking resources - Potential savings of 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://pers.nsb.no/css/main.css?v=2
2 KB180
https://pers.nsb.no/js/main.js
2 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pers.nsb.no/
0 ms272 ms0 KB0 KB302text/plain
http://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
273 ms549 ms0 KB0 KB302text/plain
https://pers.nsb.no/login;jsessionid=633078DA3CB8EFEDC218461118C412CE
549 ms1044 ms1 KB2 KB200text/htmlDocument
https://pers.nsb.no/css/main.css?v=2
1061 ms1186 ms2 KB4 KB200text/cssStylesheet
https://pers.nsb.no/js/main.js
1061 ms1555 ms2 KB3 KB200application/javascriptScript
https://pers.nsb.no/images/vy-logo-final-primary.svg
1062 ms1556 ms5 KB5 KB200image/svg+xmlImage
https://pers.nsb.no/images/button_log_in.png
1062 ms1556 ms2 KB1 KB200image/pngImage
https://www.google-analytics.com/analytics.js
1581 ms1587 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=625106716&t=pageview&_s=1&dl=https%3A%2F%2Fpers.nsb.no%2Flogin%3Bjsessionid%3D633078DA3CB8EFEDC218461118C412CE&ul=en-us&de=UTF-8&dt=pers.nsb.no&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAEAB~&jid=721464963&gjid=1196321682&cid=1850317318.1571418436&tid=UA-16020899-3&_gid=1162439559.1571418436&_r=1&z=2127607840
1677 ms1684 ms1 KB0 KB302text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-16020899-3&cid=1850317318.1571418436&jid=721464963&_gid=1162439559.1571418436&gjid=1196321682&_v=j79&z=2127607840
1684 ms1692 ms1 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://pers.nsb.no/images/vy-logo-final-primary.svg
0 ms5 KB
https://pers.nsb.no/js/main.js
0 ms2 KB
https://pers.nsb.no/css/main.css?v=2
0 ms2 KB
https://pers.nsb.no/images/button_log_in.png
0 ms2 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party usage - Third-party code blocked the main thread for 140 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB138 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1093 ms
10 ms
1602 ms
19 ms
1621 ms
8 ms
1631 ms
30 ms
1673 ms
50 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 500 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid 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://pers.nsb.no/
http://pers.nsb.no/login;jsessionid=2F6E497FE4651230761AACEA8119D09C
https://pers.nsb.no/login;jsessionid=2F6E497FE4651230761AACEA8119D09C

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://pers.nsb.no/js/main.js
Optimize CSS Delivery of the following:

https://pers.nsb.no/css/main.css?v=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 13% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

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://pers.nsb.no/images/button_log_in.png (expiration not specified)
https://pers.nsb.no/images/vy-logo-final-primary.svg (expiration not specified)
https://pers.nsb.no/js/main.js (expiration not specified)
https://www.google-***ytics.com/***ytics.js (2 hours)

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 2.8KiB (56% reduction).

Compressing https://pers.nsb.no/images/vy-logo-final-primary.svg could save 2.8KiB (56% reduction).

Optimize images

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

Optimize the following images to reduce their size by 278B (23% reduction).

Compressing https://pers.nsb.no/images/button_log_in.png could save 278B (23% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 222B (17% reduction).

Minifying https://pers.nsb.no/css/main.css?v=2 could save 222B (17% reduction) after compression.

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 p*** times.

Minify HTML for the following resources to reduce their size by 123B (11% reduction).

Minifying https://pers.nsb.no/login;jsessionid=2F6E497FE4651230761AACEA8119D09C could save 123B (11% reduction) after compression.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does pers.nsb.no use compression?

pers.nsb.no use gzip compression.
Original size: 2.75 KB
Compressed size: 1.24 KB
File reduced by: 1.51 KB (55%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

pers.nsb.no supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.nsb.no
Organization: Norges Statsbaner AS
Location: Oslo, NO
Issuer: Thawte RSA CA 2018
Valid from: Mar 22 00:00:00 2018 GMT
Valid until: Mar 21 12:00:00 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: Thawte RSA CA 2018
Organization: DigiCert Inc, OU=www.digicert.com
Location: US
Issuer: DigiCert Global Root CA
Valid from: Nov 6 12:23:52 2017 GMT
Valid until: Nov 6 12:23:52 2027 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

pers.nsb.no does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Reiser/Tog

+ Http Header

Date: Sat, 16 Nov 2019 16:27:02 GMT
Strict-Transport-Security: max-age=0
Location: /login;jsessionid=82C0E36A83F8E606C9CA0572E6A8E853
Content-Language: no-NO
Content-Length: 0
Set-Cookie: JSESSIONID=82C0E36A83F8E606C9CA0572E6A8E853; Path=/; HttpOnly
X-UA-Compatible: IE=edge
Content-Type: text/plain; charset=UTF-8

HTTP/1.1 302 
Date: Sat, 16 Nov 2019 16:27:02 GMT
Strict-Transport-Security: max-age=0
Location: https://pers.nsb.no/login;jsessionid=82C0E36A83F8E606C9CA0572E6A8E853
Content-Language: no-NO
Content-Length: 0
X-UA-Compatible: IE=edge
Content-Type: text/plain; charset=UTF-8

HTTP/1.1 200 200
Date: Sat, 16 Nov 2019 16:27:02 GMT
Strict-Transport-Security: max-age=0
Content-Type: text/html;charset=UTF-8
Content-Language: no-NO
X-UA-Compatible: IE=edge
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 1265

+ DNS Lookup

Type Ip Target TTL
A 138.62.101.15 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 1 day ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with nsb.no in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

flibaba.com
12 secs
sanfranciscodeasis.com.ar
18 secs
flirt4u.ch
58 secs
repelispro.com
1 min
mercadocentral.gob.ar
2 mins
pgmultimedias.com
2 mins
***ute.com
3 mins
okhatrimaza.com
3 mins
minijuegos.com.co
3 mins
fixsattamatkai.in
4 mins

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
pers.nsb.no widget