Website review, no card needed

ad-cap.com.ar logo

ad-cap.com.ar website review

Visit site (opens in a new tab)Reviewed 18 October 202633 issues · 77 checks

This review found 33 issues worth fixing on ad-cap.com.ar, 7 of them high impact, across 77 checks. The most urgent: page weight: 24.6 MB in 66 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.9 s1.8 sApr 25Oct 102.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.6 s
May 2, 20262.7 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.3 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
311 ms75 msApr 25Oct 10102 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026284 ms
May 2, 2026279 ms
May 9, 2026277 ms
May 16, 2026267 ms
May 23, 2026266 ms
May 30, 2026267 ms
Jun 6, 2026259 ms
Jun 13, 2026245 ms
Jun 20, 2026242 ms
Jun 27, 2026210 ms
Jul 4, 2026190 ms
Jul 11, 2026173 ms
Jul 18, 2026151 ms
Jul 25, 2026137 ms
Aug 1, 2026126 ms
Aug 8, 2026130 ms
Aug 15, 2026136 ms
Aug 22, 2026138 ms
Aug 29, 2026140 ms
Sep 5, 2026128 ms
Sep 12, 2026121 ms
Sep 19, 2026120 ms
Sep 26, 2026117 ms
Oct 3, 2026112 ms
Oct 10, 2026102 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 ad-cap.com.ar (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ad-cap.com.ar at 0.4 s0.4 s
  2. ad-cap.com.ar at 0.8 s0.8 s
  3. ad-cap.com.ar at 1.1 s1.1 s
  4. ad-cap.com.ar at 1.5 s1.5 s
  5. ad-cap.com.ar at 1.9 s1.9 s
  6. ad-cap.com.ar at 2.3 s2.3 s
  7. ad-cap.com.ar at 2.6 s2.6 s
  8. ad-cap.com.ar at 3.0 s3.0 s

Speed

4 to fix67
  • Use efficient cache lifetimes

    23.8 MB

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

  • Improve image delivery

    1.1 MB

    4 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    600 ms

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

  • Reduce unused JavaScript

    270 ms · 108 KiB

    About 108 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 270 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics and others), adding 183 KiB and 91 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    16 KiB

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

  • Legacy JavaScript

    11 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 67. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 412 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 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.

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 2 images without width and height

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

7 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 102 ms

    102 ms

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

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

    -62%

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

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

    -21%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 14 ms

    14 ms

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

Images and page weight

5 to fix28
  • Page weight: 24.6 MB in 66 requests

    24.6 MB

    Your homepage downloads 24.6 MB in 66 requests on a phone: media 19.6 MB (4), images 4.2 MB (15) and scripts 507 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (4.0 MB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (664 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    272 KiB

    1 image is downloaded at several times the size a phone draws it, for example apibrokermobile.png at 1,398 px wide, shown at 358 px. Resized copies would save about 272 KiB.

  • About 7.0 g of CO₂ per visit

    6.97 g

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

Accessibility

1 to fix96
  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

SEO

6 to fixGoogle 10071
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Adcap Grupo Financiero - Soluciones Integrales de Inversión y Servicios Financieros”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Impulsando el desarrollo financiero” and “Visión en Acción”). One clear main headline is easier for people and search engines.

  • Meta description is long (335 characters)

    Your meta description is 335 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.ad-cap.com.ar/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ad-cap.com.ar/robots.txt, the first file search crawlers ask for.

  • 22 internal links, 27 external

    The homepage links to 22 pages on ad-cap.com.ar and 27 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.ad-cap.com.ar/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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.ad-cap.com.ar/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 7 pages share a title

    https://www.ad-cap.com.ar/quienes-somos, https://www.ad-cap.com.ar/adcap-en-numeros, https://www.ad-cap.com.ar/soluciones, https://www.ad-cap.com.ar/blog, https://www.ad-cap.com.ar/legales and https://www.ad-cap.com.ar/legales/politicas-de-privacidad and 1 other all use the title “Adcap Grupo Financiero”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://www.ad-cap.com.ar/quienes-somos, https://www.ad-cap.com.ar/adcap-en-numeros, https://www.ad-cap.com.ar/soluciones, https://www.ad-cap.com.ar/blog, https://www.ad-cap.com.ar/legales and https://www.ad-cap.com.ar/legales/politicas-de-privacidad and 1 other use the same meta description. A description written for each page earns more clicks.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 8 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 8 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • About 341 words of copy

    The homepage carries about 341 words of visible text.

3 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 4 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ad-cap.com.ar, including 12 speed issues, 6 SEO issues and 4 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