Website review, no card needed
elle.com.br website review
Visit site (opens in a new tab)Reviewed 3 November 202651 issues · 91 checks
This review found 51 issues worth fixing on elle.com.br, 20 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 169 ms |
| May 23, 2026 | 169 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 174 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 186 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 199 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 218 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 220 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 232 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 238 ms |
| Oct 24, 2026 | 238 ms |
| Oct 31, 2026 | 230 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
Speed
Use efficient cache lifetimes
12.5 s · 5.3 MB121 files are served with short cache lifetimes, so returning visitors download them again (5.3 MB).
Reduce unused JavaScript
3.0 s · 879 KiBAbout 879 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Google/Doubleclick Ads adds 1.1 s
1.1 sGoogle/Doubleclick Ads costs a phone 1.1 s of main-thread work and 1.5 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.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 2.9 MB and 2.7 s of main-thread time.
Google Tag Manager adds 804 ms
804 msGoogle Tag Manager costs a phone 804 ms of main-thread work and 769 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.
Render-blocking requests
350 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Facebook adds 310 ms
310 msFacebook costs a phone 310 ms of main-thread work and 255 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 323 ms. During a long task the page ignores taps.
Improve image delivery
261 KiB9 images could be 261 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
2 KiB2 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 26.1 s
26.1 sYour largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “calcas para trabalho 30out26 cherifaakili”.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.1 s
36.1 sThe page becomes fully interactive after 36.1 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user INP: 273 ms
273 msReal visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 169 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 876 ms
876 msReal visitors wait 876 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.106
0.106The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 7.6 MB in 612 requests
7.6 MBYour homepage downloads 7.6 MB in 612 requests on a phone: images 4.4 MB (170), scripts 2.3 MB (67) and other files 425 KiB (293). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
22 images in older formats
22 images (3.7 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.
17 images below the first screen load straight away
17 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
113 KiB2 images are downloaded at several times the size a phone draws them, for example receitas-para-um-jantar-leve-2-620x840.jpeg at 620 px wide, shown at 108 px. Resized copies would save about 113 KiB.
About 2.2 g of CO₂ per visit
2.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.15 g of CO₂e: 258.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (72 elements)
All page content should be contained by landmarks: 72 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, 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.
97 internal links, 28 external
The homepage links to 97 pages on elle.com.br and 28 external pages.
6 checks passed
Meta description: 124 characters
Your meta description is 124 characters: “Um olhar sobre a moda que vai além das tendências, além das novidades mais quentes nas áreas de beleza, cultura e lifes…”.
Title: 33 characters
Your title is a healthy 33 characters: “ELLE Brasil - A moda em movimento”.
Canonical URL set
The canonical URL is https://elle.com.br/.
Structured data in place
Structured data found: Organization.
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://elle.com.br/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://elle.com.br/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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,407 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://elle.com.br/elle-view, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://elle.com.br/tag/horoscopo is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://elle.com.br/moda, https://elle.com.br/beleza, https://elle.com.br/cultura, https://elle.com.br/sociedade, https://elle.com.br/elle-decoration and https://elle.com.br/lifestyle and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://elle.com.br/elleview has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
52 third-party cookies
52 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
24 small tap targets
24 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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,192 words of copy
The homepage carries about 1,192 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 elle.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on elle.com.br, including 22 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.