Tools & Wizards About Us
lillyfinance.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lillyfinance.com

Lillian | The Next Generation Medical Finance Blockchain

Page Load Speed

2 sec in total

First Response

15 ms

Resources Loaded

1.9 sec

Page Rendered

69 ms

lillyfinance.com screenshot

About Website

Welcome to lillyfinance.com homepage info - get ready to check Lilly Finance best content for Saudi Arabia right away, or after learning these important things about lillyfinance.com

Visit lillyfinance.com

Key Findings

We analyzed Lillyfinance.com page load time and found that the first response time was 15 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

lillyfinance.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

lillyfinance.com

15 ms

www.lillianfinance.com

102 ms

originTrials.41d7301a.bundle.min.js

42 ms

minified.js

43 ms

focus-within-polyfill.js

43 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lillyfinance.com, 50% (34 requests) were made to Static.wixstatic.com and 25% (17 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 791.0 kB (62%)

Content Size

1.3 MB

After Optimization

489.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lillyfinance.com 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. 40% of websites need less resources to load. HTML takes 855.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 701.1 kB

  • Original 855.6 kB
  • After minification 854.0 kB
  • After compression 154.6 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 701.1 kB or 82% of the original size.

Image Optimization

-21%

Potential reduce by 30.5 kB

  • Original 147.7 kB
  • After minification 117.2 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. Obviously, Lilly Finance needs image optimization as it can save up to 30.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-21%

Potential reduce by 59.4 kB

  • Original 277.3 kB
  • After minification 277.3 kB
  • After compression 217.9 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 59.4 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (23%)

Requests Now

47

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lillyfinance.com

lillyfinance.com

15 ms

www.lillianfinance.com

www.lillianfinance.com

102 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

42 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

43 ms

polyfill.min.js

polyfill.min.js

311 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

thunderbolt-commons.1e70fbb2.bundle.min.js

81 ms

main.42e492e1.bundle.min.js

main.42e492e1.bundle.min.js

80 ms

lodash.min.js

lodash.min.js

81 ms

react.production.min.js

react.production.min.js

80 ms

react-dom.production.min.js

react-dom.production.min.js

80 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

81 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

83 ms

Lillan%20Color%20Icon%20Logo.png

Lillan%20Color%20Icon%20Logo.png

294 ms

eb11d5_e931a23069654a3693630e10bbaaeaa2~mv2.png

eb11d5_e931a23069654a3693630e10bbaaeaa2~mv2.png

498 ms

White%20Full%20Logo.png

White%20Full%20Logo.png

461 ms

eb11d5_3a14b26e461e4b62a5f1c485fbbf6ed1~mv2.png

eb11d5_3a14b26e461e4b62a5f1c485fbbf6ed1~mv2.png

536 ms

eb11d5_be858874e1e2401fbc0f8d9cc7a84bf8~mv2.png

eb11d5_be858874e1e2401fbc0f8d9cc7a84bf8~mv2.png

556 ms

eb11d5_9a0918d35176434881a65669201a1b3d~mv2.png

eb11d5_9a0918d35176434881a65669201a1b3d~mv2.png

507 ms

eb11d5_750b57ed033345a7845a0ed492316604~mv2.jpg

eb11d5_750b57ed033345a7845a0ed492316604~mv2.jpg

453 ms

eb11d5_0ad0792c9c2d4fcba41fb06cc55defb8~mv2.jpg

eb11d5_0ad0792c9c2d4fcba41fb06cc55defb8~mv2.jpg

598 ms

Add%20a%20little%20bit%20of%20body%20text%20(2).png

Add%20a%20little%20bit%20of%20body%20text%20(2).png

667 ms

eb11d5_ae11cc1efd054bbb98209f14b6d00c44~mv2.jpg

eb11d5_ae11cc1efd054bbb98209f14b6d00c44~mv2.jpg

770 ms

eb11d5_beafd68339cd4d30b09812910ccc4171~mv2.jpg

eb11d5_beafd68339cd4d30b09812910ccc4171~mv2.jpg

695 ms

eb11d5_426d2654b1834805b80cfe8e0ac7ae9c~mv2.jpg

eb11d5_426d2654b1834805b80cfe8e0ac7ae9c~mv2.jpg

679 ms

MedMeta_White.png

MedMeta_White.png

735 ms

screens_web3.png

screens_web3.png

850 ms

eb11d5_bf7ec37783f1472f9433e55b7c8e224ef000.jpg

eb11d5_bf7ec37783f1472f9433e55b7c8e224ef000.jpg

819 ms

ly_blockchain.png

ly_blockchain.png

816 ms

eb11d5_9de0ebb6995340729642b7821fad7863f000.jpg

eb11d5_9de0ebb6995340729642b7821fad7863f000.jpg

848 ms

LBF%20White.png

LBF%20White.png

910 ms

eb11d5_d25ce4a0e2de47b3b5a51bd164f77b73~mv2.png

eb11d5_d25ce4a0e2de47b3b5a51bd164f77b73~mv2.png

934 ms

eb11d5_b3eed9b60ffc435b833cef2f13820edb~mv2.png

eb11d5_b3eed9b60ffc435b833cef2f13820edb~mv2.png

955 ms

eb11d5_d2cb36890427492d806b169615da1841~mv2.jpg

eb11d5_d2cb36890427492d806b169615da1841~mv2.jpg

975 ms

eb11d5_0a0f1c76052446238af23005e9ebffa2~mv2.jpg

eb11d5_0a0f1c76052446238af23005e9ebffa2~mv2.jpg

995 ms

eb11d5_8127492d3f384d149947f34c99ff522b~mv2.jpg

eb11d5_8127492d3f384d149947f34c99ff522b~mv2.jpg

980 ms

eb11d5_dd55db0c3bb1425fa59ff681a131292c~mv2.png

eb11d5_dd55db0c3bb1425fa59ff681a131292c~mv2.png

1067 ms

eb11d5_008720f37aa548c793b21282900bbfa4~mv2.jpg

eb11d5_008720f37aa548c793b21282900bbfa4~mv2.jpg

1062 ms

eb11d5_1b501239579b4b3e9e6c466dfc70661d~mv2.png

eb11d5_1b501239579b4b3e9e6c466dfc70661d~mv2.png

1131 ms

eb11d5_8b91813c9205416ebcbb110af86ac5bc~mv2.jpg

eb11d5_8b91813c9205416ebcbb110af86ac5bc~mv2.jpg

978 ms

eb11d5_85c211380d2643528929d3ec35a5531a~mv2.jpg

eb11d5_85c211380d2643528929d3ec35a5531a~mv2.jpg

1158 ms

eb11d5_2d2a66b9aef9406c83b90c787ff1a227~mv2.jpg

eb11d5_2d2a66b9aef9406c83b90c787ff1a227~mv2.jpg

1131 ms

eb11d5_4ad255fcb2bc4f3aabd2fb9d962ae91a~mv2.jpg

eb11d5_4ad255fcb2bc4f3aabd2fb9d962ae91a~mv2.jpg

1271 ms

White%20Full%20Logo.png

White%20Full%20Logo.png

1302 ms

bundle.min.js

bundle.min.js

144 ms

file.woff

file.woff

784 ms

file.woff

file.woff

806 ms

file.woff

file.woff

806 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

6 ms

146 ms

140 ms

136 ms

132 ms

127 ms

129 ms

162 ms

158 ms

162 ms

156 ms

154 ms

157 ms

deprecation-en.v5.html

deprecation-en.v5.html

13 ms

bolt-performance

bolt-performance

37 ms

deprecation-style.v5.css

deprecation-style.v5.css

12 ms

right-arrow.svg

right-arrow.svg

13 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

6 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

7 ms

Accessibility Review

lillyfinance.com accessibility score

94

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

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

Links do not have a discernible name

Best Practices

lillyfinance.com 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

Page has valid source maps

SEO Factors

lillyfinance.com SEO score

93

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

lillyfinance.com

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