3.9 sec in total
548 ms
3 sec
391 ms
Click here to check amazing Tiger Lillies content for Russia. Otherwise, check out these important facts you probably never knew about tigerlillies.com
Visit tigerlillies.comWe analyzed Tigerlillies.com page load time and found that the first response time was 548 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
tigerlillies.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value13.1 s
0/100
25%
Value10.3 s
8/100
10%
Value590 ms
50/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
548 ms
253 ms
200 ms
175 ms
424 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 59% of them (36 requests) were addressed to the original Tigerlillies.com, 11% (7 requests) were made to Use.typekit.net and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tigerlillies.com.
Page size can be reduced by 16.4 kB (5%)
335.5 kB
319.1 kB
In fact, the total size of Tigerlillies.com main page is 335.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 277.6 kB which makes up the majority of the site volume.
Potential reduce by 9.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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 15% 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 9.6 kB or 71% of the original size.
Potential reduce by 6.8 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. Tiger Lillies images are well optimized though.
Potential reduce by 117 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 38 (69%)
55
17
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tiger Lillies. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.tigerlillies.com
548 ms
pex4pis.js
253 ms
buttons.js
200 ms
feast.1.min.css
175 ms
fms.2.min.js
424 ms
www.tigerlillies.com
96 ms
jquery.min.js
151 ms
bg-main.jpg
596 ms
simpleCart.min.js
162 ms
handlebars-v1.3.0.js
244 ms
jquery.ba-hashchange.min.js
334 ms
jquery.fancybox.css
332 ms
jquery.fancybox.pack.js
336 ms
flexslider.css
330 ms
jquery.flexslider.js
335 ms
bootstrap.min.js
422 ms
isotope.pkgd.min.js
425 ms
validationEngine.jquery.css
422 ms
jquery.validationEngine-en.js
426 ms
jquery.validationEngine.js
511 ms
feasttweets.css
508 ms
spin.min.js
511 ms
jquery.feasttweets.js
508 ms
jquery.placeholder.js
513 ms
burger.png
608 ms
tl-spritesheet.png
678 ms
logo.png
607 ms
hand.png
683 ms
fingers.png
607 ms
highlights.png
687 ms
Lillies%20with%20Jonas%202.jpg
1138 ms
aa.gif
1025 ms
bb.gif
931 ms
wysLC2JNRY-OykUEiyRXdjESjOEvo4N7Hq5w_YDvOHwffwOfggMdeMJ6Mk6f5Mb.woff
171 ms
qnrfygMu9awXkMXSkQHNR9kVdBppLiRb_IVxJiUe_tjffwQfggMdeMJ6Mk6f5MS.woff
316 ms
ga.js
179 ms
getAllAppDefault.esi
220 ms
P4HTGq2mokjVd6z-nJxbwpZ9hiDfmvKbKYXf8XeDrr6ffHVqggMdeMJ6Mk6f5Mb.woff
240 ms
vy4kyIgZIHB7PYONW1RS9Ybu_Q81lsDXPXm0flqP5-9ff4H8gsMdeMJ6Mk6f5Mb.woff
214 ms
jVM4kOqUoUvt8MJa8wRMqzuA37TL0eMBpMkZq_v8yYSffV2KggMdeMJ6Mk6f5Mb.woff
258 ms
jquery.min.js
13 ms
simpleCart.min.js
588 ms
__utm.gif
23 ms
getSegment.php
31 ms
t.dhj
86 ms
p.gif
123 ms
t.dhj
33 ms
hbpix
134 ms
cm
107 ms
x35248
155 ms
s-3271.xgi
11 ms
6 ms
51 ms
xrefid.xgi
7 ms
23593
35 ms
handlebars-v1.3.0.js
91 ms
jquery.ba-hashchange.min.js
88 ms
jquery.fancybox.css
93 ms
jquery.fancybox.pack.js
98 ms
flexslider.css
89 ms
jquery.flexslider.js
95 ms
tigerlillies.com accessibility score
tigerlillies.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
Page has valid source maps
tigerlillies.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tigerlillies.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Tigerlillies.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.
tigerlillies.com
Open Graph description is not detected on the main page of Tiger Lillies. 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: