Website review, no card needed

zazule.com.br logo

zazule.com.br website review

Visit site (opens in a new tab)Reviewed 18 October 202624 issues · 82 checks

This review found 24 issues worth fixing on zazule.com.br, 8 of them high impact, across 82 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
2.9 s1.9 sApr 25Oct 102.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.4 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
197 ms120 msApr 25Oct 10155 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026153 ms
May 2, 2026145 ms
May 9, 2026138 ms
May 16, 2026138 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026129 ms
Jun 13, 2026134 ms
Jun 20, 2026139 ms
Jun 27, 2026145 ms
Jul 4, 2026150 ms
Jul 11, 2026152 ms
Jul 18, 2026154 ms
Jul 25, 2026155 ms
Aug 1, 2026150 ms
Aug 8, 2026150 ms
Aug 15, 2026153 ms
Aug 22, 2026156 ms
Aug 29, 2026168 ms
Sep 5, 2026180 ms
Sep 12, 2026188 ms
Sep 19, 2026180 ms
Sep 26, 2026172 ms
Oct 3, 2026168 ms
Oct 10, 2026155 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 zazule.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix61
  • Reduce unused JavaScript

    1.4 s · 312 KiB

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

  • Mobile performance score: 61

    61/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Bing Ads and others), adding 803 KiB and 536 ms of main-thread time.

  • Google Tag Manager adds 337 ms

    337 ms

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

  • Use efficient cache lifetimes

    208 KiB

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

  • Render-blocking requests

    150 ms

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    35 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 96 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 35 ms

    35 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 9.3 s

    9.3 s

    Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “10 anos de fotos que ficam 13 lojas para ver de perto”.

  • Time to Interactive: 11.2 s

    11.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • Total Blocking Time: 236 ms

    236 ms

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

  • Tap response (INP) held steady for real visitors

    +8%

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

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

    +14%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 145 ms

    145 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.072

    0.072

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.49 g

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

4 checks passed
  • Page weight: 1.7 MB in 59 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 59 requests on a phone: scripts 956 KiB (28), images 518 KiB (14) and fonts 148 KiB (6). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

5 to fixGoogle 10094
  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

    Document should not have more than one contentinfo 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.

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

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

Google 100100
  • 123 internal links, 3 external

    The homepage links to 123 pages on zazule.com.br and 3 external pages.

8 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Sua foto vira azulejo personalizado. Veja a prévia antes de pagar, escolha o tamanho e retire em uma das 13 lojas ou re…”.

  • One H1 headline

    Your main headline reads: “Sua foto viraum azulejo personalizado”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Azulejo Personalizado com Foto a partir de R$25 | Zazulê”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, ImageObject, Organization, Place and Store.

  • 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 https://zazule.com.br/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,622 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://zazule.com.br/llms.txt (57 KiB, 167 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://zazule.com.br/carrinho is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

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

6 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 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10084
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187209383&Ver=2&mid=2d094bf8-986b-4a85-bba9-e6b35f8ca47f&bo=2&sid=17f26470cb2911f1a98f31613b18a904&vid=17f287e0cb2911f1beadadaf95fded89&vids=1&msclkid=N&pi=918639831&l.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    22 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 976 words of visible text.

5 checks passed
  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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 Microsoft Ads (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.

  • 15 cookies set on arrival

    15

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

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

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 zazule.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
E-commerce
WooCommerce
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on zazule.com.br, including 12 speed 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