Website review, no card needed

phoenixbaby.com.br logo

phoenixbaby.com.br website review

Visit site (opens in a new tab)Reviewed 16 November 202644 issues · 75 checks

This review found 44 issues worth fixing on phoenixbaby.com.br, 21 of them high impact, across 75 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

Real-visitor load time (LCP)75th percentile, phones
7.3 s4.8 sMay 30Nov 145.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.4 s
Jun 6, 20266.3 s
Jun 13, 20266.4 s
Jun 20, 20266.6 s
Jun 27, 20266.5 s
Jul 4, 20266.4 s
Jul 11, 20266.2 s
Jul 18, 20266.0 s
Jul 25, 20266.3 s
Aug 1, 20266.3 s
Aug 8, 20266.7 s
Aug 15, 20267.1 s
Aug 22, 20267.1 s
Aug 29, 20267.1 s
Sep 5, 20266.5 s
Sep 12, 20266.3 s
Sep 19, 20265.8 s
Sep 26, 20265.5 s
Oct 3, 20265.2 s
Oct 10, 20265.6 s
Oct 17, 20265.8 s
Oct 24, 20265.5 s
Oct 31, 20265.5 s
Nov 7, 20265.2 s
Nov 14, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
421 ms249 msMay 30Nov 14367 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026331 ms
Jun 6, 2026331 ms
Jun 13, 2026314 ms
Jun 20, 2026298 ms
Jun 27, 2026283 ms
Jul 4, 2026288 ms
Jul 11, 2026299 ms
Jul 18, 2026325 ms
Jul 25, 2026328 ms
Aug 1, 2026327 ms
Aug 8, 2026312 ms
Aug 15, 2026305 ms
Aug 22, 2026277 ms
Aug 29, 2026269 ms
Sep 5, 2026276 ms
Sep 12, 2026289 ms
Oct 10, 2026306 ms
Oct 24, 2026362 ms
Oct 31, 2026401 ms
Nov 14, 2026367 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 phoenixbaby.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. phoenixbaby.com.br at 0.4 s0.4 s
  2. phoenixbaby.com.br at 0.8 s0.8 s
  3. phoenixbaby.com.br at 1.1 s1.1 s
  4. phoenixbaby.com.br at 1.5 s1.5 s
  5. phoenixbaby.com.br at 1.9 s1.9 s
  6. phoenixbaby.com.br at 2.3 s2.3 s
  7. phoenixbaby.com.br at 2.6 s2.6 s
  8. phoenixbaby.com.br at 3.0 s3.0 s

Speed

10 to fix54
  • Improve image delivery

    11.6 s · 3.3 MB

    9 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.6 s faster on a phone.

  • Reduce unused JavaScript

    7.5 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.5 s faster on a phone.

  • Use efficient cache lifetimes

    6.5 s · 1.7 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 2.6 MB and 1.1 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Reduce unused CSS

    760 ms · 176 KiB

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

  • YouTube adds 429 ms

    429 ms

    YouTube costs a phone 429 ms of main-thread work and 1,009 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 452 ms

    452 ms

    Google Tag Manager costs a phone 452 ms of main-thread work and 484 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.6 s

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

  • elfsightcdn.com adds 8 ms

    8 ms

    elfsightcdn.com costs a phone 8 ms of main-thread work and 732 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.

  • 13 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Legacy JavaScript

    11 KiB

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

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

  • Document request latency

    2 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix50
  • 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.6 s

    5.6 s

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • First Contentful Paint: 12.4 s

    12.4 s

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

  • Largest Contentful Paint: 36.3 s

    36.3 s

    Your largest element takes 36.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Quarto infantil Phoenix Baby - Linha Melinda Off White”.

  • Time to Interactive: 36.3 s

    36.3 s

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

  • Speed Index: 12.4 s

    12.4 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 2 images without width and height

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

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

    +16%

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -19%

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

  • Total Blocking Time: 154 ms

    154 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix25
  • Page weight: 6.8 MB in 57 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 57 requests on a phone: images 4.0 MB (16), scripts 2.4 MB (15) and fonts 203 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Phoenix Baby - Linha Melinda Off White - Ambiente Pagina Ins weighs 3.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    3.0 MB

    1 image is downloaded at several times the size a phone draws it, for example Phoenix Baby - Linha Melinda Off White - Ambiente Pagina Ins at 6,000 px wide, shown at 390 px. Resized copies would save about 3.0 MB.

  • 2 images in older formats

    2 images (3.2 MB) 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.

  • About 1.9 g of CO₂ per visit

    1.93 g

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

6 to fixGoogle 8491
  • 26 buttons without a name

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

  • 46 text elements with low contrast

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

  • 14 tap targets too small

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 4 form fields without a label

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

6 to fixGoogle 10068
  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Phoenix Baby - Móveis Infantis com Amor e Qualidade | Arapongas/PR”.

  • No structured data

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

  • Meta description is long (175 characters)

    Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://YOUR_DOMAIN_HERE/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

3 checks passed
  • Canonical URL set

    The canonical URL is https://phoenixbaby.com.br/.

  • 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

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 390 words, but the HTML your server sends has only 0. 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.

  • No Organization structured data

    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.

  • No llms.txt

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

Best practices

2 to fixGoogle 7791
  • 5 small tap targets

    5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 390 words of copy

    The homepage carries about 390 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 5 cookies set on arrival

    5

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 phoenixbaby.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
Hosting
Immedion, LLC

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on phoenixbaby.com.br, including 19 speed issues, 6 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