Website review, no card needed

vivendadocamarao.com.br logo

vivendadocamarao.com.br website review

Visit site (opens in a new tab)Reviewed 1 November 202650 issues · 89 checks

This review found 50 issues worth fixing on vivendadocamarao.com.br, 22 of them high impact, across 89 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
4.1 s3.6 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.9 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20263.9 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20264.0 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
126 ms113 msMay 9Oct 24115 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026120 ms
May 16, 2026119 ms
May 23, 2026120 ms
May 30, 2026117 ms
Jun 6, 2026120 ms
Jun 13, 2026123 ms
Jun 20, 2026124 ms
Jun 27, 2026123 ms
Jul 4, 2026122 ms
Jul 11, 2026119 ms
Jul 18, 2026118 ms
Jul 25, 2026119 ms
Aug 1, 2026116 ms
Aug 8, 2026117 ms
Aug 15, 2026119 ms
Aug 22, 2026120 ms
Aug 29, 2026118 ms
Sep 5, 2026120 ms
Sep 12, 2026118 ms
Sep 19, 2026117 ms
Sep 26, 2026120 ms
Oct 3, 2026116 ms
Oct 10, 2026114 ms
Oct 17, 2026116 ms
Oct 24, 2026115 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 vivendadocamarao.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vivendadocamarao.com.br at 0.8 s0.8 s
  2. vivendadocamarao.com.br at 1.6 s1.6 s
  3. vivendadocamarao.com.br at 2.4 s2.4 s
  4. vivendadocamarao.com.br at 3.2 s3.2 s
  5. vivendadocamarao.com.br at 4.1 s4.1 s
  6. vivendadocamarao.com.br at 4.9 s4.9 s
  7. vivendadocamarao.com.br at 5.7 s5.7 s
  8. vivendadocamarao.com.br at 6.5 s6.5 s

Speed

6 to fix62
  • Improve image delivery

    2.5 s · 1.3 MB

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

  • Render-blocking requests

    3.4 s

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

  • Use efficient cache lifetimes

    550 ms · 595 KiB

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

  • Mobile performance score: 62

    62/100

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

  • Font display

    650 ms

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

  • Reduce unused JavaScript

    420 ms · 94 KiB

    About 94 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.

  • Reduce unused CSS

    270 ms · 22 KiB

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

  • Minify JavaScript

    120 ms · 9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cloudflare CDN, Bootstrap CDN and vlibras.gov.br and others), adding 166 KiB and 23 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 623 ms of it running JavaScript. That is comfortably low.

  • Server response: 591 ms

    591 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.0 s

    5.0 s

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

  • Largest Contentful Paint: 20.2 s

    20.2 s

    Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cardápio Nossas lojas A Vivenda Vivenda Cash Franquias Notí…”.

  • Time to Interactive: 21.3 s

    21.3 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Real-user CLS: 0.18

    0.18

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 961 ms

    961 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

3 checks passed
  • Real-user INP: 155 ms

    155 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

5 to fix36
  • Page weight: 5.5 MB in 155 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 155 requests on a phone: images 4.8 MB (36), scripts 446 KiB (53) and stylesheets 211 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

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

  • 9 images in older formats

    9 images (2.3 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.

  • An image on the first screen is lazy-loaded

    prato3-768x465.png 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).

  • 1 image far larger than shown

    26 KiB

    1 image is downloaded at several times the size a phone draws it, for example Camarao-site-certo.jpeg-Photoroom-768x768.png at 390 px wide, shown at 111 px. Resized copies would save about 26 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.56 g

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

Accessibility

14 to fixGoogle 6779
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 18 text elements with low contrast

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • 10 links without text

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

  • 1 form field without a label

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9285
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Casquinha de Camarão”, “Porção de Camarão Empanado com Batata Frita” and “Porção de Camarão Frito com Batata Frita”). One clear main headline is easier for people and search engines.

  • 68 internal links, 12 external

    The homepage links to 68 pages on vivendadocamarao.com.br and 12 external pages.

6 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “Vivenda do Camarão - Vivenda do Camarão”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at http://vivendadocamarao.com.br/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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://vivendadocamarao.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 (300 words), so crawlers that don't run JavaScript still read it.

Other pages

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

    https://vivendadocamarao.com.br/vivendadocamarao/index 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://vivendadocamarao.com.br/vivendadocamarao/index all use the title “Vivenda do Camarão - Vivenda do Camarão”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://vivendadocamarao.com.br/vivendadocamarao/index, https://vivendadocamarao.com.br/a-vivenda, https://vivendadocamarao.com.br/vivendacash, https://vivendadocamarao.com.br/franquia, https://vivendadocamarao.com.br/noticias and https://vivendadocamarao.com.br/franquias have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://vivendadocamarao.com.br/a-vivenda, https://vivendadocamarao.com.br/vivendacash, https://vivendadocamarao.com.br/franquia, https://vivendadocamarao.com.br/noticias and https://vivendadocamarao.com.br/franquias have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://vivendadocamarao.com.br/franquias took over 3 s to send its HTML from our server.

  • 6 internal pages checked

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

3 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • 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

3 to fixGoogle 9285
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (5 required). Every extra field lowers completion.

  • Only about 162 words

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

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

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 vivendadocamarao.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

CMS
WordPress
Framework
jQuery
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on vivendadocamarao.com.br, including 15 speed issues, 2 SEO issues and 6 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