Website review, no card needed

playvender.com.br logo

playvender.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 82 checks

This review found 32 issues worth fixing on playvender.com.br, 8 of them high impact, across 82 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

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.3 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.3 s
Jun 13, 20262.1 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
212 ms143 msMay 9Oct 24180 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026185 ms
May 16, 2026193 ms
May 23, 2026204 ms
May 30, 2026193 ms
Jun 6, 2026182 ms
Jun 13, 2026173 ms
Jun 20, 2026159 ms
Jun 27, 2026157 ms
Jul 4, 2026151 ms
Jul 11, 2026151 ms
Jul 18, 2026154 ms
Jul 25, 2026160 ms
Aug 1, 2026167 ms
Aug 8, 2026166 ms
Aug 15, 2026166 ms
Aug 22, 2026172 ms
Aug 29, 2026171 ms
Sep 5, 2026170 ms
Sep 12, 2026172 ms
Sep 19, 2026172 ms
Sep 26, 2026171 ms
Oct 3, 2026173 ms
Oct 10, 2026172 ms
Oct 17, 2026173 ms
Oct 24, 2026180 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 playvender.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. playvender.com.br at 0.7 s0.7 s
  2. playvender.com.br at 1.4 s1.4 s
  3. playvender.com.br at 2.1 s2.1 s
  4. playvender.com.br at 2.8 s2.8 s
  5. playvender.com.br at 3.5 s3.5 s
  6. playvender.com.br at 4.2 s4.2 s
  7. playvender.com.br at 4.9 s4.9 s
  8. playvender.com.br at 5.6 s5.6 s

Speed

8 to fix81
  • Render-blocking requests

    2.0 s

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

  • Reduce unused CSS

    1.2 s · 246 KiB

    About 246 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Improve image delivery

    150 ms · 1,015 KiB

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

  • Mobile performance score: 81

    81/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (agilecdn.com.br, Google CDN and Google Fonts), adding 2.0 MB and 572 ms of main-thread time.

  • agilecdn.com.br adds 552 ms

    552 ms

    agilecdn.com.br costs a phone 552 ms of main-thread work and 2.0 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.

  • Main-thread work: 3.8 s

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

  • 1,699 HTML elements

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

  • 8 long tasks on the main thread

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

  • Reduce unused JavaScript

    79 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    28 KiB

    28 KiB could be saved by minifying CSS.

  • 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: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Seu mercadinho limpo e lucrando”.

  • 31 images without width and height

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

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

  • Time to Interactive: 5.0 s

    5.0 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 168 ms

    168 ms

    Real visitors wait 168 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.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 704 ms

    704 ms

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

  • Largest content (LCP) got 40% faster for real visitors

    -40%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Total Blocking Time: 110 ms

    110 ms

    Scripts block the page for only 110 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 69 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 69 requests on a phone: images 1.4 MB (30), stylesheets 290 KiB (11) and scripts 258 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

3 checks passed
  • 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

6 to fixGoogle 8293
  • 6 buttons without a name

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 18 links without text

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is short (27 characters)

    Your title is only 27 characters: “Playvender Distribuidora RJ”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 186 internal links, 12 external

    The homepage links to 186 pages on playvender.com.br and 12 external pages.

7 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “Conheça os produtos disponíveis na Playvender Distribuidora RJ e faça seus pedidos online.”.

  • One H1 headline

    Your main headline reads: “Playvender Distribuidora RJ”.

  • Canonical URL set

    The canonical URL is https://www.playvender.com.br/.

  • Structured data in place

    Structured data found: Organization, WebApplication 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://www.playvender.com.br/sitemap.xml.

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://www.playvender.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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

3 to fix80
  • 1 linked page hidden from search

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

  • 2 pages share a title

    / and https://www.playvender.com.br/cadastrar all use the title “Playvender Distribuidora RJ”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.playvender.com.br/cadastrar has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.playvender.com.br/bazar, https://www.playvender.com.br/cosmeticos and https://www.playvender.com.br/farmaceuticos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 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 an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 7 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 69 words

    The homepage has only about 69 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
  • 3 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 playvender.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

Framework
jQuery
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on playvender.com.br, including 12 speed issues, 1 SEO issue 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