Website review, no card needed

locatelcolombia.com logo

locatelcolombia.com website review

Visit site (opens in a new tab)Reviewed 28 October 202652 issues · 89 checks

This review found 52 issues worth fixing on locatelcolombia.com, 21 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s3.0 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.6 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
363 ms292 msMay 9Oct 24315 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026305 ms
May 16, 2026300 ms
May 23, 2026301 ms
May 30, 2026311 ms
Jun 6, 2026321 ms
Jun 13, 2026344 ms
Jun 20, 2026355 ms
Jun 27, 2026353 ms
Jul 4, 2026348 ms
Jul 11, 2026340 ms
Jul 18, 2026331 ms
Jul 25, 2026330 ms
Aug 1, 2026325 ms
Aug 8, 2026319 ms
Aug 15, 2026319 ms
Aug 22, 2026312 ms
Aug 29, 2026314 ms
Sep 5, 2026315 ms
Sep 12, 2026313 ms
Sep 19, 2026314 ms
Sep 26, 2026311 ms
Oct 3, 2026316 ms
Oct 10, 2026316 ms
Oct 17, 2026314 ms
Oct 24, 2026315 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of locatelcolombia.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. locatelcolombia.com at 0.4 s0.4 s
  2. locatelcolombia.com at 0.8 s0.8 s
  3. locatelcolombia.com at 1.1 s1.1 s
  4. locatelcolombia.com at 1.5 s1.5 s
  5. locatelcolombia.com at 1.9 s1.9 s
  6. locatelcolombia.com at 2.3 s2.3 s
  7. locatelcolombia.com at 2.6 s2.6 s
  8. locatelcolombia.com at 3.0 s3.0 s

Speed

9 to fix38
  • Reduce unused JavaScript

    3.9 s · 807 KiB

    About 807 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.7 s · 619 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (619 KiB).

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vtexassets.com and Facebook and others), adding 2.8 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 575 ms

    575 ms

    Google Tag Manager costs a phone 575 ms of main-thread work and 839 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • vtexassets.com adds 436 ms

    436 ms

    vtexassets.com costs a phone 436 ms of main-thread work and 1.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Legacy JavaScript

    500 ms · 56 KiB

    Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 73 KiB

    About 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    200 ms · 160 KiB

    14 images could be 160 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 71 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 19 ms

    19 ms

    Your server sent the HTML in 19 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.32

    0.32

    For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 28.4 s

    28.4 s

    The page becomes fully interactive after 28.4 s. Good is under 3.8 s.

  • First Contentful Paint: 6.3 s

    6.3 s

    The first text or image appears after 6.3 s on a phone. Good is under 1.8 s.

  • Speed Index: 10.9 s

    10.9 s

    Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.

  • Real-user INP: 308 ms

    308 ms

    Real visitors wait 308 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.226

    0.226

    The layout shifts by 0.226 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 303 ms

    303 ms

    Scripts block taps and scrolling for 303 ms in total while the page loads. Good is under 200 ms.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 305 ms to 315 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

2 to fix81
  • Page weight: 3.8 MB in 185 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 185 requests on a phone: scripts 2.4 MB (67), images 449 KiB (30) and other files 402 KiB (73). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    12397b95-8af6-4cfc-bf58-5fdbe12ae219___441d8dbc83f036bd7dcdf is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7888
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 19 tap targets too small

    19 tap targets are too small or too close together to hit reliably with a finger.

  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8555
  • Page is set to noindex

    The robots meta tag says “# Disallow all crawlers access to certain pages. User-agent…”: Google is told not to list this page at all.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (16 characters)

    Your title is only 16 characters: “Locatel Colombia”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (WebSite) but with 2 problems, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 31 internal links, 0 external

    The homepage links to 31 pages on locatelcolombia.com and 0 external pages.

4 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Encuentra los mejores productos de salud, dermocosmética, cuidado personal, maternidad, nutrición y equipos médicos.”.

  • Canonical URL set

    The canonical URL is https://www.locatelcolombia.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.locatelcolombia.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.locatelcolombia.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (145 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 3 pages without a title

    https://www.locatelcolombia.com/drogueria, https://www.locatelcolombia.com/cuidado-personal and https://www.locatelcolombia.com/dermocosmetica/facial have no <title>, so Google invents the link text in results.

  • 12 linked pages hidden from search

    https://www.locatelcolombia.com/dermocosmetica, https://www.locatelcolombia.com/dispositivos-medicos-en-casa, https://www.locatelcolombia.com/alimentos-nutricionales, https://www.locatelcolombia.com/maternidad-bebe, https://www.locatelcolombia.com/marketplace and https://www.locatelcolombia.com/marcas and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.locatelcolombia.com/drogueria, https://www.locatelcolombia.com/cuidado-personal and https://www.locatelcolombia.com/dermocosmetica/facial have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.locatelcolombia.com/drogueria/vitaminas, https://www.locatelcolombia.com/4728 and https://www.locatelcolombia.com/politicas-comerciales use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.locatelcolombia.com/drogueria, https://www.locatelcolombia.com/cuidado-personal, https://www.locatelcolombia.com/marcas, https://www.locatelcolombia.com/bonos-de-regalo, https://www.locatelcolombia.com/dermocosmetica/facial and https://www.locatelcolombia.com/politicas-comerciales have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.locatelcolombia.com/drogueria, https://www.locatelcolombia.com/cuidado-personal, https://www.locatelcolombia.com/alimentos-nutricionales, https://www.locatelcolombia.com/maternidad-bebe and https://www.locatelcolombia.com/marketplace took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 10071
  • 4 broken images

    4 images failed to load on a phone, for example https://df9xluswrtwog.cloudfront.net/ImagesRepo/MTMxNi0zMzAxLWxvY2F0ZWxjb191c3I1/6681/2026/OCTUBRE/Pop_Up_SuperSale_27Oct26.jpg?time=1793196059043.

  • 30 small tap targets

    30 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 200 words

    The homepage has only about 200 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 52 other companies contacted

    Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at locatelcolombia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on locatelcolombia.com, including 21 speed issues, 6 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25