Website review, no card needed

bellasofi.com.br logo

bellasofi.com.br website review

Visit site (opens in a new tab)Reviewed 13 November 202636 issues · 81 checks

This review found 36 issues worth fixing on bellasofi.com.br, 14 of them high impact, across 81 checks. The most urgent: improve image delivery. 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

Full-page screenshot of bellasofi.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bellasofi.com.br at 0.7 s0.7 s
  2. bellasofi.com.br at 1.4 s1.4 s
  3. bellasofi.com.br at 2.1 s2.1 s
  4. bellasofi.com.br at 2.8 s2.8 s
  5. bellasofi.com.br at 3.5 s3.5 s
  6. bellasofi.com.br at 4.2 s4.2 s
  7. bellasofi.com.br at 4.9 s4.9 s
  8. bellasofi.com.br at 5.6 s5.6 s

Speed

11 to fix66
  • Improve image delivery

    3.7 s · 743 KiB

    5 images could be 743 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 672 KiB

    About 672 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 178 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (178 KiB).

  • 4,532 HTML elements

    The page has 4,532 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 (Google CDN, Google Tag Manager and Facebook and others), adding 2.2 MB and 828 ms of main-thread time.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

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

  • Google CDN adds 294 ms

    294 ms

    Google CDN costs a phone 294 ms of main-thread work and 743 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 Tag Manager adds 196 ms

    196 ms

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

  • Main-thread work: 2.0 s

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

  • mitiendanube.com adds 72 ms

    72 ms

    mitiendanube.com costs a phone 72 ms of main-thread work and 944 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

    150 ms · 21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    33 KiB

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

4 to fix61
  • Largest Contentful Paint: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vestido Infantil Luxo Circo Rosa - Palhacinha”.

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Cumulative Layout Shift: 0.095

    0.095

    The layout barely moves while loading (CLS 0.095, good is under 0.1).

  • Total Blocking Time: 182 ms

    182 ms

    Scripts block the page for only 182 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

4 to fix40
  • 1 image over 500 KB

    img-49816150-1682716398-c768663e4a9a52f46a70be190294bf871682 weighs 646 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    644 KiB

    1 image is downloaded at several times the size a phone draws it, for example img-49816150-1682716398-c768663e4a9a52f46a70be190294bf871682 at 4,500 px wide, shown at 80 px. Resized copies would save about 644 KiB.

  • Page weight: 2.8 MB in 45 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 45 requests on a phone: scripts 1.4 MB (17), images 829 KiB (9) and other files 359 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (646 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 0.8 g of CO₂ per visit

    0.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.8 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

7 to fixGoogle 8888
  • 22 text elements with low contrast

    22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (117 elements)

    All page content should be contained by landmarks: 117 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • Title is short (25 characters)

    Your title is only 25 characters: “Loja online de Bella Sofi”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://acdn-us.mitiendanube.com/stores/002/414/629/themes/common/sitemap.xml.gz, so Google discovers your pages only by following links.

  • 4 links crawlers can't follow

    4 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 set, so this is minor.

  • 88 internal links, 1 external

    The homepage links to 88 pages on bellasofi.com.br and 1 external page.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “Compre produtos de Moda e Vestuário por internet. Temos essenciais, clÁssicos e mais. Faça seu pedido e pague-o online.”.

  • One H1 headline

    Your main headline reads: “Bella Sofi”.

  • Canonical URL set

    The canonical URL is https://www.bellasofi.com.br/.

  • Structured data in place

    Structured data found: Organization, Product and WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,082 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.bellasofi.com.br/llms.txt (1 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 6 pages share 3 titles

    https://www.bellasofi.com.br/essenciais/conjunto-cjkgt and https://www.bellasofi.com.br/tematicos/conjunto all use the title “Comprar Conjunto em Bella Sofi”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages slow to respond

    https://www.bellasofi.com.br/essenciais, https://www.bellasofi.com.br/essenciais/trapezio1, https://www.bellasofi.com.br/classicos and https://www.bellasofi.com.br/classicos/vestidos-em-tule took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://www.bellasofi.com.br/.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    22 of 26 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 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 565 words of copy

    The homepage carries about 565 words of visible text.

2 checks passed
  • 25 short forms

    25 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before 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

    12

    Opening the homepage sets 12 cookies, 1 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 bellasofi.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 Analytics
Hosting
As273584 Linked Store Brasil Criacao E Desenvol De Software

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on bellasofi.com.br, including 15 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

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