4.6 sec in total
545 ms
3.4 sec
655 ms
Click here to check amazing Lilibee content for Brazil. Otherwise, check out these important facts you probably never knew about lilibee.com.br
Produtos exclusivos em até 10x sem juros e com descontos: Quarto de Bebê, Quarto Infantil, Sala de Estar, Sala de Jantar e muito mais.
Visit lilibee.com.brWe analyzed Lilibee.com.br page load time and found that the first response time was 545 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lilibee.com.br performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value18.6 s
0/100
25%
Value16.9 s
0/100
10%
Value11,290 ms
0/100
30%
Value0.174
69/100
15%
Value22.9 s
1/100
10%
545 ms
170 ms
57 ms
88 ms
108 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Lilibee.com.br, 92% (99 requests) were made to Lilibee.vtexassets.com and 3% (3 requests) were made to Io.vtex.com.br. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cl.avis-verifies.com.
Page size can be reduced by 2.6 MB (40%)
6.5 MB
3.9 MB
In fact, the total size of Lilibee.com.br main page is 6.5 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. Only a small number of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 2.5 MB
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 2.5 MB or 90% of the original size.
Potential reduce by 75.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. Lilibee images are well optimized though.
Potential reduce by 127 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.
Potential reduce by 809 B
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. Lilibee.com.br has all CSS files already compressed.
Number of requests can be reduced by 61 (60%)
102
41
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilibee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
lilibee.com.br
545 ms
www.lilibee.com.br
170 ms
lilibee.store-theme@1.0.73$style.common.min.css
57 ms
lilibee.store-theme@1.0.73$style.small.min.css
88 ms
lilibee.store-theme@1.0.73$style.notsmall.min.css
108 ms
lilibee.store-theme@1.0.73$style.large.min.css
102 ms
lilibee.store-theme@1.0.73$style.xlarge.min.css
105 ms
common.min.css
122 ms
Container.min.css
113 ms
0.min.css
124 ms
0.min.css
123 ms
index.min.css
121 ms
HighlightOverlay.min.css
120 ms
Global.min.css
121 ms
Logo.min.css
132 ms
1.min.css
125 ms
Spinner.min.css
124 ms
4.min.css
128 ms
SearchBar.min.css
129 ms
Autocomplete.min.css
128 ms
1.min.css
132 ms
Minicart.min.css
134 ms
DiscountBadge.min.css
137 ms
ProductSummaryImage.min.css
134 ms
AddProductBtn.min.css
139 ms
0.min.css
136 ms
vtex.product-list@0.37.1$overrides.css
139 ms
vtex.minicart@2.67.1$overrides.css
141 ms
lilibee.store-theme@1.0.73$overrides.css
147 ms
lilibee.store-theme@1.0.73$fonts.css
168 ms
tag.min.js
1900 ms
widde.1.1.0.js
198 ms
polyfill.min.js
325 ms
polyfill.min.js
548 ms
index.min.js
104 ms
runtime.js
104 ms
prop-types.min.js
108 ms
react.production.min.js
129 ms
react-dom.production.min.js
141 ms
react-dom-server.browser.production.min.js
143 ms
react-intl.min.js
142 ms
history.min.js
130 ms
ramda.min.js
100 ms
ls.unveilhooks.min.js
82 ms
lazysizes.min.js
82 ms
cssrelpreload.min.js
80 ms
common.min.js
78 ms
graphql.min.js
78 ms
apollo.min.js
72 ms
index.min.js
71 ms
asset.min.js
76 ms
asset.min.js
75 ms
asset.min.js
74 ms
asset.min.js
74 ms
asset.min.js
73 ms
asset.min.js
69 ms
asset.min.js
73 ms
asset.min.js
73 ms
asset.min.js
73 ms
asset.min.js
74 ms
asset.min.js
70 ms
asset.min.js
66 ms
rc.js
53 ms
af.js
116 ms
fbevents.js
60 ms
iconWhatsapp___44a266739d8611ac5ef8a38a882c2612.svg
71 ms
iconStore___85022ee14fb3a02fbf087b732835a02a.svg
68 ms
iconFavorites___fe73a1d40dae4a687892b30c231a6d76.svg
60 ms
dd49f16d-110d-462e-8eec-3c53a8e4c8ec___80bb7ba767ec5282199907fe9743dc55.jpg
70 ms
benefitBarTruck___7e4a746bb39c9d65b996d8bc89dbc83d.svg
158 ms
benefitBarSecurity___8ad42bc731f99327405b3187191e98f6.svg
74 ms
benefitBarCart___340f8425489ed69221ad2cd085fb1880.svg
63 ms
benefitBarStore___89992869ccbac21a7bba8a032c27b5cd.svg
169 ms
68300f60-700b-4043-ba69-930adc1b8632___7dde23077da6faa58f4cfe5e1fc05d96.gif
76 ms
1dfd20bd-03b7-4459-9090-95e5c8898b83___53f556bd35a35dfb0071f60cedab7d07.gif
70 ms
97b46e44-2298-4591-9812-08b759150b6e___76bd812223a7a0105e905828e3aa0a75.jpg
71 ms
096c9fa3-fd28-4278-877d-6b71b865596e___bcf4086ee51a8f9897a41a19c3db7d81.jpg
78 ms
47434d52-eac6-475b-92a6-2ee491c16d1d___3031f5fe641e9e46739897567d053904.jpg
76 ms
ef0b51fc-ff39-4cf8-aab1-4c67e7674450___6192438d82d3b79eaaec88125851e340.jpg
82 ms
7e036514-d7de-4758-8200-cdbeffbaac0f___54a2e5c69925941bd449d95852bfcd6e.jpg
79 ms
fd0f8342-99f2-4f54-8ded-c815f73f3efd___5dad286620cf11d9fafcadecb36d69c7.jpg
82 ms
521bd810-0985-400b-9b75-6f91a2f6d6ed___6ca4c82522e9a4dbbdef684b3f41f90a.jpg
151 ms
29a99a32-4769-4e4c-90d0-35209a1d5141___4d65a7201d0609d4790d12b2e0d0fcde.jpg
163 ms
edab7aeb-c768-4731-a7e5-18a5c34a9e25___df13896f01b1c87a81dfd573a02de1ae.gif
245 ms
283af2b0-7454-4151-9ee1-16ee705aa448___c021e7e61f31c2f4d53bd29e6ddc32ff.jpg
321 ms
7459bb9f-8b19-465d-8ded-52d1f4a9012e___85ec696cc6ef05faf30ea7c26afc6773.jpg
152 ms
2bb1e047-39ac-4899-b091-8a029c22dfd5___5d350a27ff6ec85052f8c04f01268ca4.jpg
157 ms
696daf1d-1b96-44cb-b00f-2dc5826eefb1___0bfbf321b090788e376bfadf51750ebb.jpg
156 ms
285004-500-auto
160 ms
275777-500-auto
164 ms
302046-500-auto
161 ms
302047-500-auto
166 ms
300373-500-auto
168 ms
300374-500-auto
227 ms
285628-500-auto
225 ms
285629-500-auto
229 ms
c87cbbe6-024f-4996-be4d-523471502fed___db630e17bd528ae648015d5f25a974e6.gif
229 ms
2cbd62b8-ae54-4848-83f2-4bb9a2fd9bdf___7d8982e23a60bd388183f54e2d275fd0.jpg
230 ms
f2de4931-d0c6-431d-b2b4-635e1799d204___8f927055849e0c93c5a34acca9f3bee2.jpg
232 ms
arrowSlideLeft___4a2b1cb8f29f0b78ea1f721715d2bd10.svg
191 ms
arrowInfocard___6ff9192213447dd4c56b3b8ecb443add.svg
187 ms
arrowSeeMore___84ad107959cf807edcdcb73d4a025141.svg
188 ms
Mulish-Medium___95fb28784ad39295fdd64be6662d81d7.ttf
155 ms
Mulish-Regular___5416a925ffafb775c6bffd116d87deb0.ttf
155 ms
Mulish-SemiBold___a4e6f571273de05494ef24d6fb65c885.ttf
158 ms
Mulish-Bold___b7fa867b7522c7629eca3c4b9f31d3c8.ttf
159 ms
iconEnvioImediato___7e7e71f9ed01b02b46d728bfe5605e5c.svg
92 ms
iconExclusivo___5d8e4f4c6012c2f4340669e72939160b.svg
89 ms
lilibee.com.br accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lilibee.com.br 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lilibee.com.br SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilibee.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Lilibee.com.br 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.
lilibee.com.br
Open Graph data is detected on the main page of Lilibee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: