Website review, no card needed
duloren.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202657 issues · 95 checks
This review found 57 issues worth fixing on duloren.com.br, 26 of them high impact, across 95 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 311 ms |
| May 23, 2026 | 311 ms |
| May 30, 2026 | 321 ms |
| Jun 6, 2026 | 322 ms |
| Jun 13, 2026 | 325 ms |
| Jun 20, 2026 | 329 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 328 ms |
| Jul 11, 2026 | 314 ms |
| Jul 18, 2026 | 303 ms |
| Jul 25, 2026 | 287 ms |
| Aug 1, 2026 | 275 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 266 ms |
| Aug 29, 2026 | 261 ms |
| Sep 5, 2026 | 261 ms |
| Sep 12, 2026 | 259 ms |
| Sep 19, 2026 | 263 ms |
| Sep 26, 2026 | 263 ms |
| Oct 3, 2026 | 267 ms |
| Oct 10, 2026 | 268 ms |
| Oct 17, 2026 | 268 ms |
| Oct 24, 2026 | 268 ms |
| Oct 31, 2026 | 264 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
How it loaded on a phone
1.6 s
3.1 s
4.7 s
6.2 s
7.8 s
9.3 s
10.9 s
12.4 s
Speed
Use efficient cache lifetimes
1.8 s · 916 KiB25 files are served with short cache lifetimes, so returning visitors download them again (916 KiB).
Render-blocking requests
2.0 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
vtexassets.com adds 1.6 s
1.6 svtexassets.com costs a phone 1.6 s of main-thread work and 3.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.
Reduce unused JavaScript
1.2 s · 663 KiBAbout 663 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 5.0 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 (vtexassets.com, Facebook and ContentSquare and others), adding 4.2 MB and 2.8 s of main-thread time.
Improve image delivery
600 ms · 291 KiB4 images could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 534 ms. During a long task the page ignores taps.
Legacy JavaScript
350 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused CSS
310 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Facebook adds 301 ms
301 msFacebook costs a phone 301 ms of main-thread work and 229 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.
Minify JavaScript
150 ms · 4 KiB4 KiB could be saved by minifying JavaScript.
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: 25 ms
25 msYour server sent the HTML in 25 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: 18.2 s
18.2 sYour largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday”.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 205 ms
205 msReal visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 311 ms to 264 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 179 requests
5.2 MBYour homepage downloads 5.2 MB in 179 requests on a phone: scripts 1.9 MB (56), fonts 1.4 MB (6) and images 1.3 MB (38). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
435 KiB2 images are downloaded at several times the size a phone draws them, for example 42d527ad-3ca6-41ae-a230-abb29ccc3758___f1dd85f432b4b5f4c8972 at 2,000 px wide, shown at 390 px. Resized copies would save about 435 KiB.
1 image in older formats
1 image (175 KiB) is 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.
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
ARIA attributes must conform to valid values (8 elements)
ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
13 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (12 elements)
Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.
Positive tabindex
6 elements have a tabindex above 0, which scrambles the keyboard order.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 14 failed. 2 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.
Structured data has 2 problems
Structured data found (WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
109 internal links, 8 external
The homepage links to 109 pages on duloren.com.br and 8 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Encontre a lingerie perfeita! Ampla variedade de sutiãs, calcinhas, modeladores, bodies e pijamas, com os melhores preç…”.
Title: 51 characters
Your title is a healthy 51 characters: “Lingeries para todas as ocasiões | Duloren Lingerie”.
Canonical URL set
The canonical URL is https://www.duloren.com.br/.
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://www.duloren.com.br/sitemap.xml.
AI search readiness
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.duloren.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.
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 (298 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.duloren.com.br/sutias and https://www.duloren.com.br/plus-size have no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.duloren.com.br/545 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.duloren.com.br/institucional all use the title “Lingeries para todas as ocasiões | Duloren Lingerie”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.duloren.com.br/sutias and https://www.duloren.com.br/plus-size have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://www.duloren.com.br/lingeries-lancamento, https://www.duloren.com.br/calcinhas, https://www.duloren.com.br/body, https://www.duloren.com.br/modeladores, https://www.duloren.com.br/pijamas and https://www.duloren.com.br/545 and 7 others use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://www.duloren.com.br/lingeries-lancamento, https://www.duloren.com.br/sutias, https://www.duloren.com.br/plus-size, https://www.duloren.com.br/kits-e-conjuntos, https://www.duloren.com.br/lingeries-selecionadas and https://www.duloren.com.br/black-friday-banner-tv and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://www.duloren.com.br/body, https://www.duloren.com.br/modeladores, https://www.duloren.com.br/plus-size, https://www.duloren.com.br/kits-e-conjuntos, https://www.duloren.com.br/lingeries-selecionadas and https://www.duloren.com.br/black-friday-banner-tv and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 61 found) and read each the way a search engine does.
2 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.
Best practices
11 small tap targets
11 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
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.
Only about 188 words
The homepage has only about 188 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 4 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
35 other companies contacted
Loading the homepage contacts 35 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 duloren.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
- Framework
- React
- Hosting
- Oracle Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on duloren.com.br, including 23 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.