senthia.com website review

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

The HTML itself could arrive about 1.7 s sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 1.7 s on a phone.

vtexassets.com costs a phone 1.4 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

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

Google Tag Manager costs a phone 474 ms of main-thread work and 320 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.

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

About 66 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.

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

Facebook costs a phone 282 ms of main-thread work and 280 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.

Your server takes 1.8 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 145 requests on a phone: scripts 1.6 MB (44), images 1.0 MB (44) and HTML 224 KiB (2). Under 2 MB keeps phones on slow connections fast.

b35957e0-cdf3-4595-8885-61132d5d564d___cc4d1e547a9c708b96f54 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).

3 images further down the page (632 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 11056d0b-77d0-4fbe-9131-e190860e82fc___56b6d19a34e3e4a79fe10 at 1,000 px wide, shown at 316 px. Resized copies would save about 13 KiB.

1 image (474 KiB) is 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 0.88 g of CO₂e: 105.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 buttons have no accessible name, so screen readers announce just “button”.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

3 images have no alt text, which hurts accessibility and image search.

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

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

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

Elements with visible text labels do not have matching accessible names. (7 elements).

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

There are 2 <h1> headlines (“Nuevos Favoritos” and “Favoritos”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 36 pages on senthia.com and 9 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.

There is no https://www.senthia.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.

https://www.senthia.com/urlHipervinculo is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.senthia.com/favoritos, https://www.senthia.com/urlHipervinculo, https://www.senthia.com/blogs and https://www.senthia.com/best-sellers use the same meta description. A description written for each page earns more clicks.

https://www.senthia.com/urlHipervinculo, https://www.senthia.com/blogs and https://www.senthia.com/best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.senthia.com/best-sellers took over 3 s to send its HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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: 4 customer or partner logos. 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 394 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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