4.1 sec in total
662 ms
3.1 sec
284 ms
Click here to check amazing Vasselai content for Brazil. Otherwise, check out these important facts you probably never knew about vasselai.imb.br
Negócios imobiliários no Alto Vale do Itajaí - CRECI 3039J
Visit vasselai.imb.brWe analyzed Vasselai.imb.br page load time and found that the first response time was 662 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
vasselai.imb.br performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value2.2 s
95/100
25%
Value5.3 s
58/100
10%
Value310 ms
77/100
30%
Value0.059
98/100
15%
Value6.1 s
63/100
10%
662 ms
777 ms
478 ms
511 ms
489 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Vasselai.imb.br, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vasselai.imb.br.
Page size can be reduced by 832.2 kB (38%)
2.2 MB
1.4 MB
In fact, the total size of Vasselai.imb.br main page is 2.2 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 42.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 18.9 kB, which is 39% 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 42.7 kB or 88% of the original size.
Potential reduce by 33.0 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. Vasselai images are well optimized though.
Potential reduce by 280.4 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 280.4 kB or 71% of the original size.
Potential reduce by 476.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. Vasselai.imb.br needs all CSS files to be minified and compressed as it can save up to 476.1 kB or 89% of the original size.
Number of requests can be reduced by 23 (46%)
50
27
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vasselai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
vasselai.imb.br
662 ms
bootstrap.css
777 ms
style.min.css
478 ms
main.min.css
511 ms
magnific-popup.css
489 ms
owl.carousel.css
1005 ms
owl.theme.css
510 ms
css
25 ms
jquery-1.10.2.min.js
761 ms
jquery.magnific-popup.min.js
619 ms
jquery.validate.js
646 ms
jquery.maskedinput.js
646 ms
jquery.lazyload.min.js
759 ms
owl.carousel.min.js
790 ms
bootstrap.js
928 ms
fhmm.js
896 ms
bootstrap-select.js
901 ms
jquery.fancybox.pack.js
904 ms
jquery.flexslider.js
933 ms
slider.js
1036 ms
master.js
1041 ms
flexslider.css
581 ms
sinister.css
609 ms
fhmm.css
618 ms
jquery.fancybox.css
669 ms
ga.js
84 ms
bg-site.jpg
430 ms
bg-top-3.png
427 ms
logo2.png
240 ms
img_b1d4ade.jpg
305 ms
img_1d40989.jpg
422 ms
img_bt_simulador.jpg
305 ms
btn_bb.gif
306 ms
btn_brad.gif
420 ms
btn_caixa.gif
425 ms
btn_hsbc.gif
430 ms
btn_itau.gif
559 ms
btn_sant.gif
563 ms
img.php
696 ms
img.php
937 ms
img.php
755 ms
img.php
1039 ms
plus.png
698 ms
img.php
1029 ms
img.php
893 ms
img.php
1024 ms
img.php
1077 ms
img.php
1211 ms
img.php
1262 ms
img.php
1209 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
177 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
177 ms
wkfQbvfT_02e2IWO3yYueQ.woff
177 ms
BVtM30trf7q_jfqYeHfjtA.woff
178 ms
fontawesome-webfont.woff
1120 ms
__utm.gif
13 ms
vasselai.imb.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
vasselai.imb.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
General
Impact
Issue
Detected JavaScript libraries
vasselai.imb.br SEO score
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 Vasselai.imb.br 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 Vasselai.imb.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.
vasselai.imb.br
Open Graph description is not detected on the main page of Vasselai. 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: