tania.co website review

325 files are served with short cache lifetimes, so returning visitors download them again (40.7 MB).

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

vtex.com.br costs a phone 1.8 s of main-thread work and 87 KiB 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 29 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (vtex.com.br, Google Tag Manager and YouTube and others), adding 8.6 MB and 4.2 s of main-thread time.

16 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

YouTube costs a phone 850 ms of main-thread work and 974 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.

Google Tag Manager costs a phone 864 ms of main-thread work and 537 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 160 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.

About 826 KiB of JavaScript is downloaded but never used on this page.

vteximg.com.br costs a phone 50 ms of main-thread work and 6.7 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

7 KiB could be saved by minifying JavaScript.

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.

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 visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 50.0 MB in 599 requests on a phone: media 38.8 MB (5), images 8.4 MB (280) and scripts 2.0 MB (71). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example e0a4587f-2e88-4918-8b7f-86e893f8a029___1fb6d2f8a04da0f5f3b46 at 1,024 px wide, shown at 42 px. Resized copies would save about 687 KiB.

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

2 images (182 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 14.18 g of CO₂e: 1702.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

2 dropdowns have no label.

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

9 elements hidden from screen readers can still receive keyboard focus.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 20 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.

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

82 links have no real href, so search engines can't follow them.

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

The homepage links to 235 pages on tania.co and 17 external pages.

There is no https://www.tania.co/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.tania.co/bControl and https://www.tania.co/es/176 all use the title “Ropa Interior, pijamas y más | Tania”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tania.co/esencial, https://www.tania.co/bControl and https://www.tania.co/es/176 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tania.co/bControl, whose canonical is https://www.tania.co/bcontrol. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tania.co/esencial, https://www.tania.co/romantica, https://www.tania.co/bControl, https://www.tania.co/es/belleza, https://www.tania.co/es/ropa-interior and https://www.tania.co/es/ropa-interior/brasieres and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

8 images failed to load on a phone, for example https://www.tania.co/.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Event name is not defined”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 861 words of visible text.

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

Opening the homepage sets 19 cookies, 1 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.