9.1 sec in total
1.5 sec
7.3 sec
244 ms
Click here to check amazing Lifi content. Otherwise, check out these important facts you probably never knew about lifi.no
Viken Fiber bygger og drifter fibernett og leverer Altibox bredbåndstjenester til husholdninger og bedriftskunder over store deler av Østlandet.
Visit lifi.noWe analyzed Lifi.no page load time and found that the first response time was 1.5 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lifi.no performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value11.7 s
0/100
25%
Value11.1 s
6/100
10%
Value570 ms
52/100
30%
Value0.452
20/100
15%
Value11.6 s
18/100
10%
1543 ms
1076 ms
456 ms
346 ms
1192 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 51% of them (36 requests) were addressed to the original Lifi.no, 13% (9 requests) were made to Google.com and 9% (6 requests) were made to Altibox.no. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Lifi.no.
Page size can be reduced by 851.5 kB (40%)
2.1 MB
1.3 MB
In fact, the total size of Lifi.no main page is 2.1 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. 55% of websites need less resources to load. Images take 975.3 kB which makes up the majority of the site volume.
Potential reduce by 54.2 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 54.2 kB or 75% of the original size.
Potential reduce by 44.9 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. Lifi images are well optimized though.
Potential reduce by 473.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 473.7 kB or 64% of the original size.
Potential reduce by 278.7 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. Lifi.no needs all CSS files to be minified and compressed as it can save up to 278.7 kB or 82% of the original size.
Number of requests can be reduced by 34 (53%)
64
30
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.lifi.no
1543 ms
jquery-1.9.1.min.js
1076 ms
css.jsp
456 ms
main.jsp
346 ms
barebone.jsp
1192 ms
main.css
963 ms
includes.css
960 ms
altibox.min.js
1167 ms
profile-bs3.min.js
1063 ms
jquery.xml2json.js
1098 ms
table2csv.js
1098 ms
date.format.js
1224 ms
altibox-jscript.js
1224 ms
jquery.swfobject.js
2966 ms
main.css
2966 ms
handlebars.runtime-v1.3.0.js
2991 ms
main.js
2875 ms
css
63 ms
profile.min.css
1895 ms
lightbox.css
1764 ms
image_gallery
1232 ms
logo0515.png
751 ms
footerlogotranswhite.png
745 ms
fbk.png
758 ms
twitter.png
744 ms
utube.png
753 ms
instagram.png
746 ms
image_gallery
1989 ms
image_gallery
1891 ms
image_gallery
2231 ms
image_gallery
1668 ms
image_gallery
1583 ms
gtm.js
91 ms
cse.js
59 ms
_aijTyevf54tkVDLy-dlnD8E0i7KZn-EPnyo3HZu7kw.woff
29 ms
_xyN3apAT_yRRDeqB3sPRg.woff
42 ms
0ihfXUL2emPh0ROJezvraD8E0i7KZn-EPnyo3HZu7kw.woff
48 ms
altibox.woff
1427 ms
altiboxFont.css
1080 ms
css
24 ms
cse.js
67 ms
analytics.js
28 ms
collect
12 ms
jsapi
18 ms
default+no.css
9 ms
default.css
21 ms
default+no.I.js
21 ms
default.css
30 ms
image_gallery
357 ms
image_gallery
339 ms
image_gallery
358 ms
242 ms
dc.js
79 ms
fbds.js
43 ms
413 ms
layout_set_logo
516 ms
person.png
534 ms
finger.png
512 ms
18 ms
__utm.gif
12 ms
__utm.gif
25 ms
285 ms
103 ms
120 ms
async-ads.js
46 ms
google_custom_search_watermark.gif
35 ms
28 ms
small-logo.png
34 ms
search_box_icon.png
27 ms
nav_logo114.png
25 ms
lifi.no accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
lifi.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
General
Impact
Issue
Detected JavaScript libraries
lifi.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifi.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lifi.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.
lifi.no
Open Graph description is not detected on the main page of Lifi. 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: