Tools & Wizards About Us
lamesa.com.co screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

lamesa.com.co

Idetour

Page Load Speed

6.4 sec in total

First Response

508 ms

Resources Loaded

3 sec

Page Rendered

2.9 sec

lamesa.com.co screenshot

About Website

Visit lamesa.com.co now to see the best up-to-date Lamesa content and also check out these interesting facts you probably never knew about lamesa.com.co

Actividades de turismo muy cerca a Bogotá

Visit lamesa.com.co

Key Findings

We analyzed Lamesa.com.co page load time and found that the first response time was 508 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lamesa.com.co performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

lamesa.com.co

508 ms

wp-emoji-release.min.js

63 ms

style.min.css

126 ms

style.css

173 ms

base.css

174 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Lamesa.com.co, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (716 ms) belongs to the original domain Lamesa.com.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.3 kB (6%)

Content Size

4.2 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lamesa.com.co main page is 4.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. 75% 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 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.8 kB

  • Original 48.6 kB
  • After minification 47.2 kB
  • After compression 8.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 39.8 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 107.1 kB

  • Original 3.9 MB
  • After minification 3.8 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. Lamesa images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 67.3 kB

  • Original 116.9 kB
  • After minification 88.8 kB
  • After compression 49.6 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 67.3 kB or 58% of the original size.

CSS Optimization

-36%

Potential reduce by 41.1 kB

  • Original 114.2 kB
  • After minification 113.6 kB
  • After compression 73.2 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. Lamesa.com.co needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (50%)

Requests Now

56

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lamesa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lamesa.com.co

lamesa.com.co

508 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

63 ms

style.min.css

style.min.css

126 ms

style.css

style.css

173 ms

base.css

base.css

174 ms

layout.css

layout.css

268 ms

shortcodes.css

shortcodes.css

251 ms

animations.min.css

animations.min.css

203 ms

jquery.ui.all.css

jquery.ui.all.css

201 ms

prettyPhoto.css

prettyPhoto.css

239 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

240 ms

responsive.css

responsive.css

288 ms

style.css

style.css

284 ms

css

css

54 ms

css

css

54 ms

jquery.js

jquery.js

355 ms

jquery-migrate.min.js

jquery-migrate.min.js

312 ms

core.min.js

core.min.js

293 ms

widget.min.js

widget.min.js

292 ms

mouse.min.js

mouse.min.js

293 ms

sortable.min.js

sortable.min.js

294 ms

tabs.min.js

tabs.min.js

491 ms

accordion.min.js

accordion.min.js

492 ms

plugins.js

plugins.js

523 ms

menu.js

menu.js

492 ms

animations.min.js

animations.min.js

492 ms

jplayer.min.js

jplayer.min.js

494 ms

translate3d.js

translate3d.js

494 ms

scripts.js

scripts.js

509 ms

wp-embed.min.js

wp-embed.min.js

521 ms

gtm.js

gtm.js

295 ms

La-mesa.png

La-mesa.png

318 ms

DSC_0371.jpg

DSC_0371.jpg

343 ms

Caba%C3%B1a-Tunos-i.jpg

Caba%C3%B1a-Tunos-i.jpg

344 ms

finca-hotel-v%C3%ADa-san-joaqu%C3%ADn-i.jpg

finca-hotel-v%C3%ADa-san-joaqu%C3%ADn-i.jpg

318 ms

tocaima-i.jpg

tocaima-i.jpg

319 ms

FInca-Hotel-La-Mesa-i.jpg

FInca-Hotel-La-Mesa-i.jpg

317 ms

Finca-Hotel-Mesitas-de-El-Colegio-i.jpg

Finca-Hotel-Mesitas-de-El-Colegio-i.jpg

417 ms

cLUB-SAN-ANTONIO-DEL-tEQUENDAMA-i.jpg

cLUB-SAN-ANTONIO-DEL-tEQUENDAMA-i.jpg

418 ms

wellness-i.jpg

wellness-i.jpg

418 ms

DSC_0380.jpg

DSC_0380.jpg

417 ms

aventura.jpg

aventura.jpg

453 ms

Los-Tunos-i.jpg

Los-Tunos-i.jpg

418 ms

Escenario-Finca-Hist%C3%B3rica-ii.jpg

Escenario-Finca-Hist%C3%B3rica-ii.jpg

387 ms

Agroparque-ii.jpg

Agroparque-ii.jpg

451 ms

DSC_0366.jpg

DSC_0366.jpg

544 ms

el-arco%C3%ADris-del-i.jpg

el-arco%C3%ADris-del-i.jpg

486 ms

Avistamiento-de-Aves-Los-Tunos-i.jpg

Avistamiento-de-Aves-Los-Tunos-i.jpg

544 ms

Tour-Privado-Los-Tunos-i.jpg

Tour-Privado-Los-Tunos-i.jpg

485 ms

Salto-de-Las-Monjas-i-1.jpg

Salto-de-Las-Monjas-i-1.jpg

483 ms

DSC_7611.jpg

DSC_7611.jpg

544 ms

tour-de-caf%C3%A9-el-Caf%C3%A9-de-Colombia-en-el-Siglo-XIX-i.jpg

tour-de-caf%C3%A9-el-Caf%C3%A9-de-Colombia-en-el-Siglo-XIX-i.jpg

560 ms

Historia-de-amor-frances-en-la-tierra-del-caf%C3%A9-i.jpg

Historia-de-amor-frances-en-la-tierra-del-caf%C3%A9-i.jpg

574 ms

Caf%C3%A9-con-Aroma-de-Mujer2i.jpg

Caf%C3%A9-con-Aroma-de-Mujer2i.jpg

574 ms

El-caf%C3%A9-de-la-monta%C3%B1a-i.jpg

El-caf%C3%A9-de-la-monta%C3%B1a-i.jpg

716 ms

box_shadow_button.png

box_shadow_button.png

603 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

165 ms

ZXuke1cDvLCKLDcimxB44_lr.ttf

ZXuke1cDvLCKLDcimxB44_lr.ttf

179 ms

mfn-icons.woff

mfn-icons.woff

512 ms

box_shadow.png

box_shadow.png

578 ms

Accessibility Review

lamesa.com.co accessibility score

74

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

Links do not have a discernible name

High

<object> elements do not have alternate text

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

lamesa.com.co best practices score

67

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lamesa.com.co SEO score

84

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

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

High

Tap targets are not sized appropriately

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document uses plugins

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 Lamesa.com.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 Lamesa.com.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.

Social Sharing Optimization

lamesa.com.co

Open Graph description is not detected on the main page of Lamesa. 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: