emo.com.co website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user TTFB: 2.3 s

  2.3 s

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

• Real-user LCP: 2.9 s

  2.9 s

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

• Real-user FCP: 2.8 s

  2.8 s

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

• Tap response (INP) held steady for real visitors

  +3%

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

• Page weight: 7.8 MB

  7.8 MB

  Your homepage downloads 7.8 MB on a phone, 5.8 MB of it images (74%). Under 2 MB keeps phones on slow connections fast.

• 40 images in older formats

  40 images (3.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (5)

• 30 images below the first screen load straight away

  30 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 2.2 g of CO₂ per visit

  2.22 g

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

• [role="img"] and [role="image"] elements must have alternative text (15 elements)

  [role="img"] and [role="image"] elements must have alternative text: 15 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 2 tap targets too small

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

  Elements (2)

• Hidden but focusable

  1 element hidden from screen readers can still receive keyboard focus.

  Elements (1)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

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

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

  Elements (3)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 12 links without text

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

  Elements (3)

• Headings skip levels

  Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  View sourceElements (2)

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

• No H1 headline

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

• Title is short (27 characters)

  Your title is only 27 characters: “Inicio - Materiales EMO SAS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 96 internal links, 12 external

  The homepage links to 96 pages on emo.com.co and 12 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• No llms.txt

  There is no /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.

• Opted out of AI training for 5 crawlers

  robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

• Your server turned our page checks away

  15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  emo.com.co has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

• Thin social proof

  Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

• 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 185 words

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

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

• No DMARC policy

  emo.com.co has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• Email authentication score: 45/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

• 23 cookies set on arrival

  23

  Opening the homepage sets 23 cookies, 1 of them by other companies (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.

• 16 other companies contacted

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