Website review, no card needed

penalty.com.br logo

penalty.com.br website review

Visit site (opens in a new tab)Reviewed 17 November 202644 issues · 84 checks

This review found 44 issues worth fixing on penalty.com.br, 15 of them high impact, across 84 checks. The most urgent: mobile performance score: 44. 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.1 s3.5 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.7 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.8 s
Jul 4, 20263.6 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.6 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Nov 7, 20263.7 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
391 ms339 msMay 30Nov 14359 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026345 ms
Jun 6, 2026358 ms
Jun 13, 2026366 ms
Jun 20, 2026370 ms
Jun 27, 2026375 ms
Jul 4, 2026373 ms
Jul 11, 2026369 ms
Jul 18, 2026367 ms
Jul 25, 2026361 ms
Aug 1, 2026358 ms
Aug 8, 2026366 ms
Aug 15, 2026372 ms
Aug 22, 2026372 ms
Aug 29, 2026374 ms
Sep 5, 2026370 ms
Sep 12, 2026370 ms
Sep 19, 2026373 ms
Sep 26, 2026382 ms
Oct 3, 2026383 ms
Oct 10, 2026382 ms
Oct 17, 2026385 ms
Oct 24, 2026380 ms
Oct 31, 2026379 ms
Nov 7, 2026376 ms
Nov 14, 2026359 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 penalty.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix44
  • Mobile performance score: 44

    44/100

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

  • 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 3.5 MB and 1.5 s of main-thread time.

  • Improve image delivery

    300 ms · 968 KiB

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

  • Reduce unused JavaScript

    300 ms · 598 KiB

    About 598 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • vtexassets.com adds 627 ms

    627 ms

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

    450 ms · 89 KiB

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

  • Google Tag Manager adds 411 ms

    411 ms

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

    446 KiB

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

  • Main-thread work: 3.0 s

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    20 KiB

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

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

1 checks passed
  • Server response: 46 ms

    46 ms

    Your server sent the HTML in 46 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 LCP: 4.1 s

    4.1 s

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

  • Real-user CLS: 0.47

    0.47

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

  • Real-user FCP: 3.6 s

    3.6 s

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

  • Time to Interactive: 22.2 s

    22.2 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

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

  • Cumulative Layout Shift: 0.486

    0.486

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user INP: 363 ms

    363 ms

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Total Blocking Time: 295 ms

    295 ms

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

  • 13 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 139 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 139 requests on a phone: scripts 1.9 MB (54), images 1.5 MB (31) and HTML 214 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (74 KiB) 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.

  • 4 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.07 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8987
  • 4 buttons without a name

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

  • 20 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (ItemList, Organization and WebSite) but with 1 problem, 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.

  • No X (Twitter) card tag

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

  • 51 internal links, 0 external

    The homepage links to 51 pages on penalty.com.br and 0 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Comprar Bola , Chuteira, Roupa e Equipamento Esportivo. Em até 10x s/juros. Produtos para Futebol, Volei, Beach Tennis,…”.

  • One H1 headline

    Your main headline reads: “PENALTY, SE JOGA!”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Esporte, Lançamentos e Ofertas Exclusivas | Penalty”.

  • Canonical URL set

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

AI search readiness

1 to fix77
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

2 checks passed
  • Organization data: 5 of 6 facts

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

  • llms.txt published

    The site publishes https://www.penalty.com.br/llms.txt (11 KiB, 34 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix74
  • 2 linked pages are broken

    Your homepage links to https://www.penalty.com.br/storm%204%20campo and https://www.penalty.com.br/digital%204, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages share a meta description

    https://www.penalty.com.br/lancamentos, https://www.penalty.com.br/stadium and https://www.penalty.com.br/penalty-magia-27 use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.penalty.com.br/penalty-magia-27 has 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.

  • 6 pages slow to respond

    https://www.penalty.com.br/lancamentos, https://www.penalty.com.br/masculino, https://www.penalty.com.br/feminino, https://www.penalty.com.br/infantil, https://www.penalty.com.br/chuteiras and https://www.penalty.com.br/equipamentos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 13 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 7 small tap targets

    7 of 17 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 “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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 143 words

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and TikTok Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Amazon Ads, 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.

  • 21 cookies set on arrival

    21

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

Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1970
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 44 issues on penalty.com.br, including 22 speed issues, 2 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