6.7 sec in total
344 ms
5.5 sec
822 ms
Visit luish.com now to see the best up-to-date Luish content for Colombia and also check out these interesting facts you probably never knew about luish.com
¿Busca una propiedad? ¡Somos especialistas en encontrar la casa o lote de sus sueños! ¡Acompañamos todo el proceso para que no se preocupe de nada! ¡Entre!
Visit luish.comWe analyzed Luish.com page load time and found that the first response time was 344 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
luish.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.8 s
7/100
25%
Value6.2 s
43/100
10%
Value810 ms
36/100
30%
Value0.001
100/100
15%
Value10.7 s
22/100
10%
344 ms
1662 ms
211 ms
209 ms
327 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 43% of them (41 requests) were addressed to the original Luish.com, 16% (15 requests) were made to Media.egorealestate-cdn.com and 10% (10 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Images.egorealestate.com.
Page size can be reduced by 778.1 kB (23%)
3.3 MB
2.5 MB
In fact, the total size of Luish.com main page is 3.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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 55.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. 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 55.7 kB or 82% of the original size.
Potential reduce by 27.4 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. Luish images are well optimized though.
Potential reduce by 352.0 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 352.0 kB or 64% of the original size.
Potential reduce by 343.0 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. Luish.com needs all CSS files to be minified and compressed as it can save up to 343.0 kB or 84% of the original size.
Number of requests can be reduced by 46 (59%)
78
32
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Luish. 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 6 to 1 for CSS and as a result speed up the page load time.
luish.com
344 ms
www.luish.com
1662 ms
_sys_scripts_trace.js.min.js
211 ms
preppy.php
209 ms
style.5_12176-2.wp.egorealestate.com.css
327 ms
CultureInfo
273 ms
_sys_scripts_jquery_jquery-1.7.1.min.js.min.js
341 ms
_sys_scripts_jquery.cookie_jquery.cookie.js.min.js
222 ms
_sys_scripts_prototype.js.min.js
316 ms
_sys_scripts_sys.js.min.js
312 ms
_sys_scripts_mobile-detect.js.min.js
433 ms
_sys_scripts_ashtml_ashtml.js.min.js
376 ms
_sys_scripts_skinform_skinform.js.min.js
418 ms
_sys_scripts_formvalidator_formvalidator.js.min.js
420 ms
_sys_scripts_populate_populate.js.min.js
433 ms
_sys_scripts_stickers.js.min.js
433 ms
_sys_scripts_favoritos_favoritos.js.min.js
477 ms
_sys_scripts_compare_compare.js.min.js
521 ms
css
25 ms
scripts_animation.js5_12176-2.min.js
522 ms
scripts_jquery.number.js5_12176-2.min.js
536 ms
_sys_plugins_DynamicSystemMenuU0L_menuexpand.js.min.js
537 ms
_sys_plugins_Londono_BasicPropertySlideshowScrollU12_ssscroll.js.min.js
541 ms
_sys_scripts_spots_tabs.js.min.js
578 ms
prototype.css
273 ms
defaultskinrange.css
108 ms
defaultdatepicker.css
108 ms
analytics.js
33 ms
ccfbb99f-bfe7-426d-acbd-b58f358888b0.jpg
582 ms
b488dd52-6f63-4523-ab17-78676e6ab99a.jpg
820 ms
946ceffc-3eb7-4638-8375-921d9382badb.png
1265 ms
c6b479b8-137b-4aa0-840f-235fd6b84b55.jpg
1090 ms
9df5fdc5-08bf-45ff-ba7f-20ab93642217.png
1183 ms
70a76b19-e2a4-48f3-b484-e40c949caee4.jpg
1229 ms
d1afe749-8532-461f-b2fd-4f14cdf51de2.jpg
1233 ms
9cd7bd12-7629-4f17-9f36-59dd0b80640a.jpg
1049 ms
8523a741-acd0-4e79-b903-e7657a87e09a.jpg
1275 ms
b511ca3a-2655-49b3-86ec-279ffcdf2e74.jpg
1307 ms
fa9d1b5a-3a64-4a2f-b3cd-5b1b96c7f0ae.jpg
1404 ms
3bd4ba24-8ca5-435e-b602-fe4f288dd095.jpg
1449 ms
3bbacfbf-b259-4d97-9a41-751a48783dfe.jpg
1452 ms
82f46a70-a0a6-4667-979b-3704f79478bf.jpg
1503 ms
3f3e49bb-1bce-4489-9ebb-41111f554a33.jpg
1496 ms
header-background.png
200 ms
es-co.png
200 ms
en-gb.png
199 ms
logo.png
199 ms
facebook.png
198 ms
googleplus.png
199 ms
youtube.png
349 ms
instagram.png
347 ms
logo-br.jpg
345 ms
fontawesome-webfont.woff
582 ms
collect
25 ms
43c04700-0000-0500-0000-0000025366da.jpg
1709 ms
32cf3600-0000-0500-0000-0000023cb72f.jpg
1830 ms
28842f00-0000-0500-0000-000001be837b.jpg
1656 ms
26cf3600-0000-0500-0000-0000023cb58f.jpg
2154 ms
47700e00-0000-0500-0000-000000953eb8.jpg
1681 ms
mediabox-next.png
294 ms
mediabox-prev.png
291 ms
collect
143 ms
CgygjtCsZuU
82 ms
lsansuni.woff
324 ms
ga-audiences
33 ms
www-embed-player-vflfNyN_r.css
20 ms
www-embed-player.js
36 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
18 ms
ad_status.js
30 ms
barra_vermelha_big.png
221 ms
chatdialog
638 ms
roundtrip.js
7 ms
messenger.png
114 ms
ZDDIZ3D6Y5CHDFN2HFMULG.js
252 ms
fbevents.hashing.js
15 ms
out
13 ms
41 ms
out
8 ms
out
13 ms
out
15 ms
out
16 ms
out
16 ms
out
16 ms
out
18 ms
out
18 ms
u.php
57 ms
56 ms
adsct
110 ms
pixel
60 ms
41 ms
sync
14 ms
377928.gif
7 ms
sd
5 ms
pixel
17 ms
in
3 ms
tap.php
113 ms
luish.com 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.
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
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
luish.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
luish.com 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Luish.com 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 Luish.com 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.
luish.com
Open Graph description is not detected on the main page of Luish. 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: