8.4 sec in total
2.7 sec
4.9 sec
800 ms
Click here to check amazing Lomelin content for Mexico. Otherwise, check out these important facts you probably never knew about lomelin.mx
Venta de propiedades, renta de propiedades, compra de propiedades en todo México
Visit lomelin.mxWe analyzed Lomelin.mx page load time and found that the first response time was 2.7 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lomelin.mx performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value9.7 s
0/100
25%
Value8.4 s
18/100
10%
Value1,330 ms
17/100
30%
Value0.006
100/100
15%
Value16.3 s
5/100
10%
2716 ms
106 ms
16 ms
70 ms
72 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 53% of them (75 requests) were addressed to the original Lomelin.mx, 13% (19 requests) were made to Crm.lomelin.mx and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Lomelin.mx.
Page size can be reduced by 1.8 MB (15%)
12.0 MB
10.2 MB
In fact, the total size of Lomelin.mx main page is 12.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.9 MB which makes up the majority of the site volume.
Potential reduce by 427.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 97.4 kB, which is 20% 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 427.7 kB or 88% of the original size.
Potential reduce by 218.9 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. Lomelin images are well optimized though.
Potential reduce by 906.9 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 906.9 kB or 68% of the original size.
Potential reduce by 262.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. Lomelin.mx needs all CSS files to be minified and compressed as it can save up to 262.3 kB or 86% of the original size.
Number of requests can be reduced by 86 (68%)
127
41
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lomelin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
lomelin.mx
2716 ms
bootstrap.css
106 ms
font-awesome.min.css
16 ms
bootstrap-ads.css
70 ms
normalize.css
72 ms
media-queries.css
73 ms
stylesheet.css
75 ms
prettyPhoto.css
98 ms
css
30 ms
css
45 ms
animate.css
137 ms
liquid-slider.css
139 ms
scaffold.css
143 ms
lytebox.css
144 ms
js
48 ms
jquery.js
235 ms
engine.js
170 ms
prototype.js
343 ms
scriptaculous.js
207 ms
lytebox.js
248 ms
BubbleTooltips.js
212 ms
application.js
242 ms
tablesort.js
278 ms
galleria.js
386 ms
lightbox.js
304 ms
jsapi
23 ms
jquery.prettyPhoto.js
362 ms
gmapez-2.5.js
362 ms
modernizr.custom.js
361 ms
prefixfree.min.js
374 ms
buttons.js
7 ms
fadeshow.js
420 ms
lightview.js
449 ms
lightview.css
417 ms
easyslider.css
421 ms
easySlider1.7.js
443 ms
jquery.min.js
35 ms
js
35 ms
jquery-1.10.2.min.js
544 ms
bootstrap.min.js
503 ms
jquery.easing.1.3.js
474 ms
jquery.touchSwipe.min.js
475 ms
jquery.liquid-slider-custom.min.js
532 ms
builder.js
165 ms
effects.js
246 ms
dragdrop.js
250 ms
controls.js
274 ms
slider.js
237 ms
sound.js
267 ms
maps
30 ms
arrow_up.png
153 ms
arrow_down.png
152 ms
analytics.js
45 ms
eugenia16_show.png
366 ms
logotipo.jpg
71 ms
8611.png
1143 ms
48519.png
1165 ms
63751.png
1115 ms
63985.png
1070 ms
logotipo_wn.png
85 ms
simple_captcha
174 ms
logotipo.png
174 ms
sombralogin.png
266 ms
inquilino_14.png
267 ms
responder.png
456 ms
telefono_12.png
365 ms
104_show.jpg
173 ms
av._toluca_104b_depto.202_escalera_show.jpg
173 ms
photo_4_show.jpg
207 ms
render1-880x495_show.jpg
208 ms
1_img_2924_show.jpg
208 ms
20151126_120238_show.jpg
363 ms
juan_cordero_47_patio_2_show.jpg
361 ms
sam_1404_show.jpg
362 ms
coscomate_111_patio_show.jpg
360 ms
wtc7_show.png
619 ms
laguna_de_terminos12_show.png
699 ms
laguna_de_terminos12_show.png
699 ms
laguna_de_terminos12_show.png
973 ms
laguna_de_terminos11_show.png
1026 ms
laguna_de_terminos12_show.png
1025 ms
palmas3_show.jpg
1025 ms
1_show.png
1164 ms
img_3097_show.jpg
1161 ms
bootstrap.css
545 ms
font-awesome.min.css
23 ms
bootstrap-ads.css
627 ms
normalize.css
971 ms
media-queries.css
1023 ms
stylesheet.css
1063 ms
prettyPhoto.css
1107 ms
css
33 ms
css
51 ms
collect
23 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
15 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
15 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
26 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
26 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
25 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
24 ms
fontawesome-webfont.woff
12 ms
glyphicons-halflings-regular.woff
1061 ms
arrow.png
957 ms
loading.gif
959 ms
widget_v2.135.js
56 ms
getAllAppDefault.esi
130 ms
__$$__stringtable_lang_es.js
24 ms
getSegment.php
13 ms
checkOAuth.esi
59 ms
t.dhj
96 ms
t.dhj
37 ms
x35248
477 ms
s-3271.xgi
79 ms
pixel
82 ms
hbpix
82 ms
275 ms
pixel
325 ms
269 ms
avatar_simple_visitor.png
205 ms
pixel
191 ms
xrefid.xgi
186 ms
pixel
140 ms
aL63HcygAAVYuCCsAAA==
27 ms
cm
52 ms
2981
50 ms
prev.png
72 ms
common.js
18 ms
util.js
19 ms
marker.js
19 ms
map.js
17 ms
poly.js
18 ms
topclose.png
71 ms
close_large.png
71 ms
close_small.png
73 ms
close_innertop.png
72 ms
loading.gif
73 ms
inner_slideshow_stop.png
79 ms
inner_prev.png
140 ms
inner_next.png
139 ms
next.png
141 ms
blank.gif
141 ms
lomelin.mx 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
Image elements do not have [alt] attributes
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.
lomelin.mx 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
lomelin.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Lomelin.mx 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 Lomelin.mx 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.
lomelin.mx
Open Graph description is not detected on the main page of Lomelin. 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: