Website review, no card needed

loccitaneaubresil.com logo

loccitaneaubresil.com website review

Visit site (opens in a new tab)Reviewed 30 October 202655 issues · 92 checks

This review found 55 issues worth fixing on loccitaneaubresil.com, 24 of them high impact, across 92 checks. The most urgent: improve image delivery. 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.8 s1.9 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.2 s
Jul 11, 20263.0 s
Jul 18, 20262.8 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
675 ms189 msMay 9Oct 24258 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026531 ms
May 16, 2026569 ms
May 23, 2026597 ms
May 30, 2026619 ms
Jun 6, 2026586 ms
Jun 13, 2026525 ms
Jun 20, 2026487 ms
Jun 27, 2026445 ms
Jul 4, 2026433 ms
Jul 11, 2026414 ms
Jul 18, 2026377 ms
Jul 25, 2026339 ms
Aug 1, 2026305 ms
Aug 8, 2026288 ms
Aug 15, 2026286 ms
Aug 22, 2026286 ms
Aug 29, 2026277 ms
Sep 5, 2026269 ms
Sep 12, 2026256 ms
Sep 19, 2026246 ms
Sep 26, 2026245 ms
Oct 3, 2026249 ms
Oct 10, 2026254 ms
Oct 17, 2026256 ms
Oct 24, 2026258 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 loccitaneaubresil.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. loccitaneaubresil.com at 1.1 s1.1 s
  2. loccitaneaubresil.com at 2.2 s2.2 s
  3. loccitaneaubresil.com at 3.3 s3.3 s
  4. loccitaneaubresil.com at 4.4 s4.4 s
  5. loccitaneaubresil.com at 5.5 s5.5 s
  6. loccitaneaubresil.com at 6.6 s6.6 s
  7. loccitaneaubresil.com at 7.8 s7.8 s
  8. loccitaneaubresil.com at 8.9 s8.9 s

Speed

13 to fix38
  • Improve image delivery

    4.0 s · 2.5 MB

    27 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 6.0 s

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

  • 5,113 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Dynatrace and goadopt.io and others), adding 1.5 MB and 2.1 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 544 KiB

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

  • Use efficient cache lifetimes

    500 ms · 753 KiB

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

  • Google Tag Manager adds 850 ms

    850 ms

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

  • 20 long tasks on the main thread

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

  • Dynatrace adds 680 ms

    680 ms

    Dynatrace costs a phone 680 ms of main-thread work and 123 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.

  • Reduce unused CSS

    450 ms · 138 KiB

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

  • goadopt.io adds 259 ms

    259 ms

    goadopt.io costs a phone 259 ms of main-thread work and 276 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.

  • Legacy JavaScript

    35 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 36.2 s

    36.2 s

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

  • Speed Index: 22.9 s

    22.9 s

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

  • Time to Interactive: 44.5 s

    44.5 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 423 ms

    423 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

4 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 53% faster for real visitors

    -53%

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

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

    -35%

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

  • Cumulative Layout Shift: 0.031

    0.031

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

Images and page weight

5 to fix28
  • Page weight: 26.8 MB in 245 requests

    26.8 MB

    Your homepage downloads 26.8 MB in 245 requests on a phone: media 13.4 MB (6), images 11.6 MB (184) and scripts 1.5 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 8.1 MB together. On a phone connection a single image that size takes seconds.

  • 15 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (7.4 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.

  • 2 images far larger than shown

    76 KiB

    2 images are downloaded at several times the size a phone draws them, for example 10_HP-pudim-(com-cta)-1500x640.webp at 1,500 px wide, shown at 390 px. Resized copies would save about 76 KiB.

  • About 7.6 g of CO₂ per visit

    7.59 g

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

Accessibility

13 to fixGoogle 7383
  • 2 buttons without a name

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

  • 38 tap targets too small

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

  • 16 text elements with low contrast

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

  • Form elements should have a visible label (3 elements)

    Form elements should have a visible label: 3 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

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

  • 15 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    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.

  • 13 links without text

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

  • 5 form fields without a label

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

  • Alternative text of images should not be repeated as text (12 elements)

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8579
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “L'Occitane au Brésil | Brasilidade efervescente com um toque Francês”.

  • No structured data

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

  • Meta description is long (262 characters)

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

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 351 internal links, 4 external

    The homepage links to 351 pages on loccitaneaubresil.com and 4 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “DESCUBRA POR”.

  • Canonical URL set

    The canonical URL is https://br.loccitaneaubresil.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://br.loccitaneaubresil.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://br.loccitaneaubresil.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,204 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://br.loccitaneaubresil.com/pt-br/Homepage 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.

  • 2 pages share a title

    / and https://br.loccitaneaubresil.com/pt-br/Homepage all use the title “L'Occitane au Brésil | Brasilidade efervescente com um toque Francês”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://br.loccitaneaubresil.com/pt-br/fretegratisexclusivo.html, https://br.loccitaneaubresil.com/pt-br/atendimentoaoconsumidor.html, https://br.loccitaneaubresil.com/pt-br/Localizador-de-lojas, https://br.loccitaneaubresil.com/pt-br/presentes-masculinos.html and https://br.loccitaneaubresil.com/pt-br/combo-caju-esfoliante-hidratante-e-serum-gotas/424852.html use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9687
  • 91 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • Thin social proof

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

  • 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 1,918 words of copy

    The homepage carries about 1,918 words of visible text.

3 checks passed
  • 5 short forms

    5 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 17 cookies set on arrival

    17

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

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 loccitaneaubresil.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

Analytics
Google Tag Manager
Hosting
CSC

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on loccitaneaubresil.com, including 23 speed issues, 5 SEO issues and 3 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