4.6 sec in total
554 ms
3.6 sec
427 ms
Welcome to poloar.com.br homepage info - get ready to check Poloar best content for Brazil right away, or after learning these important things about poloar.com.br
Na Poloar você encontra a maior variedade de condicionadores de ar, além do melhor atendimento e condições exclusiva. Acesse e confira.
Visit poloar.com.brWe analyzed Poloar.com.br page load time and found that the first response time was 554 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
poloar.com.br performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value18.4 s
0/100
25%
Value26.7 s
0/100
10%
Value17,470 ms
0/100
30%
Value0.351
31/100
15%
Value37.4 s
0/100
10%
554 ms
197 ms
233 ms
120 ms
159 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 5% of them (7 requests) were addressed to the original Poloar.com.br, 55% (78 requests) were made to Poloar.vteximg.com.br and 8% (11 requests) were made to Io.vtex.com.br. The less responsive or slowest element that took the longest time to load (808 ms) relates to the external source Poloar.vteximg.com.br.
Page size can be reduced by 576.1 kB (28%)
2.1 MB
1.5 MB
In fact, the total size of Poloar.com.br main page is 2.1 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 77.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 77.2 kB or 82% of the original size.
Potential reduce by 81.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. Poloar images are well optimized though.
Potential reduce by 182.8 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 182.8 kB or 65% of the original size.
Potential reduce by 234.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. Poloar.com.br needs all CSS files to be minified and compressed as it can save up to 234.7 kB or 82% of the original size.
Number of requests can be reduced by 62 (56%)
110
48
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poloar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.poloar.com.br
554 ms
rc.js
197 ms
jquery-1.8.3.min.js
233 ms
swfobject.js
120 ms
vtex.ajax.wait.js
159 ms
vtex.common.js
131 ms
vtex-i18n.min.js
120 ms
vtex-utils.min.js
128 ms
dust-core-2.3.5.min.js
124 ms
vtex.tagmanager.helper.js
132 ms
vtex-events-all.min.js
124 ms
vtex-analytics.js
116 ms
vtex.min.js
183 ms
vtexid-jquery.min.js
192 ms
jquery.ui.core.js
414 ms
jquery.ui.widget.js
584 ms
jquery.ui.position.js
413 ms
jquery.ui.autocomplete.js
193 ms
vtex.commerce.search.js
199 ms
vtex.viewPart.fullTextSearchBox.js
211 ms
portal-minicart-with-template.min.js
187 ms
portal-template-as-modal.min.js
186 ms
portal-sku-selector-with-template.min.js
178 ms
vtex.cookie.js
260 ms
jquery.pager.js
258 ms
font-awesome.min.css
300 ms
jquery-ui.min.css
260 ms
bootstrap.min.css
808 ms
owl.carousel.css
301 ms
style.css
326 ms
estiloteste.css
384 ms
carrossel.css
392 ms
font-awesome.min.css
298 ms
zoom.css
433 ms
jquery.scrollbox.js
446 ms
Track.js
469 ms
thickbox.js
521 ms
json2.js
506 ms
vtex.viewPart.CallCenterDisclaimer.js
523 ms
vtex.viewPart.ajaxLoader_V2.js
531 ms
vtex-view-part.js
593 ms
vtex.commerce.batchbuy.js
603 ms
vtex.jsevents.js
603 ms
vtex.skuEvents.js
614 ms
vtex.skuEvents.skuDataFetcher.js
614 ms
jquery.livequery.min.js
695 ms
jquery.prettyPhoto.js
759 ms
lean-prettyPhoto.js
673 ms
vtex.commerce.Compare.js
693 ms
vtex.make.mobile.pager.js
697 ms
bootstrap.js
761 ms
pace.min.js
771 ms
owl.carousel.min.js
685 ms
menu-responsivo.js
683 ms
advanced-filter.js
714 ms
admake-mini-cart.js
666 ms
default.js
671 ms
analytics.js
125 ms
ecommerce.js
33 ms
collect
102 ms
logo-poloar.png
48 ms
i-split.png
75 ms
i-inverter.png
73 ms
i-janela.png
88 ms
i-piso-teto.png
75 ms
i-cassete.png
76 ms
i-multi-split.png
95 ms
i-portatil.png
99 ms
i-cortina-de-ar.png
97 ms
1BannerSite_1170x312.png
549 ms
2BannerSite_1170x312.png
170 ms
logo-carrier.png
100 ms
Logo-Elgin.png
157 ms
Logo-Fujitsu.png
165 ms
Logo-LG.png
158 ms
Logo-Midea.png
164 ms
Logo-Samsung.png
159 ms
Logo-Springer.png
162 ms
Logo-Totaline.png
166 ms
Logo-Daikin.png
234 ms
.png
435 ms
PT18FRCAV2_18000_Carrier.png
437 ms
HIWELG024CRH220_24000_ELGIN.png
438 ms
.png
433 ms
PT18FRCAV2_18000_Carrier.png
438 ms
ZQA215RB_21000_Springer.png
440 ms
vitrine-daikin-tri.png
443 ms
.png
452 ms
ASBG1209LJCA_18000_Fujitsu-com-sensor.png
446 ms
.png
484 ms
UCLELG030CRH220_30000_Elgin.png
467 ms
CSTFUJ048CRH380M_48000_Fujitsu.png
514 ms
gtm.js
86 ms
getProfile
60 ms
formas_de_pagamento.jpg
492 ms
logo-innovate.png
500 ms
large_large_logo_vtex.png
484 ms
logo-vtex.png
475 ms
orderForm
183 ms
fontawesome-webfont.woff
76 ms
fontawesome-webfont.woff
77 ms
orderForm
276 ms
collect
131 ms
getSelo.js
233 ms
aw.js
194 ms
dt-faq.js
196 ms
tracking.js
155 ms
ld.js
152 ms
Track.aspx
175 ms
disclaimer
164 ms
welcome
174 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
107 ms
collect
486 ms
aHR0cDovL3d3dy5wb2xvYXIuY29tLmJyLw==
451 ms
get.php
453 ms
aHR0cDovL3d3dy5wb2xvYXIuY29tLmJyLw==
446 ms
initialize.js
57 ms
promise.js
384 ms
siteblindado.gif
416 ms
iframeResizer.min.js
23 ms
event
63 ms
event
63 ms
vtex_cart.js
39 ms
fetch.js
61 ms
index.html
49 ms
jquery-1.11.1.js
202 ms
angular.min.js
84 ms
angular-route.min.js
237 ms
angular-sanitize.min.js
238 ms
fingerprint.js
47 ms
iframeResizer.contentWindow.min.js
56 ms
style.css
81 ms
appFAQ.js
71 ms
17 ms
nr-918.min.js
101 ms
39099a57-85ea-4375-8bec-6b7ce460fc68
20 ms
img_33785.png
515 ms
dis.aspx
90 ms
dis.aspx
89 ms
d7dea43aa7
224 ms
logo.png
70 ms
poloar.com.br 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 input fields 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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
poloar.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
poloar.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
Links do not have descriptive text
Image elements do not have [alt] attributes
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poloar.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Poloar.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.
poloar.com.br
Open Graph description is not detected on the main page of Poloar. 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: