Website review, no card needed

paccoby.com.br logo

paccoby.com.br website review

Visit site (opens in a new tab)Reviewed 5 November 202647 issues · 86 checks

This review found 47 issues worth fixing on paccoby.com.br, 16 of them high impact, across 86 checks. The most urgent: page weight: 13.3 MB in 204 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
3.1 s2.0 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
461 ms255 msMay 16Oct 31435 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026316 ms
May 23, 2026316 ms
May 30, 2026306 ms
Jun 6, 2026296 ms
Jun 13, 2026288 ms
Jun 20, 2026279 ms
Jun 27, 2026283 ms
Jul 4, 2026288 ms
Jul 11, 2026295 ms
Jul 18, 2026299 ms
Jul 25, 2026300 ms
Aug 1, 2026315 ms
Aug 8, 2026328 ms
Aug 15, 2026336 ms
Aug 22, 2026348 ms
Aug 29, 2026338 ms
Sep 5, 2026330 ms
Sep 12, 2026328 ms
Sep 19, 2026326 ms
Sep 26, 2026341 ms
Oct 3, 2026365 ms
Oct 10, 2026387 ms
Oct 17, 2026420 ms
Oct 24, 2026437 ms
Oct 31, 2026435 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 paccoby.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paccoby.com.br at 1.4 s1.4 s
  2. paccoby.com.br at 2.9 s2.9 s
  3. paccoby.com.br at 4.3 s4.3 s
  4. paccoby.com.br at 5.7 s5.7 s
  5. paccoby.com.br at 7.2 s7.2 s
  6. paccoby.com.br at 8.6 s8.6 s
  7. paccoby.com.br at 10.0 s10.0 s
  8. paccoby.com.br at 11.5 s11.5 s

Speed

9 to fix51
  • Main-thread work: 8.7 s

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

  • 3,216 HTML elements

    The page has 3,216 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 51

    51/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and openai.com and others), adding 735 KiB and 719 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Reduce unused CSS

    430 ms · 70 KiB

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

  • Google Tag Manager adds 404 ms

    404 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused JavaScript

    285 KiB

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

  • Minify JavaScript

    130 ms · 18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    130 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Improve image delivery

    53 KiB

    4 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    48 KiB

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

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

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

11 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 LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 9.6 s

    9.6 s

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

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Total Blocking Time: 774 ms

    774 ms

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Real-user INP: 316 ms

    316 ms

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

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

    +38%

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

  • Real-user TTFB: 839 ms

    839 ms

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

4 to fix50
  • Page weight: 13.3 MB in 204 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 204 requests on a phone: media 9.6 MB (4), images 1.5 MB (40) and scripts 951 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (1.5 MB) are 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.

  • An image on the first screen is lazy-loaded

    banner-home-05.11-colecao-canecas-mobile-pacco_129a3693-0d2b 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).

  • 3 images far larger than shown

    244 KiB

    3 images are downloaded at several times the size a phone draws them, for example garrafa-termica-easy-pacco-png-950ml-cor-cherry-blossom-1.we at 800 px wide, shown at 180 px. Resized copies would save about 244 KiB.

  • 2 images below the first screen load straight away

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

  • About 3.8 g of CO₂ per visit

    3.77 g

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

Accessibility

10 to fixGoogle 8789
  • 1 button without a name

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

  • 20 images without alt text

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

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

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

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

    Main 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 main landmark (1 element)

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

  • ARIA role should be appropriate for the element (61 elements)

    ARIA role should be appropriate for the element: 61 elements on the page fail this check, rated minor by axe-core.

  • 12 links without text

    12 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 should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

SEO

Google 92100
  • 211 internal links, 21 external

    The homepage links to 211 pages on paccoby.com.br and 21 external pages.

8 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Descubra os produtos térmicos que simplificam a rotina, proporcionam saúde e bem-estar. Viva ainda melhor com a sua PAC…”.

  • One H1 headline

    Your main headline reads: “PACCO | Garrafas, copos, bolsas e acessórios térmicos”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “PACCO | Garrafas, copos, bolsas e acessórios térmicos”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, DataFeed, Organization and WebSite.

  • 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://paccoby.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://paccoby.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 (1,042 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://paccoby.com.br/collections/best-sellers, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://paccoby.com.br/pages/fique-atento has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://paccoby.com.br/pages/fique-atento, https://paccoby.com.br/pages/pacco-plus and https://paccoby.com.br/products/camiseta-unissex-pacco-insider have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://paccoby.com.br/collections/colecoes took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

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

  • 55 small tap targets

    55 of 98 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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: 1 trust badge. 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.

  • Only about 239 words

    The homepage has only about 239 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 8 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 paccoby.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

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on paccoby.com.br, including 20 speed 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