Website review, no card needed

afabula.com.br logo

afabula.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202652 issues · 92 checks

This review found 52 issues worth fixing on afabula.com.br, 20 of them high impact, across 92 checks. The most urgent: page weight: 21.8 MB in 345 requests. 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.9 s1.7 sAug 15Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20263.3 s
Aug 22, 20263.4 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.4 s
Sep 19, 20263.2 s
Sep 26, 20263.0 s
Oct 3, 20262.6 s
Oct 10, 20262.4 s
Oct 17, 20262.1 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
486 ms271 msAug 15Oct 24461 ms
Show as table
DateReal-visitor tap response (INP)
Aug 15, 2026296 ms
Aug 22, 2026320 ms
Aug 29, 2026379 ms
Sep 5, 2026455 ms
Sep 12, 2026461 ms
Sep 19, 2026451 ms
Sep 26, 2026445 ms
Oct 3, 2026443 ms
Oct 10, 2026442 ms
Oct 17, 2026450 ms
Oct 24, 2026461 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 afabula.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. afabula.com.br at 2.8 s2.8 s
  2. afabula.com.br at 5.6 s5.6 s
  3. afabula.com.br at 8.4 s8.4 s
  4. afabula.com.br at 11.2 s11.2 s
  5. afabula.com.br at 14.0 s14.0 s
  6. afabula.com.br at 16.8 s16.8 s
  7. afabula.com.br at 19.7 s19.7 s
  8. afabula.com.br at 22.5 s22.5 s

Speed

12 to fix38
  • Main-thread work: 10.2 s

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

  • Mobile performance score: 38

    38/100

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

  • 3,360 HTML elements

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

  • Improve image delivery

    3.1 MB

    10 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 1.5 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    1.1 MB

    119 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Render-blocking requests

    900 ms

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Google Tag Manager adds 359 ms

    359 ms

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

  • Facebook adds 312 ms

    312 ms

    Facebook costs a phone 312 ms of main-thread work and 280 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 336 ms. During a long task the page ignores taps.

  • Other Google APIs/SDKs adds 182 ms

    182 ms

    Other Google APIs/SDKs costs a phone 182 ms of main-thread work and 378 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

    88 KiB

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

  • Minify JavaScript

    80 KiB

    80 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    21 KiB

    About 21 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

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

  • Speed Index: 20.6 s

    20.6 s

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

  • Time to Interactive: 36.1 s

    36.1 s

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

  • Cumulative Layout Shift: 0.693

    0.693

    The layout shifts by 0.693 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 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 INP: 462 ms

    462 ms

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

  • Real-user CLS: 0.13

    0.13

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

  • Tap response (INP) got 48% slower for real visitors

    +48%

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

  • Real-user TTFB: 994 ms

    994 ms

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

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

    -39%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix26
  • Page weight: 21.8 MB in 345 requests

    21.8 MB

    Your homepage downloads 21.8 MB in 345 requests on a phone: media 14.0 MB (3), images 4.2 MB (110) and scripts 3.2 MB (113). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    2.3 MB

    6 images are downloaded at several times the size a phone draws them, for example selo_premio_empresa_campea_horizontal_cinza.png at 10,569 px wide, shown at 94 px. Resized copies would save about 2.3 MB.

  • 2 images over 500 KB

    2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.1 MB) 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.

  • An image on the first screen is lazy-loaded

    807b8039-2d3e-4333-b4e5-f75ae878b27f___744cc9300e71d4474f625 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images below the first screen load straight away

    2 images further down the page (71 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.17 g

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

Accessibility

7 to fixGoogle 8389
  • 94 buttons without a name

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

  • 5 tap targets too small

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

  • 15 images without alt text

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

  • All page content should be contained by landmarks (18 elements)

    All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

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

  • 47 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (6 characters)

    Your title is only 6 characters: “Fabula”. 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.

  • 28 internal links, 0 external

    The homepage links to 28 pages on afabula.com.br and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.afabula.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.afabula.com.br/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    3%

    A phone browser shows 487 words, but the HTML your server sends has only 15. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://afabula.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.

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

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://afabula.com.br/politicas/regulamento-e-promocoes 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://afabula.com.br/politicas/regulamento-e-promocoes all use the title “Fabula”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://afabula.com.br/smiley, https://afabula.com.br/tem-promo, https://afabula.com.br/promo-zumzum and https://afabula.com.br/politicas/regulamento-e-promocoes use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://afabula.com.br/smiley, https://afabula.com.br/tem-promo, https://afabula.com.br/promo-zumzum, https://afabula.com.br/meninos and https://afabula.com.br/meninas have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://afabula.com.br/smiley, https://afabula.com.br/tem-promo, https://afabula.com.br/promo-zumzum, https://afabula.com.br/politicas/regulamento-e-promocoes and https://afabula.com.br/meninos took over 3 s to send their HTML from our server.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    6 pages of 13 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is 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”.

  • 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

    119 of 141 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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 487 words of copy

    The homepage carries about 487 words of visible text.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 afabula.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 52 issues on afabula.com.br, including 23 speed issues, 4 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

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