4.6 sec in total
379 ms
4 sec
280 ms
Click here to check amazing Localisa content for Brazil. Otherwise, check out these important facts you probably never knew about localisa.com.br
Visit localisa.com.brWe analyzed Localisa.com.br page load time and found that the first response time was 379 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
localisa.com.br performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.6 s
86/100
25%
Value3.8 s
84/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
379 ms
16 ms
53 ms
53 ms
5 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 35% of them (53 requests) were addressed to the original Localisa.com.br, 13% (19 requests) were made to Widgets.uol.com.br and 11% (16 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Widgets.uol.com.br.
Page size can be reduced by 158.8 kB (41%)
391.6 kB
232.7 kB
In fact, the total size of Localisa.com.br main page is 391.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 206.8 kB which makes up the majority of the site volume.
Potential reduce by 119.7 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 45.1 kB, which is 35% 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 119.7 kB or 92% of the original size.
Potential reduce by 8.5 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. Localisa images are well optimized though.
Potential reduce by 29.9 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 29.9 kB or 58% of the original size.
Potential reduce by 662 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. Localisa.com.br needs all CSS files to be minified and compressed as it can save up to 662 B or 18% of the original size.
Number of requests can be reduced by 85 (59%)
143
58
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Localisa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
localisa.com.br
379 ms
branding.css
16 ms
localisa-logo2.gif
53 ms
ft1.jpg
53 ms
adsbygoogle.js
5 ms
image.gif
52 ms
localisa-achatudo.gif
52 ms
ff7a.jpg
51 ms
88.gif
74 ms
branding.css
67 ms
ff2a.jpg
58 ms
ff4.jpg
57 ms
ff9.jpg
25 ms
ff11.jpg
25 ms
ff13.jpg
95 ms
ff17.jpg
95 ms
ff15.jpg
93 ms
ff19.jpg
92 ms
ff21.jpg
93 ms
ff23.jpg
95 ms
ff5.jpg
93 ms
ff34.jpg
93 ms
f35.jpg
93 ms
ff25.jpg
83 ms
ff29.jpg
83 ms
ff27.jpg
82 ms
ff7.jpg
154 ms
ff31.jpg
151 ms
widget.js
497 ms
empty.gif
509 ms
ca-pub-1145382074514651.js
167 ms
zrt_lookup.html
133 ms
show_ads_impl.js
60 ms
widget.css
458 ms
f11a.jpg
89 ms
ff3.jpg
90 ms
ff10.jpg
89 ms
ff12.jpg
90 ms
ff14.jpg
111 ms
ff18.jpg
110 ms
ff16.jpg
108 ms
ff20.jpg
110 ms
ff22.jpg
110 ms
ff24.jpg
111 ms
ff6.jpg
130 ms
ff33.jpg
132 ms
ff36.jpg
132 ms
ff26.jpg
131 ms
ff30.jpg
133 ms
ff28.jpg
131 ms
ff8.jpg
152 ms
ff32.jpg
153 ms
uolwidgetstools.js
810 ms
uolwidgetstools.js
942 ms
uolwidgetstools.js
1072 ms
uolwidgetstools.js
1073 ms
estrela.gif
151 ms
15261_lgo_magazine_luiza_br.png
149 ms
subsub.gif
151 ms
publi-shop1.jpg
150 ms
publi-poli2.jpg
191 ms
publi-pontofrio2.jpg
169 ms
publi-americanas2.gif
170 ms
banner-seph.gif
192 ms
logo-embaixo.gif
170 ms
ads
284 ms
osd.js
10 ms
abg.js
27 ms
googlelogo_color_112x36dp.png
46 ms
index.html
45 ms
s
16 ms
x_button_blue2.png
6 ms
css
59 ms
unslider.css
5 ms
jquery.min.js
63 ms
exitapi-impl.js
5 ms
addata.js
6 ms
unslider-min.js
7 ms
bg_tipo-3_topol.png
167 ms
bg_tipo-3_topor.png
159 ms
logo_zh_peq2.png
174 ms
bg-ct.gif
335 ms
bg_tipo-3_baser.png
347 ms
bg_tipo-3_basel.gif
333 ms
list-zh.gif
331 ms
bg_tipo-3_link.gif
359 ms
proxy.jsp
536 ms
728-90.jpg
26 ms
1.jpg
7 ms
7.jpg
5 ms
3.jpg
6 ms
6.jpg
5 ms
5.jpg
9 ms
4.jpg
9 ms
2.jpg
6 ms
8.jpg
8 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
48 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
5 ms
UolWidgetsConfigCINEMA.js
263 ms
UolWidgetsConfigCINEMA.js
133 ms
UolWidgetsConfigCINEMA.js
133 ms
click.uol.com.br
411 ms
noticias-ciavaliacao.jhtm
813 ms
UolWidgetsConfigCELEBRIDADES.js
133 ms
MostraSelo.php
56 ms
fb2.gif
23 ms
urchin.js
21 ms
beacon.js
5 ms
__utm.gif
10 ms
activeview
13 ms
noticias-cinovidades.jhtm
810 ms
click.uol.com.br
404 ms
noticias-cireportagens.jhtm
677 ms
click.uol.com.br
269 ms
x.gif
408 ms
noticias-cereportagens.jhtm
544 ms
click.uol.com.br
136 ms
x.gif
285 ms
x.gif
413 ms
x.gif
413 ms
uoluatools.js
134 ms
UolGetParamTool.js
134 ms
topeua.js
541 ms
UOLWidgetsStyleCinema.css
272 ms
widgets-cinema-top.js
134 ms
widgets-cinema-bottom.js
135 ms
uoluatools.js
133 ms
UOLWidgetsStyleCelebridades-novo.css
266 ms
widgets-celebridades-top.js
134 ms
widgets-celebridades-bottom.js
135 ms
titulo.gif
675 ms
titulo-bg.gif
670 ms
ico_indice.gif
141 ms
widgets-ico4.gif
140 ms
titulo.gif
799 ms
seta-baixo.gif
930 ms
seta-direita.gif
931 ms
noticias-cinovidades.jhtm
275 ms
titulo-bg.gif
669 ms
seta-baixo.gif
802 ms
seta-direita.gif
802 ms
uoluatools.js
133 ms
UolGetParamTool.js
133 ms
widgets-cinema-top.js
136 ms
widgets-cinema-bottom.js
136 ms
ico_verfotos.gif
136 ms
ico_assistir.gif
134 ms
ico_grupodiscussao.gif
132 ms
ico_ondeassistir.gif
264 ms
um-louco-apaixonado-132-div.jpg
652 ms
localisa.com.br accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
localisa.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
localisa.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
PT
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Localisa.com.br 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 Localisa.com.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
localisa.com.br
Open Graph description is not detected on the main page of Localisa. 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: