Website review, no card needed

distribeaute.com logo

distribeaute.com website review

Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 73 checks

This review found 31 issues worth fixing on distribeaute.com, 12 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.9 sJul 25Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 20263.1 s
Aug 1, 20262.6 s
Aug 29, 20263.2 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20262.8 s
Sep 26, 20262.6 s
Oct 3, 20262.4 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
233 ms174 msSep 12Oct 17181 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 2026216 ms
Sep 19, 2026216 ms
Sep 26, 2026219 ms
Oct 3, 2026220 ms
Oct 10, 2026226 ms
Oct 17, 2026181 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of distribeaute.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. distribeaute.com at 0.6 s0.6 s
  2. distribeaute.com at 1.2 s1.2 s
  3. distribeaute.com at 1.8 s1.8 s
  4. distribeaute.com at 2.4 s2.4 s
  5. distribeaute.com at 3.0 s3.0 s
  6. distribeaute.com at 3.7 s3.7 s
  7. distribeaute.com at 4.3 s4.3 s
  8. distribeaute.com at 4.9 s4.9 s

Speed

6 to fix65
  • Reduce unused JavaScript

    1.4 s · 286 KiB

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

  • Improve image delivery

    11.8 MB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (supabase.co and Cloudinary), adding 12.4 MB and 0 ms of main-thread time.

  • Cloudinary adds 0 ms

    0 ms

    Cloudinary costs a phone 0 ms of main-thread work and 12.3 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.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.5 s

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

  • 7 long tasks on the main thread

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

  • Render-blocking requests

    200 ms

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

  • Legacy JavaScript

    100 ms · 14 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 9.0 s

    9.0 s

    Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Distribución de Belleza”. Most of its time is element render delay (3.8 s).

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 181 ms

    181 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 568 ms

    568 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Total Blocking Time: 163 ms

    163 ms

    Scripts block the page for only 163 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 13.4 MB in 66 requests

    13.4 MB

    Your homepage downloads 13.4 MB in 66 requests on a phone: images 12.7 MB (19), scripts 523 KiB (18) and fonts 86 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    3.7 MB

    7 images are downloaded at several times the size a phone draws them, for example EssenceKV_Gris_1920x1080_n9xzce.png at 1,920 px wide, shown at 356 px. Resized copies would save about 3.7 MB.

  • 11 images in older formats

    11 images (8.8 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.

  • 10 images below the first screen load straight away

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

  • About 3.8 g of CO₂ per visit

    3.79 g

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

Accessibility

1 to fix94
  • 2 buttons without a name

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

1 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

SEO

5 to fixGoogle 10081
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.distribeaute.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at distribeaute.com/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 21 internal links, 4 external

    The homepage links to 21 pages on distribeaute.com and 4 external pages.

3 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Connecting leading beauty and fragrance brands with consumers through exceptional experiences.”.

  • One H1 headline

    Your main headline reads: “Distribución de Belleza”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Distribeaute - Beauty Distribution”.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    17%

    A phone browser shows 918 words, but the HTML your server sends has only 159. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No Organization structured data

    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.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 16 pages share a title

    /, https://www.distribeaute.com/brands, https://www.distribeaute.com/colombia, https://www.distribeaute.com/panama, https://www.distribeaute.com/costa-rica and https://www.distribeaute.com/contact and 10 others all use the title “Distribeaute - Beauty Distribution”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.distribeaute.com/brands, https://www.distribeaute.com/colombia, https://www.distribeaute.com/panama, https://www.distribeaute.com/costa-rica, https://www.distribeaute.com/contact and https://www.distribeaute.com/categories/perfumery and 9 others use the same meta description. A description written for each page earns more clicks.

  • 11 pages with very little text

    https://www.distribeaute.com/brands, https://www.distribeaute.com/colombia, https://www.distribeaute.com/panama, https://www.distribeaute.com/costa-rica, https://www.distribeaute.com/categories/perfumery and https://www.distribeaute.com/categories/makeup and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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.

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

  • About 918 words of copy

    The homepage carries about 918 words of visible text.

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 1 phone link and 4 email links.

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at distribeaute.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
v0.app
Framework
Next.js
Hosting
Vercel

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on distribeaute.com, including 11 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25