4.4 sec in total
1.4 sec
2.7 sec
296 ms
Visit liltomatoes.com now to see the best up-to-date Lil Tomatoes content and also check out these interesting facts you probably never knew about liltomatoes.com
Lil' Tomatoes
Visit liltomatoes.comWe analyzed Liltomatoes.com page load time and found that the first response time was 1.4 sec and then it took 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.
liltomatoes.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value13.5 s
0/100
25%
Value45.4 s
0/100
10%
Value37,840 ms
0/100
30%
Value0.196
63/100
15%
Value54.1 s
0/100
10%
1406 ms
660 ms
761 ms
696 ms
673 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 86% of them (43 requests) were addressed to the original Liltomatoes.com, 10% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Liltomatoes.com.
Page size can be reduced by 864.8 kB (40%)
2.2 MB
1.3 MB
In fact, the total size of Liltomatoes.com main page is 2.2 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 44.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 12.8 kB, which is 25% 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 44.6 kB or 88% of the original size.
Potential reduce by 98.0 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. Lil Tomatoes images are well optimized though.
Potential reduce by 279.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 279.5 kB or 71% of the original size.
Potential reduce by 442.7 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. Liltomatoes.com needs all CSS files to be minified and compressed as it can save up to 442.7 kB or 86% of the original size.
Number of requests can be reduced by 18 (41%)
44
26
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lil Tomatoes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
liltomatoes.com
1406 ms
jquery-2.1.1.min.js
660 ms
bootstrap.min.css
761 ms
bootstrap.min.js
696 ms
font-awesome.min.css
673 ms
jquery.fancybox.css
511 ms
jquery.fancybox.js
252 ms
css
64 ms
css
27 ms
animate.css
353 ms
stylesheet.css
484 ms
font-awesome.css
581 ms
owl.carousel.css
609 ms
style.css
744 ms
revslider.css
695 ms
parallax.js
735 ms
common.js
754 ms
common1.js
808 ms
cloudzoom.js
809 ms
owl.carousel.min.js
809 ms
revslider.js
844 ms
logo.png
218 ms
search-icon.png
221 ms
boys_collection.jpg
264 ms
loading.gif
221 ms
banner-01-765x433.jpg
219 ms
banner02-765x433.jpg
295 ms
RHS-offer-banner.jpg
217 ms
RHS-offer-banner1.jpg
221 ms
RHS-offer-banner2.jpg
338 ms
slide1-332x390.jpg
371 ms
slide2-332x390.jpg
444 ms
slide3-332x390.jpg
348 ms
footer-logo.png
337 ms
payment-1.png
338 ms
payment-2.png
367 ms
payment-3.png
365 ms
payment-4.png
380 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
185 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
186 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
187 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
186 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
187 ms
fontawesome-webfont.woff
433 ms
fontawesome-webfont.woff
465 ms
plus-img.png
216 ms
to-top-arrow.png
212 ms
left-a.png
233 ms
right-a.png
266 ms
glyphicons-halflings-regular.woff
247 ms
liltomatoes.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
liltomatoes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
liltomatoes.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liltomatoes.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 Liltomatoes.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.
liltomatoes.com
Open Graph description is not detected on the main page of Lil Tomatoes. 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: