3 sec in total
313 ms
1.9 sec
764 ms
Visit liron.com now to see the best up-to-date Liron content and also check out these interesting facts you probably never knew about liron.com
Art that brings the power of nature indoors.
Visit liron.comWe analyzed Liron.com page load time and found that the first response time was 313 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
liron.com performance score
name
value
score
weighting
Value13.6 s
0/100
10%
Value16.0 s
0/100
25%
Value20.7 s
0/100
10%
Value7,310 ms
0/100
30%
Value0
100/100
15%
Value22.1 s
1/100
10%
313 ms
197 ms
9 ms
217 ms
177 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 49% of them (34 requests) were addressed to the original Liron.com, 12% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Liron.com.
Page size can be reduced by 637.2 kB (16%)
4.0 MB
3.4 MB
In fact, the total size of Liron.com main page is 4.0 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. 65% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 75.9 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 75.9 kB or 78% of the original size.
Potential reduce by 111.1 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. Liron images are well optimized though.
Potential reduce by 241.6 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 241.6 kB or 62% of the original size.
Potential reduce by 208.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. Liron.com needs all CSS files to be minified and compressed as it can save up to 208.6 kB or 83% of the original size.
Number of requests can be reduced by 22 (33%)
66
44
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liron. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
liron.com
313 ms
jquery-1.8.3.min.js
197 ms
jquery.min.js
9 ms
style.css
217 ms
menu-style.css
177 ms
plusone.js
41 ms
widgets.js
9 ms
in.js
24 ms
pinit.js
13 ms
script.js
174 ms
cb=gapi.loaded_0
51 ms
PinExt.png
17 ms
collector_ca_400.jpg
302 ms
collector_commission_400.jpg
302 ms
collector_6_rooms_400.jpg
302 ms
collector_nyc_400.jpg
302 ms
collector_norway_over_there3_400.jpg
303 ms
collector_all_400.jpg
303 ms
collector_w_conversation_400.jpg
460 ms
collector_bloom_400.jpg
521 ms
collectors_fl_400.jpg
460 ms
liron_sissman_art_at_glendale_adventist_medical_center_400.jpg
459 ms
lobby_art_400.jpg
459 ms
kate_hudson_and_ginnifer_goodwin_something_borrowed_w_liron_sissman_painting_400.jpg
459 ms
fall_colors3_liron_sissman_background.jpg
1363 ms
modal_subscribe_bg.jpg
745 ms
purchase_prints.gif
792 ms
main-menu-back.png
787 ms
liron-logo.png
581 ms
button_hover.png
594 ms
button.png
658 ms
down-back5.png
671 ms
down-back3.png
738 ms
facebook_18.jpg
751 ms
twitter_18.jpg
827 ms
youtube_18.jpg
840 ms
purchase_signed.jpg
891 ms
pixel.gif
884 ms
liron_sissman_painting_w_kate_hudson_something_borrowed.jpg
877 ms
collectors_logos_smaller.jpg
1161 ms
press_banner.jpg
930 ms
secureAnonymousFramework
129 ms
HC0vc7daCCk
117 ms
ga.js
28 ms
__utm.gif
67 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
118 ms
cb=gapi.loaded_1
31 ms
fastbutton
131 ms
l3uihl3UN8w
107 ms
like.php
290 ms
pinit_main.js
51 ms
postmessageRelay
175 ms
www-embed-player-vfl-z2BtK.css
129 ms
www-embed-player.js
144 ms
count.json
204 ms
sprite_connect_v14.png
167 ms
cb=gapi.loaded_0
61 ms
cb=gapi.loaded_1
62 ms
tweet_button.64a917b4a230f163048902c783e1530f.en.html
39 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
103 ms
ad_status.js
96 ms
3193398744-postmessagerelay.js
66 ms
rpc:shindig_random.js
47 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
80 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
86 ms
CiVxVZUu1dU.js
105 ms
cb=gapi.loaded_0
21 ms
LVx-xkvaJ0b.png
94 ms
jot
96 ms
liron.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
liron.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
liron.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liron.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Liron.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.
liron.com
Open Graph data is detected on the main page of Liron. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: