Tools & Wizards About Us
lifevision.no screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lifevision.no

NG DIALOGUE

Page Load Speed

4.1 sec in total

First Response

413 ms

Resources Loaded

3.2 sec

Page Rendered

425 ms

lifevision.no screenshot

About Website

Click here to check amazing Lifevision content for Norway. Otherwise, check out these important facts you probably never knew about lifevision.no

NG Dialogue

Visit lifevision.no

Key Findings

We analyzed Lifevision.no page load time and found that the first response time was 413 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

lifevision.no performance score

0

Network Requests Diagram

lifevision.no

413 ms

main.css

383 ms

skeleton.css

499 ms

flexslider.css

242 ms

ui.all.css

239 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 48% of them (47 requests) were addressed to the original Lifevision.no, 33% (32 requests) were made to Static.xx.fbcdn.net and 10% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (967 ms) belongs to the original domain Lifevision.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.0 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifevision.no main page is 1.3 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 24.0 kB

  • Original 31.2 kB
  • After minification 24.6 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 6.6 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.0 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 28.5 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Lifevision images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 35.6 kB

  • Original 70.0 kB
  • After minification 69.7 kB
  • After compression 34.3 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 35.6 kB or 51% of the original size.

CSS Optimization

-85%

Potential reduce by 101.9 kB

  • Original 119.3 kB
  • After minification 89.4 kB
  • After compression 17.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. Lifevision.no needs all CSS files to be minified and compressed as it can save up to 101.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (49%)

Requests Now

96

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifevision. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lifevision.no

lifevision.no

413 ms

main.css

main.css

383 ms

skeleton.css

skeleton.css

499 ms

flexslider.css

flexslider.css

242 ms

ui.all.css

ui.all.css

239 ms

datepicker_custom.css

datepicker_custom.css

247 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

7 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

254 ms

jquery.infieldlabel.min.js

jquery.infieldlabel.min.js

247 ms

knockout-2.0.0.js

knockout-2.0.0.js

501 ms

ui.base.css

ui.base.css

127 ms

ui.theme.css

ui.theme.css

244 ms

ui.core.css

ui.core.css

120 ms

ui.datepicker.css

ui.datepicker.css

122 ms

ga.js

ga.js

28 ms

all.js

all.js

166 ms

slide-landing-page2.png

slide-landing-page2.png

888 ms

slide-blog.png

slide-blog.png

730 ms

start-form-bg.png

start-form-bg.png

250 ms

logo-android.png

logo-android.png

135 ms

logo-iphone.png

logo-iphone.png

134 ms

logo-symbian.png

logo-symbian.png

235 ms

logo-windows.png

logo-windows.png

251 ms

logo-blackberry.png

logo-blackberry.png

257 ms

main-hgl.png

main-hgl.png

462 ms

header-bg.png

header-bg.png

356 ms

logo.png

logo.png

357 ms

ajax-loader.gif

ajax-loader.gif

362 ms

no.png

no.png

476 ms

selectbox-marker.png

selectbox-marker.png

480 ms

white-90.png

white-90.png

482 ms

main-bg.gif

main-bg.gif

579 ms

line-pattern.png

line-pattern.png

599 ms

main_slider_hgl.png

main_slider_hgl.png

837 ms

color-lines-bg.jpg

color-lines-bg.jpg

723 ms

services-icons.png

services-icons.png

702 ms

quotes.png

quotes.png

722 ms

list-dot.png

list-dot.png

821 ms

send-btn.png

send-btn.png

834 ms

close-btn.png

close-btn.png

844 ms

icon-user.png

icon-user.png

844 ms

icon-password.png

icon-password.png

944 ms

top-hgl3.png

top-hgl3.png

967 ms

footer-bg.gif

footer-bg.gif

955 ms

footer-topline.gif

footer-topline.gif

962 ms

footer-hgl.png

footer-hgl.png

961 ms

__utm.gif

__utm.gif

12 ms

72 ms

xd_arbiter.php

xd_arbiter.php

144 ms

xd_arbiter.php

xd_arbiter.php

268 ms

ping

ping

48 ms

main_slider_dots_bg.png

main_slider_dots_bg.png

121 ms

main_slider_dots.png

main_slider_dots.png

121 ms

main_slider_nav.png

main_slider_nav.png

128 ms

Oswald-Regular-webfont.woff

Oswald-Regular-webfont.woff

245 ms

like_box.php

like_box.php

159 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

178 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

221 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

263 ms

Ek6lpayKeeB.css

Ek6lpayKeeB.css

360 ms

EoarYgA68t4.css

EoarYgA68t4.css

376 ms

5VZ003vMUZg.css

5VZ003vMUZg.css

344 ms

dAhyk4_vXRy.css

dAhyk4_vXRy.css

301 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

393 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

416 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

339 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

431 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

435 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

436 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

449 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

502 ms

1FCa-btixu2.js

1FCa-btixu2.js

438 ms

IjqSyiwKeaX.js

IjqSyiwKeaX.js

439 ms

rBxSIHk4zIe.js

rBxSIHk4zIe.js

461 ms

n6VgtouijQL.js

n6VgtouijQL.js

440 ms

7BE0CZr3HTs.js

7BE0CZr3HTs.js

461 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

500 ms

_UYztdBNTjs.js

_UYztdBNTjs.js

462 ms

-7JBD_ybv4q.js

-7JBD_ybv4q.js

571 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

570 ms

295127_320209591404440_1464202575_n.jpg

295127_320209591404440_1464202575_n.jpg

291 ms

1912118_589819361110127_198890188_n.jpg

1912118_589819361110127_198890188_n.jpg

195 ms

1452058_971401556285237_8139382787514160842_n.jpg

1452058_971401556285237_8139382787514160842_n.jpg

229 ms

10351831_970659276359465_3479281562740800848_n.jpg

10351831_970659276359465_3479281562740800848_n.jpg

228 ms

12720257_963076537117739_1477804831_n.jpg

12720257_963076537117739_1477804831_n.jpg

172 ms

12814421_962985620460164_82456212101108171_n.jpg

12814421_962985620460164_82456212101108171_n.jpg

504 ms

12813895_962985623793497_3429661239523329770_n.jpg

12813895_962985623793497_3429661239523329770_n.jpg

178 ms

12321417_962985650460161_1684623547818232794_n.jpg

12321417_962985650460161_1684623547818232794_n.jpg

179 ms

12670385_962985653793494_3651072650131488363_n.jpg

12670385_962985653793494_3651072650131488363_n.jpg

181 ms

1450124_952405974851462_5091057152892431859_n.jpg

1450124_952405974851462_5091057152892431859_n.jpg

243 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

149 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

150 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

149 ms

l5aPruN9xMM.png

l5aPruN9xMM.png

150 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

147 ms

b8XhdWI9eAN.js

b8XhdWI9eAN.js

75 ms

K_65vAc89SX.png

K_65vAc89SX.png

53 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

46 ms

SEO Factors

lifevision.no SEO score

0

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifevision.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed English language. Our system also found out that Lifevision.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.

Social Sharing Optimization

lifevision.no

Open Graph description is not detected on the main page of Lifevision. 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: