Website review, no card needed

garrido.com.do logo

garrido.com.do website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 66 checks

This review found 43 issues worth fixing on garrido.com.do, 21 of them high impact, across 66 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
8.4 s6.6 sApr 25Oct 107.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20268.0 s
May 2, 20268.0 s
May 9, 20267.9 s
May 16, 20267.6 s
May 23, 20267.5 s
May 30, 20267.3 s
Jun 6, 20267.2 s
Jun 13, 20267.4 s
Jun 20, 20267.3 s
Jun 27, 20267.2 s
Jul 4, 20267.0 s
Jul 11, 20266.8 s
Jul 18, 20266.9 s
Jul 25, 20266.9 s
Aug 1, 20267.2 s
Aug 8, 20267.4 s
Aug 15, 20267.7 s
Aug 22, 20268.1 s
Aug 29, 20268.1 s
Sep 5, 20268.1 s
Sep 12, 20268.2 s
Sep 19, 20268.0 s
Sep 26, 20268.1 s
Oct 3, 20268.0 s
Oct 10, 20267.8 s
Real-visitor tap response (INP)75th percentile, phones
1.1 s831 msApr 25Oct 10931 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 20261.0 s
May 2, 2026993 ms
May 9, 2026932 ms
May 16, 2026889 ms
May 23, 2026968 ms
May 30, 2026977 ms
Jun 6, 2026921 ms
Jun 13, 2026916 ms
Jun 20, 2026865 ms
Jun 27, 2026897 ms
Jul 4, 2026991 ms
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 2026990 ms
Aug 8, 2026990 ms
Aug 15, 2026931 ms
Aug 22, 2026938 ms
Aug 29, 2026941 ms
Sep 5, 2026922 ms
Sep 12, 2026971 ms
Sep 19, 2026950 ms
Sep 26, 2026974 ms
Oct 3, 2026971 ms
Oct 10, 2026931 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 garrido.com.do (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. garrido.com.do at 1.0 s1.0 s
  2. garrido.com.do at 2.0 s2.0 s
  3. garrido.com.do at 2.9 s2.9 s
  4. garrido.com.do at 3.9 s3.9 s
  5. garrido.com.do at 4.9 s4.9 s
  6. garrido.com.do at 5.9 s5.9 s
  7. garrido.com.do at 6.9 s6.9 s
  8. garrido.com.do at 7.8 s7.8 s

Speed

10 to fix10
  • Reduce unused JavaScript

    6.9 s · 1.4 MB

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

  • Improve image delivery

    1.9 s · 4.2 MB

    30 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Main-thread work: 11.3 s

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

  • Mobile performance score: 10

    10/100

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

  • Use efficient cache lifetimes

    3.9 MB

    28 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).

  • Render-blocking requests

    850 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and firebaseapp.com and others), adding 2.3 MB and 496 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 344 ms

    344 ms

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

  • instaleap.io adds 0 ms

    0 ms

    instaleap.io costs a phone 0 ms of main-thread work and 1.7 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

    52 KiB

    About 52 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    28 KiB

    Polyfills for old browsers add 28 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.

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

    46 ms

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

Core Web Vitals

12 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: 8.5 s

    8.5 s

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

  • Real-user INP: 1.4 s

    1.4 s

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

  • Real-user CLS: 1.57

    1.57

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

  • Real-user FCP: 6.2 s

    6.2 s

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

  • Largest Contentful Paint: 27.7 s

    27.7 s

    Your largest element takes 27.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banners principal - App-Banner-0”.

  • Speed Index: 22.2 s

    22.2 s

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

  • Time to Interactive: 45.9 s

    45.9 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Cumulative Layout Shift: 0.448

    0.448

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

Images and page weight

2 to fix60
  • Page weight: 9.1 MB in 234 requests

    9.1 MB

    Your homepage downloads 9.1 MB in 234 requests on a phone: images 5.6 MB (40), scripts 3.0 MB (155) and fonts 224 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    108 KiB

    1 image is downloaded at several times the size a phone draws it, for example TIENDAS_GARRIDO_banners_20250723_home_1753303461108.png at 1,356 px wide, shown at 374 px. Resized copies would save about 108 KiB.

  • 1 image in older formats

    1 image (37 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 2.6 g of CO₂ per visit

    2.58 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 8095
  • 5 buttons without a name

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

  • 5 text elements with low contrast

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

  • 1 form field without a label

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

8 to fixGoogle 7762
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (10 characters)

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

  • Canonical points to another host

    Your canonical URL points to tiendas-garrido.instaleap.io, not garrido.com.do, so Google may credit that host instead.

  • 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.garrido.com.do/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at garrido.com.do/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

1 checks passed
  • One H1 headline

    Your main headline reads: “Garrido Ta”.

AI search readiness

1 to fix69
  • 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.garrido.com.do/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.

Best practices

1 to fixGoogle 8897
  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 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 24 words

    The homepage has only about 24 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
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 garrido.com.do, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on garrido.com.do, including 22 speed issues, 8 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