Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lily.fi

Lily.fi | Lily

Page Load Speed

12.7 sec in total

First Response

534 ms

Resources Loaded

10.6 sec

Page Rendered

1.6 sec

lily.fi screenshot

About Website

Visit lily.fi now to see the best up-to-date Lily content for Finland and also check out these interesting facts you probably never knew about lily.fi

Lue Suomen parhaita blogeja ja toimituksen juttuja, keskustele tai perusta oma blogi osaksi Lily-yhteisöä.

Visit lily.fi

Key Findings

We analyzed Lily.fi page load time and found that the first response time was 534 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

lily.fi performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.921

3/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

www.lily.fi

534 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

237 ms

css_6Vw_e6ZWRs-ROLbc84ZhUpdg2KTIhTlSioYD-M7NI7I.css

249 ms

css_hBDzOrwL_oGrlEouh2l-32k7nITzYDV1O89Vr5T7UVY.css

251 ms

css__2ZQ-i7xW0LX6iC14PP0UOM-WYjOHaiSwTJO5DRDsRU.css

496 ms

Our browser made a total of 424 requests to load all elements on the main page. We found that 22% of them (92 requests) were addressed to the original Lily.fi, 8% (35 requests) were made to Pixel.rubiconproject.com and 8% (32 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Lily.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (20%)

Content Size

9.9 MB

After Optimization

7.9 MB

In fact, the total size of Lily.fi main page is 9.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 309.0 kB

  • Original 380.3 kB
  • After minification 371.0 kB
  • After compression 71.3 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 309.0 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 403.1 kB

  • Original 7.6 MB
  • After minification 7.2 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. Lily images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 1.0 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 573.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 1.0 MB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 223.6 kB

  • Original 270.2 kB
  • After minification 267.1 kB
  • After compression 46.6 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. Lily.fi needs all CSS files to be minified and compressed as it can save up to 223.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 196 (52%)

Requests Now

376

After Optimization

180

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

Accessibility Review

lily.fi accessibility score

75

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lily.fi best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lily.fi SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

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

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