2.7 sec in total
82 ms
2.2 sec
444 ms
Click here to check amazing Lichias content. Otherwise, check out these important facts you probably never knew about lichias.com
Tudo sobre lichia, curiosidades, cotações, cadastro de produtores, destinado a produtores, importadores, intermediários, consumidores e apaixonados por lichias
Visit lichias.comWe analyzed Lichias.com page load time and found that the first response time was 82 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
lichias.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value6.8 s
7/100
25%
Value16.1 s
0/100
10%
Value18,980 ms
0/100
30%
Value0.033
100/100
15%
Value26.4 s
0/100
10%
82 ms
77 ms
91 ms
47 ms
52 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Lichias.com, 62% (56 requests) were made to Static.parastorage.com and 13% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (531 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.8 MB (59%)
4.8 MB
2.0 MB
In fact, the total size of Lichias.com main page is 4.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 87.2 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 87.2 kB or 82% of the original size.
Potential reduce by 8.3 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. Lichias images are well optimized though.
Potential reduce by 2.6 MB
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 2.6 MB or 75% of the original size.
Potential reduce by 135.4 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. Lichias.com needs all CSS files to be minified and compressed as it can save up to 135.4 kB or 84% of the original size.
Number of requests can be reduced by 62 (77%)
81
19
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lichias. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lichias.com
82 ms
www.lichias.com
77 ms
bt
91 ms
require.min.js
47 ms
main-r.min.js
52 ms
viewer.css
49 ms
dynamicmodel
11 ms
dbbca7_2aafd0239368e8e9a04061e35de28d19_126.json.z
501 ms
dbbca7_cf2f6b9e86d31dfd36a7f9c817a99add_123.json.z
506 ms
ugc-viewer
57 ms
bt
93 ms
skins.min.js
270 ms
components.min.js
267 ms
utils.min.js
86 ms
core.min.js
91 ms
react-with-addons.min.js
85 ms
lodash.min.js
36 ms
TweenMax.min.js
56 ms
layout.min.js
87 ms
tpa.min.js
88 ms
fonts.min.js
85 ms
animations.min.js
88 ms
swfobject.min.js
93 ms
mousetrap.min.js
89 ms
tweenEngine.min.js
90 ms
DrawSVGPlugin.min.js
90 ms
react-dom.min.js
90 ms
ScrollToPlugin.min.js
259 ms
widgets.min.js
91 ms
experiment.js
91 ms
render.min.js
252 ms
wixappsCore.min.js
256 ms
wixappsBuilder.min.js
253 ms
zepto.min.js
250 ms
color.min.js
252 ms
bt
236 ms
dc.js
218 ms
react-dom-server.min.js
125 ms
bt
370 ms
latin.css
31 ms
dbbca7_f9d8bf74e7f94a638524a98d66d51f93.jpg
439 ms
StripSlideshow.html
162 ms
cartwidget
171 ms
__utm.gif
105 ms
dbbca7_e9a6ffa41d7d459cbf6ce4b25236f27e.jpg
531 ms
84770f_c44337bdebe947c58a78f7b6ba401354.png
132 ms
dbbca7_0a28b5de5c23404e8c45861a8d33b0ca.jpg
369 ms
dbbca7_36088bd7c1844981ba1952341f6cb657.jpg
396 ms
dbbca7_aae6c76a6b0c434e8282438af51fd985.jpg
370 ms
84770f_93639e4c394e4d119678909b0ab37371.png
225 ms
11062b_1c6001b9888a4ba89939a510eee406d1f000.jpg
268 ms
bt
124 ms
bt
124 ms
bt
124 ms
jquery.min.js
134 ms
jquery.easing-1.3.min.js
127 ms
lodash.min.js
128 ms
webfont.js
262 ms
Wix.js
367 ms
style.min.css
127 ms
app.min.js
127 ms
cart-widget.css
121 ms
wix.min.js
148 ms
jquery.min.js
125 ms
lodash.min.js
120 ms
angular.min.js
214 ms
angular-translate.min.js
120 ms
angular-debounce.js
175 ms
angular-locale_pt.js
232 ms
messages_pt.js
173 ms
cartWidgetModules.js
233 ms
cartWidget.min.js
212 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
149 ms
8fb1090e-b4d0-4685-ac8f-3d0c29d60130.woff
188 ms
20323430-24f4-4767-9d4d-060d1e89758a.woff
187 ms
ae844b11-5158-4caf-90b4-7ace49ac3440.woff
187 ms
d3bbaa1b-d5e3-431f-93a7-9cea63601bb6.woff
231 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
208 ms
nr-632.min.js
165 ms
ugc-viewer
131 ms
cartwidgetPopup
250 ms
popup_close_x.png
38 ms
c99d7f1ab0
78 ms
dbbca7_d1a102730cb042c5a2e8a7f30531389f.jpg
411 ms
mini-cart.css
33 ms
cartWidgetPopupModules.js
7 ms
cartWidgetPopup.min.js
24 ms
ec
54 ms
cartWidgetPopupView.html
159 ms
11062b_1c6001b9888a4ba89939a510eee406d1f000.jpg
31 ms
lichias.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
button, link, and menuitem elements do not have accessible names.
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
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
lichias.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lichias.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lichias.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Lichias.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.
lichias.com
Open Graph data is detected on the main page of Lichias. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: