Tools & Wizards About Us
lio.se screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lio.se

Region Östergötland - Region Östergötland

Page Load Speed

5.9 sec in total

First Response

446 ms

Resources Loaded

5.3 sec

Page Rendered

203 ms

lio.se screenshot

About Website

Click here to check amazing Lio content for Sweden. Otherwise, check out these important facts you probably never knew about lio.se

Region Östergötlands viktigaste uppdrag är att erbjuda invånarna i Östergötland en bra hälso- och sjukvård, där även tandvård ingår. Inom den högspecialiserade vården har Region Östergötland också ett...

Visit lio.se

Key Findings

We analyzed Lio.se page load time and found that the first response time was 446 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

lio.se performance score

0

Network Requests Diagram

lio.se

446 ms

www.regionostergotland.se

2379 ms

bootstrap.css

418 ms

bootstrap-responsive.css

317 ms

style.css

426 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lio.se, 80% (49 requests) were made to Regionostergotland.se and 18% (11 requests) were made to F1.eu.readspeaker.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Regionostergotland.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (69%)

Content Size

1.7 MB

After Optimization

513.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lio.se main page is 1.7 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 592.9 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 451.6 kB

  • Original 504.5 kB
  • After minification 353.1 kB
  • After compression 52.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. This page needs HTML code to be minified as it can gain 151.3 kB, which is 30% 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 451.6 kB or 90% of the original size.

Image Optimization

-5%

Potential reduce by 17.0 kB

  • Original 326.3 kB
  • After minification 309.3 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. Lio images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 476.4 kB

  • Original 592.9 kB
  • After minification 415.5 kB
  • After compression 116.5 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 476.4 kB or 80% of the original size.

CSS Optimization

-86%

Potential reduce by 207.5 kB

  • Original 242.5 kB
  • After minification 194.8 kB
  • After compression 35.0 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. Lio.se needs all CSS files to be minified and compressed as it can save up to 207.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (46%)

Requests Now

59

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lio.se

lio.se

446 ms

www.regionostergotland.se

www.regionostergotland.se

2379 ms

bootstrap.css

bootstrap.css

418 ms

bootstrap-responsive.css

bootstrap-responsive.css

317 ms

style.css

style.css

426 ms

responsive.css

responsive.css

219 ms

menucolors.css

menucolors.css

220 ms

jquery-1.9.1.js

jquery-1.9.1.js

762 ms

jquery-respond.js

jquery-respond.js

436 ms

jquery-easy.menu.js

jquery-easy.menu.js

423 ms

jquery-sidebar.js

jquery-sidebar.js

518 ms

jquery-slider.js

jquery-slider.js

526 ms

jquery-cookie.js

jquery-cookie.js

531 ms

bootstrap.js

bootstrap.js

652 ms

script.js

script.js

593 ms

ReadSpeaker.js

ReadSpeaker.js

222 ms

siteseeker

siteseeker

649 ms

js

js

2004 ms

js

js

1177 ms

WebResource.axd

WebResource.axd

204 ms

ReadSpeaker.Styles.css

ReadSpeaker.Styles.css

75 ms

ReadSpeaker.Core.js

ReadSpeaker.Core.js

99 ms

ReadSpeaker.pub.Config.js

ReadSpeaker.pub.Config.js

104 ms

ReadSpeaker.lib.Facade.adapter.jquery.js

ReadSpeaker.lib.Facade.adapter.jquery.js

75 ms

ReadSpeaker.Common.Settings.js

ReadSpeaker.Common.Settings.js

36 ms

ReadSpeaker.PlayerAPI.js

ReadSpeaker.PlayerAPI.js

74 ms

ReadSpeaker.HL.js

ReadSpeaker.HL.js

76 ms

ReadSpeaker.ui.js

ReadSpeaker.ui.js

103 ms

logo_region.png

logo_region.png

103 ms

white-right.png

white-right.png

109 ms

arrows.png

arrows.png

107 ms

search.png

search.png

105 ms

rokfritt.jpg

rokfritt.jpg

113 ms

etjanster.jpg

etjanster.jpg

224 ms

sociala_medier.jpg

sociala_medier.jpg

204 ms

kulturstipendier.jpg

kulturstipendier.jpg

315 ms

regiondirektorensblogg.jpg

regiondirektorensblogg.jpg

215 ms

sok_utlysta_forskningsmedel.jpg

sok_utlysta_forskningsmedel.jpg

325 ms

icon_rss.png

icon_rss.png

223 ms

arrow-right-blue.png

arrow-right-blue.png

307 ms

sveriges_basta_sjukhus.jpg

sveriges_basta_sjukhus.jpg

322 ms

vgw2.jpg

vgw2.jpg

333 ms

logo-bg-large.png

logo-bg-large.png

332 ms

arrow-right-white.png

arrow-right-white.png

409 ms

mobilebutton.png

mobilebutton.png

418 ms

phone.png

phone.png

428 ms

email.png

email.png

431 ms

snailmail.png

snailmail.png

440 ms

facebook.gif

facebook.gif

444 ms

twitter.gif

twitter.gif

510 ms

youtube3.gif

youtube3.gif

523 ms

linkedin3.gif

linkedin3.gif

536 ms

RSS.gif

RSS.gif

539 ms

i.png

i.png

549 ms

ReadSpeaker.enlargeHL.js

ReadSpeaker.enlargeHL.js

84 ms

ReadSpeaker.enlargeHL.css

ReadSpeaker.enlargeHL.css

75 ms

pageload

pageload

529 ms

glyphicons-halflings.png

glyphicons-halflings.png

536 ms

print.css

print.css

102 ms

arrow-right-black.png

arrow-right-black.png

102 ms

pause.png

pause.png

109 ms

SEO Factors

lio.se SEO score

0

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

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

lio.se

Open Graph data is detected on the main page of Lio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: