Website review, no card needed

estampartepf.com.br logo

estampartepf.com.br website review

Visit site (opens in a new tab)Reviewed 20 November 202619 issues · 58 checks

This review found 19 issues worth fixing on estampartepf.com.br, 4 of them high impact, across 58 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

Full-page screenshot of estampartepf.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. estampartepf.com.br at 0.4 s0.4 s
  2. estampartepf.com.br at 0.8 s0.8 s
  3. estampartepf.com.br at 1.3 s1.3 s
  4. estampartepf.com.br at 1.7 s1.7 s
  5. estampartepf.com.br at 2.1 s2.1 s
  6. estampartepf.com.br at 2.5 s2.5 s
  7. estampartepf.com.br at 2.9 s2.9 s
  8. estampartepf.com.br at 3.3 s3.3 s

Speed

2 to fix90
  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    550 ms · 338 KiB

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

  • Improve image delivery

    28 KiB

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

  • Reduce unused JavaScript

    21 KiB

    About 21 KiB of JavaScript is downloaded but never used on this page.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 87 KiB and 4 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

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

  • Server response: 124 ms

    124 ms

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

Core Web Vitals

4 to fix93
  • Speed Index: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Estamparte Brindes”. Most of its time is resource load delay (1.2 s).

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • Cumulative Layout Shift: 0.012

    0.012

    The layout barely moves while loading (CLS 0.012, 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

1 to fix90
  • 1 image far larger than shown

    74 KiB

    1 image is downloaded at several times the size a phone draws it, for example loja-estamparte.jpg at 1,254 px wide, shown at 322 px. Resized copies would save about 74 KiB.

  • 1 image in older formats

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

    0.12 g

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

2 checks passed
  • Page weight: 446 KiB in 36 requests

    446 KiB

    Your homepage downloads 446 KiB in 36 requests on a phone: images 187 KiB (2), scripts 132 KiB (15) and fonts 81 KiB (6). That is a lean page.

  • Images load when needed

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

Accessibility

3 to fixGoogle 9195
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

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

  • 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 X (Twitter) card tag

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

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Estamparte Brindes - Mais de 8 anos transformando marcas em experiências. Especialistas em brindes corporativos e perso…”.

  • One H1 headline

    Your main headline reads: “Mais de 8 anos transformando marcas em experiências”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “estamparte – brindes personalizados”.

  • Canonical URL set

    The canonical URL is https://estampartepf.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://estampartepf.com.br/wp-sitemap.xml.

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://estampartepf.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 (474 words), so crawlers that don't run JavaScript still read it.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 468 words of visible text.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 estampartepf.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
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on estampartepf.com.br, including 6 speed issues, 3 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