republiccosmetics.com website review

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

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

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

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

8 third-party services load with your homepage (loox.io, rebuyengine.com and vitals.app and others), adding 1.4 MB and 1.4 s of main-thread time.

loox.io costs a phone 715 ms of main-thread work and 27 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.

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

64 KiB could be saved by minifying JavaScript.

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

rebuyengine.com costs a phone 215 ms of main-thread work and 330 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 185 ms of main-thread work and 620 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 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

9 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 208 requests on a phone: scripts 1.5 MB (101), other files 741 KiB (82) and images 205 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

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

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

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

Your title is 80 characters, so Google will cut it off around 60: “Maquillaje, belleza y cuidado personal | Republic Cosmetics – REPUBLIC COSMETICS”.

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

The homepage links to 263 pages on republiccosmetics.com and 0 external pages.

Your Organization JSON-LD is missing logo, 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.

https://republiccosmetics.com/collections/pestanas-multimarca-2025, https://republiccosmetics.com/collections/perfumes-y-fragancias-2025, https://republiccosmetics.com/collections/lanzamientos-yuya and https://republiccosmetics.com/collections/labiales-liquidos-yuya have no meta description, so Google writes the search snippet from whatever text it finds.

https://republiccosmetics.com/collections/cabello, https://republiccosmetics.com/collections/rostro-1, https://republiccosmetics.com/collections/ojos-1, https://republiccosmetics.com/collections/pestanas-multimarca-2025, https://republiccosmetics.com/collections/labios-1 and https://republiccosmetics.com/collections/unas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “The Content Security Policy 'frame-ancestors 'self' https://onlive.site ' was delivered via a <meta> element outside th…”.

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

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.

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

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 1,329 words of visible text.

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

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