Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lomelin.mx

Lomelín

Page Load Speed

8.4 sec in total

First Response

2.7 sec

Resources Loaded

4.9 sec

Page Rendered

800 ms

lomelin.mx screenshot

About Website

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.mx

Key Findings

We 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.

Performance Metrics

lomelin.mx performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

lomelin.mx

2716 ms

bootstrap.css

106 ms

font-awesome.min.css

16 ms

bootstrap-ads.css

70 ms

normalize.css

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 Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (15%)

Content Size

12.0 MB

After Optimization

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.

HTML Optimization

-88%

Potential reduce by 427.7 kB

  • Original 488.5 kB
  • After minification 391.2 kB
  • After compression 60.9 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.

Image Optimization

-2%

Potential reduce by 218.9 kB

  • Original 9.9 MB
  • After minification 9.7 MB

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.

JavaScript Optimization

-68%

Potential reduce by 906.9 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 424.3 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.

CSS Optimization

-86%

Potential reduce by 262.3 kB

  • Original 304.2 kB
  • After minification 245.9 kB
  • After compression 41.9 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.

Requests Breakdown

Number of requests can be reduced by 86 (68%)

Requests Now

127

After Optimization

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.

Accessibility Review

lomelin.mx accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lomelin.mx best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lomelin.mx SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    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.

Social Sharing Optimization

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: