Website review, no card needed
lelis.com.br website review
Visit site (opens in a new tab)Reviewed 28 October 202661 issues · 99 checks
This review found 61 issues worth fixing on lelis.com.br, 25 of them high impact, across 99 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
48FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 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.4 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 362 ms |
| May 16, 2026 | 353 ms |
| May 23, 2026 | 347 ms |
| May 30, 2026 | 346 ms |
| Jun 6, 2026 | 347 ms |
| Jun 13, 2026 | 357 ms |
| Jun 20, 2026 | 362 ms |
| Jun 27, 2026 | 353 ms |
| Jul 4, 2026 | 355 ms |
| Jul 11, 2026 | 350 ms |
| Jul 18, 2026 | 346 ms |
| Jul 25, 2026 | 355 ms |
| Aug 1, 2026 | 354 ms |
| Aug 8, 2026 | 347 ms |
| Aug 15, 2026 | 339 ms |
| Aug 22, 2026 | 331 ms |
| Aug 29, 2026 | 326 ms |
| Sep 5, 2026 | 336 ms |
| Sep 12, 2026 | 350 ms |
| Sep 19, 2026 | 361 ms |
| Sep 26, 2026 | 371 ms |
| Oct 3, 2026 | 369 ms |
| Oct 10, 2026 | 356 ms |
| Oct 17, 2026 | 339 ms |
| Oct 24, 2026 | 315 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.5 s
Speed
Use efficient cache lifetimes
6.4 s · 23.5 MB84 files are served with short cache lifetimes, so returning visitors download them again (23.5 MB).
Reduce unused JavaScript
12.5 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.5 s faster on a phone.
vtexassets.com adds 2.3 s
2.3 svtexassets.com costs a phone 2.3 s of main-thread work and 2.0 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.
Render-blocking requests
2.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 7.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 6
6/100Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,136 HTML elements
The page has 3,136 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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 4.8 MB and 4.9 s of main-thread time.
Improve image delivery
600 ms · 645 KiB29 images could be 645 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.
Reduce unused CSS
990 ms · 139 KiBAbout 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 990 ms faster on a phone.
Google Tag Manager adds 979 ms
979 msGoogle Tag Manager costs a phone 979 ms of main-thread work and 701 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.
Google CDN adds 716 ms
716 msGoogle CDN costs a phone 716 ms of main-thread work and 1.5 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.
Legacy JavaScript
400 ms · 108 KiBPolyfills for old browsers add 108 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 9 KiB9 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: 29 ms
29 msYour server sent the HTML in 29 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.
Real-user LCP: 5.9 s
5.9 sReal visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.64
0.64For real visitors the layout shifts by 0.64 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 48.2 s
48.2 sYour largest element takes 48.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 27.9 s
27.9 sVisually, the page fills in at 27.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.5 s
48.5 sThe page becomes fully interactive after 48.5 s. Good is under 3.8 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.633
0.633The layout shifts by 0.633 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Real-user INP: 399 ms
399 msReal visitors wait 399 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 888 ms
888 msReal visitors wait 888 ms for your server to start answering (75th percentile). Good is under 800 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 362 ms to 315 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 30.5 MB in 309 requests
30.5 MBYour homepage downloads 30.5 MB in 309 requests on a phone: media 22.4 MB (2), scripts 4.8 MB (117) and images 1.3 MB (72). Under 2 MB keeps phones on slow connections fast.
15 images below the first screen load straight away
15 images further down the page (618 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
38 KiB1 image is downloaded at several times the size a phone draws it, for example 578565-960-1313.5 at 960 px wide, shown at 171 px. Resized copies would save about 38 KiB.
About 8.6 g of CO₂ per visit
8.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.64 g of CO₂e: 1036.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
20 elements hidden from screen readers can still receive keyboard focus.
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 75 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 11 failed. 4 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.
Title is short (20 characters)
Your title is only 20 characters: “LE LIS | Loja Online”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (28 characters)
Your meta description is only 28 characters: “Compre na loja online LE LIS”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (ItemList, Organization, VideoObject and WebSite) but with 1 problem, 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.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
317 internal links, 23 external
The homepage links to 317 pages on lelis.com.br and 23 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.lelis.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.lelis.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.lelis.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (915 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without an H1
https://www.lelis.com.br/colecoes/novidades, https://www.lelis.com.br/colecoes/novidades-vestidos, https://www.lelis.com.br/colecoes/novidades-blusas, https://www.lelis.com.br/colecoes/novidades-tops-e-regatas-femininas, https://www.lelis.com.br/colecoes/novidades-calcas and https://www.lelis.com.br/colecoes/novidades-saias and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://www.lelis.com.br/colecoes/novidades-blusas, https://www.lelis.com.br/colecoes/novidades-tops-e-regatas-femininas, https://www.lelis.com.br/colecoes/novidades-calcas, https://www.lelis.com.br/colecoes/novidades-saias, https://www.lelis.com.br/colecoes/novidades-shorts-e-bermudas-femininas and https://www.lelis.com.br/colecoes/novidades-acessorios 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 197 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5321442&Ver=2&mid=9106da1f-982b-4999-8276-7d7d7dd69137&bo=1&sid=bf0fb460d31311f19514c57d16dcc1ab&vid=bf0fd330d31311f1bf079d76a6131d01&vids=1&msclkid=N&pi=918639831&lg=.
18 small tap targets
18 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Warning: No APP NAME ID is defined. Please configure it in the apps admin.”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 284 words of copy
The homepage carries about 284 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Mixpanel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 2 of them by other companies (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.
56 other companies contacted
Loading the homepage contacts 56 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 lelis.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
- Analytics
- Google Tag Manager | Mixpanel
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 61 issues on lelis.com.br, including 27 speed issues, 6 SEO issues and 6 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.