2.6 sec in total
294 ms
2.2 sec
171 ms
Visit fjellinjen.no now to see the best up-to-date Fjellinjen content for Norway and also check out these interesting facts you probably never knew about fjellinjen.no
Fra finansiering av Festningstunnelen til Fornebubanen. Fjellinjen har tatt inn og forvaltet mer enn 50 milliarder kroner. Pengene finansierer fremtidens trafikkløsninger i Stor-Oslo.
Visit fjellinjen.noWe analyzed Fjellinjen.no page load time and found that the first response time was 294 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fjellinjen.no performance score
name
value
score
weighting
Value2.7 s
62/100
10%
Value6.4 s
10/100
25%
Value7.2 s
30/100
10%
Value780 ms
38/100
30%
Value0
100/100
15%
Value11.4 s
19/100
10%
294 ms
525 ms
198 ms
509 ms
31 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 91% of them (39 requests) were addressed to the original Fjellinjen.no, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (743 ms) belongs to the original domain Fjellinjen.no.
Page size can be reduced by 938.1 kB (64%)
1.5 MB
523.0 kB
In fact, the total size of Fjellinjen.no main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 997.8 kB which makes up the majority of the site volume.
Potential reduce by 9.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.8 kB or 67% of the original size.
Potential reduce by 31.1 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Fjellinjen images are well optimized though.
Potential reduce by 844.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 844.7 kB or 85% of the original size.
Potential reduce by 52.4 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fjellinjen.no needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 82% of the original size.
Number of requests can be reduced by 20 (49%)
41
21
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fjellinjen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fjellinjen.no
294 ms
www.fjellinjen.no
525 ms
reset.css
198 ms
styles.css
509 ms
jquery.min.js
31 ms
jquery-migrate-1.0.0.js
416 ms
jquery.fancybox-1.3.4.pack.js
423 ms
jquery.mousewheel-3.0.4.pack.js
222 ms
jquery.fancybox-1.3.4.css
292 ms
site.js
331 ms
jquery.meio.mask.min.js
484 ms
jquery.watermark.js
589 ms
SavingsCalculator.css
445 ms
jquery-ui-1.9.0.custom.min.css
531 ms
jquery-ui-1.9.0.custom.min.js
743 ms
WebResource.axd
453 ms
ScriptResource.axd
706 ms
ScriptResource.axd
603 ms
ScriptResource.axd
524 ms
ScriptResource.axd
563 ms
savingscalculator.js
483 ms
WebResource.axd
519 ms
ga.js
29 ms
logo.png
116 ms
dkd_bestill_bedrift.jpg
102 ms
dkd_bestill_privat.jpg
103 ms
dkd_chatboxRED.png
106 ms
dkd_snakk01.jpg
98 ms
dkd_snakk02.jpg
131 ms
dkd_snakk03.jpg
207 ms
app-forsidemed%20tekst.jpg
407 ms
f_logo_small2.jpg
206 ms
twitter-bird_small2.png
207 ms
Instagram_Icon_Small_34_2.png
218 ms
yt-brand-yt-stackedlogo_small2.png
237 ms
LinkedIn_Logo30px2.png
306 ms
__utm.gif
62 ms
header_background.png
248 ms
headercontent_background.png
360 ms
arrow.png
275 ms
footer_background2.png
290 ms
footercontent_background.png
344 ms
ps.js
700 ms
fjellinjen.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
fjellinjen.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fjellinjen.no SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fjellinjen.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Fjellinjen.no main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
fjellinjen.no
Open Graph description is not detected on the main page of Fjellinjen. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: