lummia.com.co website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

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

The page has 4,127 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (heatmap.com, Shopify and TikTok and others), adding 1.2 MB and 1.3 s of main-thread time.

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

About 425 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

heatmap.com costs a phone 285 ms of main-thread work and 93 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.

Shopify costs a phone 214 ms of main-thread work and 372 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.

Klaviyo costs a phone 192 ms of main-thread work and 315 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.

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

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

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Modelo con LummiSkin Pro morado”.

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

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

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

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

Your homepage downloads 4.6 MB in 448 requests on a phone: scripts 1.5 MB (104), other files 1.4 MB (290) and images 967 KiB (34). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example cm-lsm-bar-device.webp at 240 px wide, shown at 53 px. Resized copies would save about 55 KiB.

5 images (472 KiB) 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.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 4 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 on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 318 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 83 pages on lummia.com.co and 13 external pages.

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.

https://www.lummia.com.co/products/lummiairpro declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.lummia.com.co/products/lummiairpro all use the title “Lummia Colombia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lummia.com.co/collections/frontpage, https://www.lummia.com.co/collections/depilacion, https://www.lummia.com.co/collections/facial, https://www.lummia.com.co/collections/hair, https://www.lummia.com.co/pages/modo-de-uso-1 and https://www.lummia.com.co/pages/pushdaddy-faq-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lummia.com.co/collections and https://www.lummia.com.co/products/lummiairpro use the same meta description. A description written for each page earns more clicks.

https://www.lummia.com.co/products/lummiskin-pro, https://www.lummia.com.co/products/lummiair, https://www.lummia.com.co/products/lummimask, https://www.lummia.com.co/products/lummiwave, https://www.lummia.com.co/products/difusor-lummiair and https://www.lummia.com.co/pages/modo-de-uso-1 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

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

Social proof on the homepage: 155 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 744 words of visible text.

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

Opening the homepage sets 38 cookies, 4 of them by other companies (measured from a US location before any click).

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.

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