1.3 sec in total
25 ms
832 ms
471 ms
Visit wasi.co now to see the best up-to-date Wasi content for Colombia and also check out these interesting facts you probably never knew about wasi.co
La plataforma inmobiliaria que te ayuda a vender y hacer más negocios. ¡conviértete en el agente inmobiliario número 1!
Visit wasi.coWe analyzed Wasi.co page load time and found that the first response time was 25 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
wasi.co performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value10.6 s
0/100
25%
Value3.3 s
91/100
10%
Value190 ms
91/100
30%
Value1.03
2/100
15%
Value9.0 s
33/100
10%
25 ms
80 ms
31 ms
55 ms
55 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Wasi.co, 68% (44 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 52.6 kB (18%)
294.8 kB
242.2 kB
In fact, the total size of Wasi.co main page is 294.8 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. 70% of websites need less resources to load. Javascripts take 136.3 kB which makes up the majority of the site volume.
Potential reduce by 52.6 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 52.6 kB or 78% of the original size.
Potential reduce by 0 B
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. Wasi images are well optimized though.
Potential reduce by 36 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 30 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. Wasi.co has all CSS files already compressed.
Number of requests can be reduced by 6 (35%)
17
11
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wasi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for CSS and as a result speed up the page load time.
wasi.co
25 ms
wasi.co
80 ms
style.min.css
31 ms
black-friday.min.css
55 ms
cookieconsent.min.css
55 ms
fonts.min.css
58 ms
global.min.js
55 ms
cookieconsent.min.js
51 ms
black-friday-mundial.png
72 ms
logo.svg
48 ms
phone.svg
51 ms
whatsapp.svg
54 ms
css2
50 ms
css2
47 ms
css2
41 ms
tshadow.png
66 ms
analytics-browser-2.0.0-min.js.gz
47 ms
bg-footer.png
36 ms
blue-arrow.svg
35 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
42 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
40 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
41 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
42 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
42 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
42 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
44 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
48 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
47 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
43 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
47 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
48 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
49 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
49 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
49 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
50 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
49 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
51 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
51 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
49 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
49 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
51 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
50 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
51 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
51 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
52 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
52 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
51 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
52 ms
KFOlCnqEu92Fr1MmYUtfChc-AMP6lbBP.woff
53 ms
KFOlCnqEu92Fr1MmYUtfCxc-AMP6lbBP.woff
52 ms
KFOlCnqEu92Fr1MmYUtfBxc-AMP6lbBP.woff
53 ms
KFOlCnqEu92Fr1MmYUtfCBc-AMP6lbBP.woff
53 ms
KFOlCnqEu92Fr1MmYUtfABc-AMP6lbBP.woff
53 ms
KFOlCnqEu92Fr1MmYUtfCRc-AMP6lbBP.woff
53 ms
FBVwdDflz-iPfoPuIC2iKgEB_UBFIEwpNzY.woff
65 ms
FBVwdDflz-iPfoPuIC2iKgEB_U5FIEwpNzZQXQ.woff
64 ms
FBVwdDflz-iPfoPuIC2iKgEB_U9FIEwpNzZQXQ.woff
36 ms
FBVwdDflz-iPfoPuIC2iKh0C_UBFIEwpNzY.woff
37 ms
FBVwdDflz-iPfoPuIC2iKh0C_U5FIEwpNzZQXQ.woff
31 ms
FBVwdDflz-iPfoPuIC2iKh0C_U9FIEwpNzZQXQ.woff
30 ms
FBVzdDflz-iPfoPuIC2iIqYn7m1nK2Y.woff
414 ms
FBVzdDflz-iPfoPuIC2iIqgn7m1nK2YTPg.woff
64 ms
FBVzdDflz-iPfoPuIC2iIqkn7m1nK2YTPg.woff
65 ms
fa-regular-400.ttf
70 ms
fa-solid-900.ttf
72 ms
wasi.co accessibility score
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
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
wasi.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wasi.co 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wasi.co can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Wasi.co 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.
wasi.co
Open Graph data is detected on the main page of Wasi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: