Website review, no card needed

precolandia.com.br logo

precolandia.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202651 issues · 94 checks

This review found 51 issues worth fixing on precolandia.com.br, 19 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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.3 s2.9 sMay 9Oct 244.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.8 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20264.2 s
Oct 24, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
306 ms220 msMay 9Oct 24253 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026280 ms
May 16, 2026274 ms
May 23, 2026271 ms
May 30, 2026266 ms
Jun 6, 2026272 ms
Jun 13, 2026276 ms
Jun 20, 2026273 ms
Jun 27, 2026270 ms
Jul 4, 2026257 ms
Jul 11, 2026244 ms
Jul 18, 2026233 ms
Jul 25, 2026230 ms
Aug 1, 2026233 ms
Aug 8, 2026236 ms
Aug 15, 2026243 ms
Aug 22, 2026265 ms
Aug 29, 2026288 ms
Sep 5, 2026294 ms
Sep 12, 2026296 ms
Sep 19, 2026281 ms
Sep 26, 2026256 ms
Oct 3, 2026252 ms
Oct 10, 2026254 ms
Oct 17, 2026255 ms
Oct 24, 2026253 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 precolandia.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. precolandia.com.br at 1.0 s1.0 s
  2. precolandia.com.br at 2.1 s2.1 s
  3. precolandia.com.br at 3.1 s3.1 s
  4. precolandia.com.br at 4.2 s4.2 s
  5. precolandia.com.br at 5.2 s5.2 s
  6. precolandia.com.br at 6.2 s6.2 s
  7. precolandia.com.br at 7.3 s7.3 s
  8. precolandia.com.br at 8.3 s8.3 s

Speed

10 to fix51
  • Reduce unused JavaScript

    2.5 s · 700 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 644 KiB

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

  • 4,455 HTML elements

    The page has 4,455 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 (vtexassets.com, Google Tag Manager and Facebook and others), adding 2.8 MB and 1.6 s of main-thread time.

  • Mobile performance score: 51

    51/100

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

  • vtexassets.com adds 708 ms

    708 ms

    vtexassets.com costs a phone 708 ms of main-thread work and 1.4 MB 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.

  • Reduce unused CSS

    640 ms · 93 KiB

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

  • Google Tag Manager adds 472 ms

    472 ms

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

  • Render-blocking requests

    500 ms

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

  • Main-thread work: 3.8 s

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

  • Legacy JavaScript

    250 ms · 49 KiB

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

  • Improve image delivery

    150 ms · 64 KiB

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

  • 11 long tasks on the main thread

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 42 ms

    42 ms

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

Core Web Vitals

12 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 CLS: 0.57

    0.57

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

  • Largest Contentful Paint: 19.5 s

    19.5 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user INP: 253 ms

    253 ms

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

  • Largest content (LCP) got 34% slower for real visitors

    +34%

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

  • 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: 847 ms

    847 ms

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

  • Total Blocking Time: 386 ms

    386 ms

    Scripts block taps and scrolling for 386 ms in total while the page loads. Good is under 200 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) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix83
  • Page weight: 3.3 MB in 178 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 178 requests on a phone: scripts 2.2 MB (63), images 547 KiB (27) and fonts 168 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    ed79537d-b8fa-4ba1-9426-102d7d185306___ec36921d409ba30c1b383 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 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 0.9 g of CO₂ per visit

    0.93 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

11 to fixGoogle 7284
  • ARIA commands must have an accessible name (126 elements)

    ARIA commands must have an accessible name: 126 elements on the page fail this check, rated serious by axe-core.

  • 10 buttons without a name

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

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • 8 tap targets too small

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

  • Hidden but focusable

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

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

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

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

  • 4 links without text

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

1 checks passed
  • 41 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: 41 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8584
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Kit Utensílios de Cozinha, Eletroportáteis e muito mais | Preçolândia”.

  • Structured data has 3 problems

    Structured data found ((untyped) and WebSite) but with 3 problems, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 46 internal links, 5 external

    The homepage links to 46 pages on precolandia.com.br and 5 external pages.

5 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Encontre tudo o que sua casa precisa na Preçolândia. Utensílios de Cozinha, Jogos de Cama, Decoração e muito mais. Aces…”.

  • One H1 headline

    Your main headline reads: “Preçolandia: Referência em utilidades domésticas para casa e cozinha”.

  • Canonical URL set

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

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.precolandia.com.br/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    35%

    The HTML your server sends has 619 of the 1,783 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

Other pages

3 to fix86
  • 5 pages share a title

    /, https://www.precolandia.com.br/politica-de-entrega, https://www.precolandia.com.br/nossas-lojas, https://www.precolandia.com.br/gift-list-home and https://www.precolandia.com.br/vendas-corporativas all use the title “Kit Utensílios de Cozinha, Eletroportáteis e muito mais | Preçolândia”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.precolandia.com.br/politica-de-entrega, https://www.precolandia.com.br/nossas-lojas, https://www.precolandia.com.br/gift-list-home and https://www.precolandia.com.br/vendas-corporativas use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.precolandia.com.br/gift-list-home has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.precolandia.com.br/nossas-lojas and https://www.precolandia.com.br/gift-list-home 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.

  • 2 pages slow to respond

    https://www.precolandia.com.br/nossas-lojas and https://www.precolandia.com.br/cozinha/cozinhar-dia-a-dia/panela-de-pressao took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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 a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9278
  • 1 broken image

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    74 of 90 tappable elements near the top are at least 24 px.

  • 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 1,783 words of copy

    The homepage carries about 1,783 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 24 cookies set on arrival

    24

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

  • 46 other companies contacted

    Loading the homepage contacts 46 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 precolandia.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

Framework
React
Analytics
Google Tag Manager
Hosting
Enflow

Company

Founded
1978
Headquarters
São Paulo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on precolandia.com.br, including 22 speed issues, 4 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