Website review, no card needed
mariafilo.com.br website review
Visit site (opens in a new tab)Reviewed 2 November 202646 issues · 90 checks
This review found 46 issues worth fixing on mariafilo.com.br, 15 of them high impact, across 90 checks. The most urgent: mobile performance score: 44. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.9 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 250 ms |
| May 23, 2026 | 235 ms |
| May 30, 2026 | 219 ms |
| Jun 6, 2026 | 231 ms |
| Jun 13, 2026 | 229 ms |
| Jun 20, 2026 | 239 ms |
| Jun 27, 2026 | 261 ms |
| Jul 4, 2026 | 287 ms |
| Jul 11, 2026 | 343 ms |
| Jul 18, 2026 | 379 ms |
| Jul 25, 2026 | 407 ms |
| Aug 1, 2026 | 417 ms |
| Aug 8, 2026 | 425 ms |
| Aug 15, 2026 | 425 ms |
| Aug 22, 2026 | 414 ms |
| Aug 29, 2026 | 422 ms |
| Sep 5, 2026 | 476 ms |
| Sep 12, 2026 | 558 ms |
| Sep 19, 2026 | 597 ms |
| Sep 26, 2026 | 608 ms |
| Oct 3, 2026 | 594 ms |
| Oct 10, 2026 | 557 ms |
| Oct 17, 2026 | 461 ms |
| Oct 24, 2026 | 439 ms |
| Oct 31, 2026 | 420 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
Mobile performance score: 44
44/100Your mobile performance score is 44. 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.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
950 ms · 272 KiB3 images could be 272 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.3 MB and 1.0 s of main-thread time.
Render-blocking requests
900 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Use efficient cache lifetimes
796 KiB41 files are served with short cache lifetimes, so returning visitors download them again (796 KiB).
Reduce initial server response time
552 msReduce initial server response time. Google estimates savings of 552 ms on a phone.
Document request latency
550 msThe HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 340 ms. During a long task the page ignores taps.
Google Tag Manager adds 308 ms
308 msGoogle Tag Manager costs a phone 308 ms of main-thread work and 305 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.
1,772 HTML elements
The page has 1,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Other Google APIs/SDKs adds 118 ms
118 msOther Google APIs/SDKs costs a phone 118 ms of main-thread work and 328 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.
Server response: 652 ms
652 msYour server takes 652 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 70 KiBPolyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
90 KiB90 KiB could be saved by minifying JavaScript.
Reduce unused CSS
23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page.
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.
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.
Time to Interactive: 29.4 s
29.4 sThe page becomes fully interactive after 29.4 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user INP: 322 ms
322 msReal visitors wait 322 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 77% slower for real visitors
+77%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 250 ms to 420 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 879 ms
879 msReal visitors wait 879 ms for your server to start answering (75th percentile). Good is under 800 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (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.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.043
0.043The layout barely moves while loading (CLS 0.043, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 9.6 MB in 268 requests
9.6 MBYour homepage downloads 9.6 MB in 268 requests on a phone: media 3.6 MB (3), scripts 2.9 MB (99) and images 2.5 MB (41). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.72 g of CO₂e: 326.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
23 images without alt text
23 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail 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.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Maria Filó”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (41 characters)
Your meta description is only 41 characters: “Moda Feminina para Mulheres Protagonistas”. 70 to 160 characters is enough to sell the click.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
33 internal links, 0 external
The homepage links to 33 pages on mariafilo.com.br and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Maria Filó — sua loja de roupa feminina com elegância e protagonismo”.
Canonical URL set
The canonical URL is https://www.mariafilo.com.br/.
Structured data in place
Structured data found: OnlineStore.
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.mariafilo.com.br/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://mariafilo.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 (439 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://mariafilo.com.br/favoritos 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.
8 pages share a title
/, https://mariafilo.com.br/new-in, https://mariafilo.com.br/off-bazar, https://mariafilo.com.br/favoritos, https://mariafilo.com.br/verao-27 and https://mariafilo.com.br/semana-do-cliente-b and 2 others all use the title “Maria Filó”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://mariafilo.com.br/camisa-jeans-bolso-used-jeans-15-29053-0091/p and https://mariafilo.com.br/calca-jeans-wide-leg-recorte-wavy-jeans-15-29132-0091/p use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://mariafilo.com.br/new-in, https://mariafilo.com.br/roupas, https://mariafilo.com.br/acessorios, https://mariafilo.com.br/off-bazar, https://mariafilo.com.br/favoritos and https://mariafilo.com.br/verao-27 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://mariafilo.com.br/favoritos, https://mariafilo.com.br/sp-open-mf, https://mariafilo.com.br/camisa-jeans-bolso-used-jeans-15-29053-0091/p and https://mariafilo.com.br/calca-jeans-wide-leg-recorte-wavy-jeans-15-29132-0091/p 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.
7 pages slow to respond
https://mariafilo.com.br/new-in, https://mariafilo.com.br/roupas, https://mariafilo.com.br/acessorios, https://mariafilo.com.br/verao-27, https://mariafilo.com.br/semana-do-cliente-c and https://mariafilo.com.br/sp-open-mf and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
4 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.
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 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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_FAILED”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
22 of 25 tappable elements near the top are at least 24 px.
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.
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 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 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 319 words of copy
The homepage carries about 319 words of visible text.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
36 other companies contacted
Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 mariafilo.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
- Next.js
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on mariafilo.com.br, including 23 speed issues, 3 SEO issues and 5 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.