Website review, no card needed

zonacriativa.com.br logo

zonacriativa.com.br website review

Visit site (opens in a new tab)Reviewed 19 October 202661 issues · 76 checks

This review found 61 issues worth fixing on zonacriativa.com.br, 28 of them high impact, across 76 checks. The most urgent: avoid multiple page redirects. 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

Full-page screenshot of zonacriativa.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zonacriativa.com.br at 1.4 s1.4 s
  2. zonacriativa.com.br at 2.9 s2.9 s
  3. zonacriativa.com.br at 4.3 s4.3 s
  4. zonacriativa.com.br at 5.8 s5.8 s
  5. zonacriativa.com.br at 7.2 s7.2 s
  6. zonacriativa.com.br at 8.7 s8.7 s
  7. zonacriativa.com.br at 10.1 s10.1 s
  8. zonacriativa.com.br at 11.6 s11.6 s

Speed

6 to fix25
  • Avoid multiple page redirects

    1.4 s

    The page goes through 2 redirects before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.

  • Main-thread work: 10.4 s

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

  • Mobile performance score: 25

    25/100

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

  • Reduce unused JavaScript

    150 ms · 2.7 MB

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

  • Reduce unused CSS

    900 ms · 210 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 32 ms

    32 ms

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

Core Web Vitals

13 to fix0
  • 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 INP: 556 ms

    556 ms

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

  • Real-user CLS: 0.34

    0.34

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

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

  • Speed Index: 20.2 s

    20.2 s

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

  • Time to Interactive: 52.8 s

    52.8 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

    Scripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.122

    0.122

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

  • 12 images without width and height

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

Images and page weight

4 to fix28
  • Page weight: 13.2 MB in 317 requests

    13.2 MB

    Your homepage downloads 13.2 MB in 317 requests on a phone: images 6.7 MB (102), scripts 4.2 MB (94) and other files 826 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    3.3 MB

    9 images are downloaded at several times the size a phone draws them, for example 4d04822d-b7e3-4f29-8eaf-ecc3f46d0746___1a34e4e7aeccf0c82a69c at 2,605 px wide, shown at 160 px. Resized copies would save about 3.3 MB.

  • 4 images over 500 KB

    4 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 8 images below the first screen load straight away

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

  • About 3.7 g of CO₂ per visit

    3.75 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

14 to fixGoogle 7983
  • 5 buttons without a name

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

  • 19 tap targets too small

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

  • Hidden but focusable

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

  • ARIA commands must have an accessible name (5 elements)

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 12 links without text

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

  • 2 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

10 to fixGoogle 10043
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • 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://zonacriativa.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 507 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://zonacriativa.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.

Best practices

6 to fixGoogle 5056
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 32 small tap targets

    32 of 81 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.

  • 6 JavaScript errors while loading

    6 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 ()”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

Content and conversion

5 to fix20
  • 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.

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

    The homepage carries about 507 words of visible text.

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, Hotjar and Meta Pixel 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.

  • 28 cookies set on arrival

    28

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 zonacriativa.com.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 61 issues on zonacriativa.com.br, including 19 speed issues, 10 SEO issues and 5 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