Website review, no card needed

digaspi.com.br logo

digaspi.com.br website review

Visit site (opens in a new tab)Reviewed 18 November 202654 issues · 91 checks

This review found 54 issues worth fixing on digaspi.com.br, 22 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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.8 s4.2 sMay 30Nov 144.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20264.4 s
Jun 20, 20264.3 s
Jun 27, 20264.3 s
Jul 4, 20264.3 s
Jul 11, 20264.3 s
Jul 18, 20264.2 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.5 s
Aug 29, 20264.6 s
Sep 5, 20264.6 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.5 s
Oct 3, 20264.4 s
Oct 10, 20264.4 s
Oct 17, 20264.6 s
Oct 24, 20264.7 s
Oct 31, 20264.7 s
Nov 7, 20264.7 s
Nov 14, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
393 ms291 msMay 30Nov 14336 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026303 ms
Jun 6, 2026305 ms
Jun 13, 2026308 ms
Jun 20, 2026310 ms
Jun 27, 2026318 ms
Jul 4, 2026314 ms
Jul 11, 2026322 ms
Jul 18, 2026324 ms
Jul 25, 2026323 ms
Aug 1, 2026327 ms
Aug 8, 2026329 ms
Aug 15, 2026333 ms
Aug 22, 2026335 ms
Aug 29, 2026352 ms
Sep 5, 2026367 ms
Sep 12, 2026375 ms
Sep 19, 2026381 ms
Sep 26, 2026376 ms
Oct 3, 2026369 ms
Oct 10, 2026357 ms
Oct 17, 2026342 ms
Oct 24, 2026341 ms
Oct 31, 2026340 ms
Nov 7, 2026342 ms
Nov 14, 2026336 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 digaspi.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. digaspi.com.br at 0.8 s0.8 s
  2. digaspi.com.br at 1.7 s1.7 s
  3. digaspi.com.br at 2.5 s2.5 s
  4. digaspi.com.br at 3.4 s3.4 s
  5. digaspi.com.br at 4.2 s4.2 s
  6. digaspi.com.br at 5.1 s5.1 s
  7. digaspi.com.br at 5.9 s5.9 s
  8. digaspi.com.br at 6.8 s6.8 s

Speed

12 to fix26
  • Reduce unused JavaScript

    1.6 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Improve image delivery

    1.1 s · 301 KiB

    14 images could be 301 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 4.0 s

    A phone's processor spends 4.0 s on main-thread work while loading, 2.4 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 CDN, vtexassets.com and Google Tag Manager and others), adding 5.4 MB and 1.9 s of main-thread time.

  • Google CDN adds 624 ms

    624 ms

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

  • Use efficient cache lifetimes

    350 ms · 298 KiB

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

  • vtexassets.com adds 475 ms

    475 ms

    vtexassets.com costs a phone 475 ms of main-thread work and 1.6 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 · 70 KiB

    About 70 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 379 ms

    379 ms

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

  • Google Maps adds 189 ms

    189 ms

    Google Maps costs a phone 189 ms of main-thread work and 328 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.

  • Legacy JavaScript

    200 ms · 47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 16 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 10 KiB

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

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 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 CLS: 1.17

    1.17

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

  • Cumulative Layout Shift: 3.159

    3.159

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

  • Largest Contentful Paint: 10.2 s

    10.2 s

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

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user INP: 256 ms

    256 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 455 ms

    455 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 21 images without width and height

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

Images and page weight

2 to fix64
  • Page weight: 4.8 MB in 159 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 159 requests on a phone: scripts 2.7 MB (56), images 958 KiB (56) and other files 731 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    098d2310-4605-4405-8a0c-a4dd1f9e57b4___8ff0557ad90d66842fac3 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).

  • 4 images in older formats

    4 images (229 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.

  • About 1.3 g of CO₂ per visit

    1.35 g

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

10 to fixGoogle 7386
  • 1 button without a name

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

  • Hidden but focusable

    70 elements hidden from screen readers can still receive keyboard focus.

  • 4 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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 (10 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 5 form fields without a label

    5 form fields have 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

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

SEO

5 to fixGoogle 9274
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “Di Gaspi - Moda dos pés à cabeça, calçados, Roupas e Moda Esportiva em até 10x sem juros”.

  • Structured data has 1 problem

    Structured data found (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.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 93 internal links, 14 external

    The homepage links to 93 pages on digaspi.com.br and 14 external pages.

4 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Di Gaspi: rede de lojas de calçados, moda e artigos esportivos desde 1989. Nike, Adidas, Puma e mais, com 5% off no Pix…”.

  • Canonical URL set

    The canonical URL is https://www.digaspi.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.digaspi.com.br/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://www.digaspi.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 (509 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix43
  • 1 linked page is broken

    Your homepage links to https://www.digaspi.com.br/novidades/primavera-verao-2027, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a title

    https://www.digaspi.com.br/anabela and https://www.digaspi.com.br/pegada have no <title>, so Google invents the link text in results.

  • 5 linked pages hidden from search

    https://www.digaspi.com.br/jeans, https://www.digaspi.com.br/1074, https://www.digaspi.com.br/elevado, https://www.digaspi.com.br/t%C3%AAnis%20olympikus%20corre%20vento%203%20unissex and https://www.digaspi.com.br/1060 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.digaspi.com.br/anabela and https://www.digaspi.com.br/pegada have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.digaspi.com.br/novidades, https://www.digaspi.com.br/jeans, https://www.digaspi.com.br/1074, https://www.digaspi.com.br/elevado, https://www.digaspi.com.br/t%C3%AAnis%20olympikus%20corre%20vento%203%20unissex and https://www.digaspi.com.br/1060 use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.digaspi.com.br/1074, https://www.digaspi.com.br/anabela and https://www.digaspi.com.br/pegada have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.digaspi.com.br/novidades, https://www.digaspi.com.br/marcas, https://www.digaspi.com.br/feminino/calcados/sandalias, https://www.digaspi.com.br/jeans and https://www.digaspi.com.br/pegada took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 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 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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: 3 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 446 words of copy

    The homepage carries about 446 words of visible text.

3 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 20 cookies set on arrival

    20

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 digaspi.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
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on digaspi.com.br, including 25 speed issues, 5 SEO issues and 3 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