Website review, no card needed
digamo.uy website review
Visit site (opens in a new tab)Reviewed 12 November 202639 issues · 78 checks
This review found 39 issues worth fixing on digamo.uy, 19 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63D- #107,110 of 112,578 reviewed websitesbeats 4%
- #63,258 of 64,677 online storesbeats 2%
- #2,427 of 2,571 WooCommerce storesbeats 4%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 5.3 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.8 s |
| Jul 25, 2026 | 7.2 s |
| Aug 1, 2026 | 6.4 s |
| Aug 8, 2026 | 5.3 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 6.0 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 5.8 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.7 s |
| Oct 31, 2026 | 5.6 s |
| Nov 7, 2026 | 5.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 81 ms |
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 81 ms |
| Jul 4, 2026 | 77 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 105 ms |
| Aug 22, 2026 | 92 ms |
| Sep 5, 2026 | 121 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
Speed
Use efficient cache lifetimes
3.3 s · 866 KiB62 files are served with short cache lifetimes, so returning visitors download them again (866 KiB).
Render-blocking requests
2.6 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.8 s · 392 KiBAbout 392 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
600 ms · 146 KiBAbout 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
300 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 207 ms. During a long task the page ignores taps.
Improve image delivery
193 KiB1 image could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 third-party services on the page
4 third-party services load with your homepage (mercadopago.com, Google Fonts and mercadolibre.com and others), adding 175 KiB and 7 ms of main-thread time.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 687 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.5 s
5.5 sReal visitors see the first content after 5.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.8 s
5.8 sReal visitors wait 5.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Cumulative Layout Shift: 0.451
0.451The layout shifts by 0.451 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.7 s
8.7 sThe page becomes fully interactive after 8.7 s. Good is under 3.8 s.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 81 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 377 ms
377 msScripts block taps and scrolling for 377 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.7 s to 5.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
1 image far larger than shown
191 KiB1 image is downloaded at several times the size a phone draws it, for example IMAGOTIPO-DIGAMO.png at 3,415 px wide, shown at 171 px. Resized copies would save about 191 KiB.
1 image in older formats
1 image (195 KiB) is 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 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.7 MB in 73 requests
1.7 MBYour homepage downloads 1.7 MB in 73 requests on a phone: scripts 804 KiB (50), images 507 KiB (5) and fonts 227 KiB (7). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
18 text elements with low contrast
18 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.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (9 elements)
ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
44 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: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (23 characters)
Your title is only 23 characters: “Digamo.uy – baby & kids”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
79 internal links, 2 external
The homepage links to 79 pages on digamo.uy and 2 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.digamo.uy/.
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.digamo.uy/wp-sitemap.xml.
AI search readiness
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.
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 (280 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.digamo.uy/index.php/tienda, https://www.digamo.uy/index.php/categoria-producto/beb-s/andadores-y-veh-culos-de-beb-s, https://www.digamo.uy/index.php/categoria-producto/beb-s/art-culos-de-beb-s-para-ba-o and https://www.digamo.uy/index.php/categoria-producto/beb-s/cuarto-del-beb have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
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.
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 4 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'innerHTML')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 151 words
The homepage has only about 151 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.
1 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 3 of them by other companies (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 digamo.uy, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- React
- E-commerce
- WooCommerce
- Hosting
- Administracion Nacional de Telecomunicaciones
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on digamo.uy, including 17 speed issues, 6 SEO issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.