3 sec in total
428 ms
1.8 sec
681 ms
Visit 220i.com.br now to see the best up-to-date 220 I content and also check out these interesting facts you probably never knew about 220i.com.br
This domain may be for sale!
Visit 220i.com.brWe analyzed 220i.com.br page load time and found that the first response time was 428 ms and then it took 2.5 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.
220i.com.br performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.1 s
74/100
25%
Value3.0 s
94/100
10%
Value90 ms
99/100
30%
Value0.298
40/100
15%
Value3.1 s
95/100
10%
428 ms
31 ms
71 ms
28 ms
103 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 47% of them (47 requests) were addressed to the original 220i.com.br, 32% (32 requests) were made to Maps.googleapis.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (459 ms) belongs to the original domain 220i.com.br.
Page size can be reduced by 570.0 kB (40%)
1.4 MB
864.2 kB
In fact, the total size of 220i.com.br main page is 1.4 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. 60% of websites need less resources to load. Images take 664.3 kB which makes up the majority of the site volume.
Potential reduce by 50.5 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 50.5 kB or 86% of the original size.
Potential reduce by 26.8 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. 220 I images are well optimized though.
Potential reduce by 430.2 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 430.2 kB or 68% of the original size.
Potential reduce by 62.5 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. 220i.com.br needs all CSS files to be minified and compressed as it can save up to 62.5 kB or 81% of the original size.
Number of requests can be reduced by 37 (41%)
91
54
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 220 I. 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.
220i.com.br
428 ms
css
31 ms
base.css
71 ms
jquery.min.js
28 ms
center.js
103 ms
js
51 ms
jquery.easing-1.3.js
102 ms
jquery.nav.js
108 ms
jquery.sticky.js
120 ms
jquery.fancybox.pack.js
108 ms
jquery.fancybox-media.js
125 ms
mql.js
199 ms
jquery.flexslider.js
150 ms
selectnav.min.js
158 ms
jquery.scrollTo.js
158 ms
jquery.isotope.min.js
163 ms
contact.js
159 ms
settings.js
190 ms
shortcodes.js
207 ms
last-tw.js
231 ms
220icomunicacao.json
93 ms
normalize.css
145 ms
layout.css
161 ms
shortcodes.css
164 ms
grid.css
227 ms
isotope.css
188 ms
jquery.fancybox.css
184 ms
flexslider.css
208 ms
mediaqueries.css
199 ms
logo-b.png
84 ms
logo-m.png
84 ms
he_thumb.jpg
86 ms
alineeandre_thumb.jpg
85 ms
bosque_thumb.jpg
85 ms
cassio_thumb.jpg
84 ms
centromedicohe_thumb.jpg
127 ms
ilhadocal_thumb.jpg
127 ms
intranetapae_thumb.jpg
145 ms
pipline_thumb.jpg
150 ms
raison_thumb.jpg
185 ms
reinaldo_thumb.jpg
150 ms
texas_thumb.jpg
178 ms
tk_thumb.jpg
175 ms
torres_thumb.jpg
179 ms
andreabotto_thumb.jpg
246 ms
analytics.js
20 ms
header1.jpg
459 ms
pattern.png
222 ms
top-waves.png
206 ms
bottom-waves.png
196 ms
collect
44 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
39 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
39 ms
websymbolsligaregular.woff
144 ms
common.js
9 ms
map.js
35 ms
util.js
55 ms
marker.js
56 ms
onion.js
13 ms
openhand_8_8.cur
77 ms
ViewportInfoService.GetViewportInfo
69 ms
stats.js
24 ms
controls.js
27 ms
css
89 ms
transparent.png
43 ms
logo_ico.png
67 ms
google4.png
40 ms
mapcnt6.png
64 ms
sv5.png
64 ms
tmapctrl.png
48 ms
cb_scout5.png
74 ms
tmapctrl4.png
59 ms
imgs8.png
60 ms
vt
55 ms
vt
63 ms
vt
42 ms
vt
37 ms
vt
97 ms
vt
96 ms
vt
97 ms
vt
97 ms
vt
96 ms
vt
97 ms
vt
119 ms
vt
113 ms
vt
118 ms
vt
119 ms
vt
112 ms
vt
111 ms
vt
138 ms
vt
136 ms
vt
143 ms
vt
144 ms
vt
137 ms
vt
134 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
67 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
68 ms
AuthenticationService.Authenticate
265 ms
220i.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.
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
220i.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
220i.com.br SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 220i.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 220i.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.
220i.com.br
Open Graph description is not detected on the main page of 220 I. 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: