Website review, no card needed

justapprove.com.br logo

justapprove.com.br website review

Visit site (opens in a new tab)Reviewed 24 October 202630 issues · 84 checks

This review found 30 issues worth fixing on justapprove.com.br, 8 of them high impact, across 84 checks. The most urgent: mobile performance score: 40. 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
1.7 s1.2 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
923 ms74 msMay 2Oct 17196 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026825 ms
May 9, 2026608 ms
May 16, 2026421 ms
May 23, 2026287 ms
May 30, 2026281 ms
Jun 6, 2026281 ms
Jun 13, 2026280 ms
Jun 20, 2026277 ms
Jun 27, 2026265 ms
Jul 4, 2026245 ms
Jul 11, 2026215 ms
Jul 18, 2026191 ms
Jul 25, 2026187 ms
Aug 1, 2026182 ms
Aug 8, 2026181 ms
Aug 15, 2026183 ms
Aug 22, 2026181 ms
Aug 29, 2026177 ms
Sep 5, 2026174 ms
Sep 12, 2026172 ms
Sep 19, 2026173 ms
Sep 26, 2026178 ms
Oct 3, 2026184 ms
Oct 10, 2026191 ms
Oct 17, 2026196 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 justapprove.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. justapprove.com.br at 0.8 s0.8 s
  2. justapprove.com.br at 1.7 s1.7 s
  3. justapprove.com.br at 2.5 s2.5 s
  4. justapprove.com.br at 3.4 s3.4 s
  5. justapprove.com.br at 4.2 s4.2 s
  6. justapprove.com.br at 5.0 s5.0 s
  7. justapprove.com.br at 5.9 s5.9 s
  8. justapprove.com.br at 6.7 s6.7 s

Speed

14 to fix40
  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 8.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.8 MB and 3.8 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 1.2 MB

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

  • Google Tag Manager adds 994 ms

    994 ms

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

  • Improve image delivery

    750 ms · 203 KiB

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

  • Google CDN adds 871 ms

    871 ms

    Google CDN costs a phone 871 ms of main-thread work and 734 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.

  • Render-blocking requests

    850 ms

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

  • 20 long tasks on the main thread

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

  • Facebook adds 529 ms

    529 ms

    Facebook costs a phone 529 ms of main-thread work and 282 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

    525 KiB

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

  • tiendanube.com adds 363 ms

    363 ms

    tiendanube.com costs a phone 363 ms of main-thread work and 128 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.

  • Other Google APIs/SDKs adds 301 ms

    301 ms

    Other Google APIs/SDKs costs a phone 301 ms of main-thread work and 198 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.

  • 2,379 HTML elements

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

  • Reduce unused CSS

    150 ms · 61 KiB

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

  • Legacy JavaScript

    52 KiB

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

  • Minify JavaScript

    49 KiB

    49 KiB could be saved by minifying JavaScript.

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 32 ms

    32 ms

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

Core Web Vitals

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

  • Time to Interactive: 25.0 s

    25.0 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Look oficial Approve com camiseta Only off-white, vista de …”.

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user INP: 240 ms

    240 ms

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

  • Speed Index: 5.7 s

    5.7 s

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

7 checks passed
  • 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 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: 693 ms

    693 ms

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

  • Tap response (INP) got 73% faster for real visitors

    -73%

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

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

    -11%

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

1 to fix85
  • Page weight: 3.7 MB in 127 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 127 requests on a phone: scripts 2.5 MB (44), images 482 KiB (15) and other files 407 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.05 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.8 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

3 to fixGoogle 9797
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

2 checks passed
  • Every image has alt text

    All 69 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 2 mores 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 (7 characters)

    Your title is only 7 characters: “Approve”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 268 internal links, 12 external

    The homepage links to 268 pages on justapprove.com.br and 12 external pages.

7 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Streetwear Brasil: camisetas, moletons e roupas urbanas exclusivas. Compre moda streetwear original com estilo e autent…”.

  • One H1 headline

    Your main headline reads: “APPROVEYOURSELF.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, Product and WebPage.

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

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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://justapprove.com.br/llms.txt (1 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 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 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 15 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 363 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “SHOP”.

  • 5 short forms

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

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.

  • 19 cookies set on arrival

    19

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

  • 38 other companies contacted

    Loading the homepage contacts 38 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 justapprove.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 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 30 issues on justapprove.com.br, including 21 speed issues, 1 SEO issue and 2 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