Website review, no card needed

alabarce.net.br logo

alabarce.net.br website review

Visit site (opens in a new tab)Reviewed 18 October 202642 issues · 89 checks

This review found 42 issues worth fixing on alabarce.net.br, 13 of them high impact, across 89 checks. The most urgent: render-blocking 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
4.8 s3.9 sApr 25Oct 104.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.0 s
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20264.3 s
May 30, 20264.4 s
Jun 6, 20264.6 s
Jun 13, 20264.7 s
Jun 20, 20264.5 s
Jun 27, 20264.5 s
Jul 4, 20264.4 s
Jul 11, 20264.4 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
275 ms165 msApr 25Oct 10178 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026260 ms
May 2, 2026262 ms
May 9, 2026227 ms
May 16, 2026220 ms
May 23, 2026213 ms
May 30, 2026228 ms
Jun 6, 2026247 ms
Jun 13, 2026242 ms
Jun 20, 2026241 ms
Jun 27, 2026209 ms
Jul 4, 2026195 ms
Jul 11, 2026238 ms
Jul 18, 2026232 ms
Jul 25, 2026255 ms
Aug 1, 2026240 ms
Aug 8, 2026178 ms
Aug 15, 2026190 ms
Aug 22, 2026179 ms
Aug 29, 2026178 ms
Sep 5, 2026194 ms
Sep 12, 2026186 ms
Sep 19, 2026188 ms
Sep 26, 2026198 ms
Oct 3, 2026194 ms
Oct 10, 2026178 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 alabarce.net.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix71
  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    900 ms · 99 KiB

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

  • Reduce unused CSS

    410 ms · 56 KiB

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

  • Reduce unused JavaScript

    150 ms · 186 KiB

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

  • Legacy JavaScript

    200 ms · 28 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and JSDelivr CDN and others), adding 439 KiB and 79 ms of main-thread time.

  • Font display

    50 ms

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

  • Minify JavaScript

    47 KiB

    47 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    8 KiB

    1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 23 ms

    23 ms

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

Core Web Vitals

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Termo de Uso e Consentimento Pelo presente Termo de Uso e C…”.

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 268 ms

    268 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Time to Interactive: 5.2 s

    5.2 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Tap response (INP) got 29% faster for real visitors

    -29%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 1 image in older formats

    1 image (130 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.2 g of CO₂ per visit

    0.22 g

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

3 checks passed
  • Page weight: 785 KiB in 40 requests

    785 KiB

    Your homepage downloads 785 KiB in 40 requests on a phone: scripts 376 KiB (14), images 193 KiB (10) and fonts 105 KiB (2). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 7284
  • 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.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 24 images without alt text

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

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

  • 4 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

7 to fixGoogle 7766
  • No meta description

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

  • Title is short (17 characters)

    Your title is only 17 characters: “DELIVERY ALABARCE”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 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 XML sitemap

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

  • 7 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 207 internal links, 21 external

    The homepage links to 207 pages on alabarce.net.br and 21 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://alabarce.net.br/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://alabarce.net.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 (1,046 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 11 pages share a title

    https://alabarce.net.br/products, https://alabarce.net.br/t/departamentos/hortifruti, https://alabarce.net.br/t/departamentos/hortifruti/frutas, https://alabarce.net.br/t/departamentos/hortifruti/legumes, https://alabarce.net.br/t/departamentos/hortifruti/embalados and https://alabarce.net.br/t/departamentos/hortifruti/verduras and 5 others all use the title “Bot Index”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://alabarce.net.br/sale, https://alabarce.net.br/products, https://alabarce.net.br/t/departamentos/hortifruti, https://alabarce.net.br/t/departamentos/hortifruti/frutas, https://alabarce.net.br/t/departamentos/hortifruti/legumes and https://alabarce.net.br/t/departamentos/hortifruti/embalados and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages with very little text

    https://alabarce.net.br/products, https://alabarce.net.br/t/departamentos/hortifruti, https://alabarce.net.br/t/departamentos/hortifruti/frutas, https://alabarce.net.br/t/departamentos/hortifruti/legumes, https://alabarce.net.br/t/departamentos/hortifruti/embalados and https://alabarce.net.br/t/departamentos/hortifruti/verduras and 5 others have 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.

  • 1 page slow to respond

    https://alabarce.net.br/sale took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 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 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8878
  • 3 broken images

    3 images failed to load on a phone, for example https://alabarce.net.br/s3/alabarce/ecommerce/production/spree/taxon_images/33772_attachments_original.svg?1615340849.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://s3.us-east-1.amazonaws.com/bluesoft-erp-us/alabarce/ecommerce/production/spree/the…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

  • 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 252 words of copy

    The homepage carries about 252 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Pet Shop”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 alabarce.net.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on alabarce.net.br, including 14 speed issues, 7 SEO issues and 3 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