gestababyoficial.com.br website review

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

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

4 images could be 265 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

67 KiB could be saved by minifying JavaScript.

About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

Google CDN costs a phone 83 ms of main-thread work and 352 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.

5 third-party services load with your homepage (Google CDN, Cloudflare CDN and Other Google APIs/SDKs and others), adding 440 KiB and 86 ms of main-thread time.

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

9 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

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

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.

7 images (632 KiB) are 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.

2 images are downloaded at several times the size a phone draws them, for example bbbc92f9fe93dc21309c2579aaf15aba8f8ed23b.jpg at 1,600 px wide, shown at 359 px. Resized copies would save about 123 KiB.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

11 visible links have no text or label, so screen readers cannot say where they go.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

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

Your title is only 10 characters: “Gesta Baby”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at http://www.gestababyoficial.com.br/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at gestababyoficial.com.br/robots.txt, the first file search crawlers ask for.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 41 pages on gestababyoficial.com.br and 10 external pages.

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.

There is no https://www.gestababyoficial.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.

Your homepage links to https://www.gestababyoficial.com.br/novo/servico/consultoria-de-amamentacao and https://www.gestababyoficial.com.br/numbers-matching.html, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.gestababyoficial.com.br/parceiros, https://www.gestababyoficial.com.br/memorias, https://www.gestababyoficial.com.br/contato, https://www.gestababyoficial.com.br/servicos and https://www.gestababyoficial.com.br/cursos have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.gestababyoficial.com.br/contato has 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.

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

3 errors were logged to the browser console while the page loaded, for example “require is not defined”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 221 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.