5 sec in total
458 ms
4 sec
574 ms
Welcome to olist.com homepage info - get ready to check Olist best content for Brazil right away, or after learning these important things about olist.com
As melhores tecnologias, ferramentas e integrações na sua operação de vendas online está no Olist. Acelere o seu negócio!
Visit olist.comWe analyzed Olist.com page load time and found that the first response time was 458 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
olist.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value6.8 s
7/100
25%
Value17.7 s
0/100
10%
Value35,180 ms
0/100
30%
Value0.184
66/100
15%
Value50.3 s
0/100
10%
458 ms
785 ms
9 ms
427 ms
269 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Olist.com, 28% (27 requests) were made to Solidarium.s3.amazonaws.com and 15% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (862 ms) relates to the external source Solidarium.s3.amazonaws.com.
Page size can be reduced by 768.7 kB (53%)
1.5 MB
683.5 kB
In fact, the total size of Olist.com main page is 1.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. 65% of websites need less resources to load. CSS take 520.4 kB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 16% 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 47.2 kB or 79% of the original size.
Potential reduce by 10.4 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. Olist images are well optimized though.
Potential reduce by 277.0 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 277.0 kB or 60% of the original size.
Potential reduce by 434.1 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. Olist.com needs all CSS files to be minified and compressed as it can save up to 434.1 kB or 83% of the original size.
Number of requests can be reduced by 42 (49%)
85
43
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
olist.com
458 ms
bootstrap.min.css
785 ms
font-awesome.min.css
9 ms
jquery-ui.min.css
427 ms
jquery.tagsinput.css
269 ms
css
34 ms
icomoon.css
415 ms
estilo.css
670 ms
jquery.min.js
53 ms
jquery.min.js
648 ms
bootstrap.min.js
644 ms
jquery-ui.min.js
662 ms
rd-js-integration.min.js
53 ms
conversion.js
28 ms
8a332032-6ca5-4968-88a8-c61c69054baa-loader.js
63 ms
scripts.js
550 ms
mask.min.js
280 ms
fbds.js
165 ms
logo-olist.svg
161 ms
logo-olist-fixed.svg
152 ms
bg-img-video.jpg
162 ms
capa-pegn.jpg
284 ms
logo-pegn.svg
156 ms
capa-fsaopaulo.jpg
162 ms
logo-folhaspaulo.svg
283 ms
capa-catraca.jpg
287 ms
logo-catracalivre.svg
286 ms
ilustracao-simulacao2.jpg
782 ms
ilustracao-funciona2.jpg
575 ms
cha-simples.gif
401 ms
cronometro-rapido.gif
401 ms
roda-revolucionario.gif
404 ms
hRL3Sm8v28s
149 ms
mask-video.png
320 ms
sprite.png
576 ms
icomoon.ttf
862 ms
fontawesome-webfont.woff
10 ms
nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf
56 ms
TNtGAwzXtCEY_5hzRlIJNPesZW2xOQ-xsNqO47m55DA.ttf
96 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
122 ms
K6ngFdK5haaaRGBV8waDwA.ttf
124 ms
160 ms
www-embed-player-vflQrT_sR.css
157 ms
www-embed-player.js
193 ms
base.js
267 ms
91 ms
mixpanel-2-latest.min.js
114 ms
analytics.js
76 ms
traffic-source-cookie.min.js
40 ms
lead-tracking.min.js
41 ms
sdk.js
297 ms
send
220 ms
59 ms
collect
37 ms
13 ms
14 ms
collect
180 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
44 ms
ad_status.js
54 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
95 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
107 ms
ga-audiences
42 ms
58 ms
xd_arbiter.php
215 ms
xd_arbiter.php
419 ms
estilo-print.css
138 ms
21 ms
page.php
214 ms
fuz5iiRHS6l.css
284 ms
4zP11uWGt9j.css
354 ms
_rx8naC75Dy.js
555 ms
3o1espZ6Mhb.js
482 ms
XDG5PZnYHRI.js
619 ms
qLkez9vV75x.js
630 ms
g7eQ7KS-feD.js
629 ms
pJPDNGWM_rf.js
618 ms
11026113_1145591852120880_6253063756882475611_n.jpg
357 ms
12107077_1145128368833895_7730451962121949079_n.jpg
424 ms
11903935_908697972512415_4362297295879681039_n.jpg
494 ms
12733521_1760491407507389_8396451215604901424_n.jpg
561 ms
12240031_1003188176421606_4044127283562887906_n.jpg
560 ms
11036086_619375238207664_4765347246354208661_n.jpg
559 ms
544660_474812845919466_289867679_n.jpg
561 ms
12647161_213136915699797_6540820703799037465_n.jpg
562 ms
12728884_1111581658882776_5633190412217617839_n.jpg
562 ms
12733382_1085622521459785_8377724854109011666_n.jpg
626 ms
1510895_990814317598894_4385127553599992532_n.jpg
627 ms
1000246_630512906986873_1370772246_n.jpg
689 ms
12654690_1012758585457935_3033288995809111715_n.jpg
628 ms
390760_235011233239996_1609320670_n.jpg
627 ms
12801412_1673893052892061_7639116044028092014_n.jpg
669 ms
wL6VQj7Ab77.png
83 ms
s7jcwEQH7Sx.png
83 ms
6GqoI2ZyIrf.png
71 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
69 ms
kDOzhTr2W91.js
73 ms
olist.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
olist.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
Browser errors were logged to the console
olist.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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olist.com 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 Olist.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.
olist.com
Open Graph data is detected on the main page of Olist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: