6 sec in total
1.1 sec
4.5 sec
376 ms
Welcome to indisa.com.br homepage info - get ready to check Indisa best content for Brazil right away, or after learning these important things about indisa.com.br
Visit indisa.com.brWe analyzed Indisa.com.br page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
indisa.com.br performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value27.8 s
0/100
25%
Value9.8 s
10/100
10%
Value750 ms
39/100
30%
Value0.095
91/100
15%
Value21.7 s
1/100
10%
1092 ms
49 ms
81 ms
121 ms
139 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 51% of them (37 requests) were addressed to the original Indisa.com.br, 16% (12 requests) were made to Maps.googleapis.com and 11% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Indisa.com.br.
Page size can be reduced by 906.0 kB (39%)
2.3 MB
1.4 MB
In fact, the total size of Indisa.com.br main page is 2.3 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 23.9 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 5.0 kB, which is 17% 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 23.9 kB or 80% of the original size.
Potential reduce by 53.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. Indisa images are well optimized though.
Potential reduce by 621.6 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 621.6 kB or 68% of the original size.
Potential reduce by 207.3 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. Indisa.com.br needs all CSS files to be minified and compressed as it can save up to 207.3 kB or 87% of the original size.
Number of requests can be reduced by 38 (57%)
67
29
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indisa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.indisa.com.br
1092 ms
styles.css
49 ms
woocommerce-layout.css
81 ms
woocommerce.css
121 ms
bootstrap.css
139 ms
carousel.css
49 ms
style.css
75 ms
app.css
75 ms
jquery.js
165 ms
jquery-migrate.min.js
89 ms
bootstrap.min.js
112 ms
jquery.form.min.js
62 ms
scripts.js
63 ms
add-to-cart.min.js
90 ms
jquery.blockUI.min.js
90 ms
woocommerce.min.js
89 ms
jquery.cookie.min.js
89 ms
cart-fragments.min.js
91 ms
comment-reply.min.js
136 ms
logo.png
62 ms
indisanew3.jpg
157 ms
bg-text.png
62 ms
indisanew2.jpg
147 ms
indisanew1.jpg
122 ms
catimage.jpg
62 ms
prod1.jpg
84 ms
prod2.png
136 ms
prod3.png
120 ms
prod4.png
173 ms
prod6.png
240 ms
prod5.png
203 ms
iconfaceweb.png
164 ms
iconinstaweb.png
176 ms
embed
157 ms
analytics.js
39 ms
admin-ajax.php
2315 ms
ajax-loader.gif
136 ms
glyphicons-halflings-regular.woff
187 ms
collect
13 ms
js
46 ms
init_embed.js
29 ms
widget_v2.135.js
10 ms
__$$__stringtable_lang_pt_BR.js
68 ms
common.js
54 ms
map.js
55 ms
google4.png
136 ms
overlay.js
16 ms
util.js
119 ms
onion.js
130 ms
search_impl.js
131 ms
StaticMapService.GetMapImage
171 ms
stats.js
85 ms
ViewportInfoService.GetViewportInfo
49 ms
kh
100 ms
transparent.png
35 ms
controls.js
22 ms
vt
81 ms
vt
81 ms
vt
77 ms
vt
81 ms
vt
69 ms
vt
72 ms
vt
108 ms
css
83 ms
mapcnt6.png
26 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
19 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
22 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
29 ms
AuthenticationService.Authenticate
25 ms
avatar_simple_visitor.png
58 ms
aL63HcygAAVYuCCsAAA==
1 ms
woocommerce-smallscreen.css
26 ms
indisa.com.br 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.
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
Links do not have a discernible name
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.
indisa.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
indisa.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indisa.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Portuguese. Our system also found out that Indisa.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.
indisa.com.br
Open Graph description is not detected on the main page of Indisa. 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: