Website review, no card needed

aportesenlinea.com logo

aportesenlinea.com website review

Visit site (opens in a new tab)Reviewed 31 October 202646 issues · 84 checks

This review found 46 issues worth fixing on aportesenlinea.com, 21 of them high impact, across 84 checks. The most urgent: improve image delivery. 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.5 s2.1 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
198 ms183 msMay 9Oct 24196 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026192 ms
May 16, 2026193 ms
May 23, 2026192 ms
May 30, 2026193 ms
Jun 6, 2026194 ms
Jun 13, 2026193 ms
Jun 20, 2026192 ms
Jun 27, 2026191 ms
Jul 4, 2026191 ms
Jul 11, 2026189 ms
Jul 18, 2026188 ms
Jul 25, 2026187 ms
Aug 1, 2026187 ms
Aug 8, 2026186 ms
Aug 15, 2026186 ms
Aug 22, 2026185 ms
Aug 29, 2026185 ms
Sep 5, 2026186 ms
Sep 12, 2026187 ms
Sep 19, 2026187 ms
Sep 26, 2026188 ms
Oct 3, 2026190 ms
Oct 10, 2026193 ms
Oct 17, 2026195 ms
Oct 24, 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 aportesenlinea.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix36
  • Improve image delivery

    9.6 s · 2.5 MB

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

  • Avoid multiple page redirects

    8.0 s

    The page goes through 1 redirect before it starts loading, costing about 8.0 s. Link and advertise the final URL directly.

  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    2.7 s · 348 KiB

    About 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.5 s · 446 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Google Tag Manager adds 311 ms

    311 ms

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

  • Minify CSS

    300 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Main-thread work: 2.0 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google/Doubleclick Ads and others), adding 400 KiB and 332 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 38.6 s

    38.6 s

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

  • Time to Interactive: 38.8 s

    38.8 s

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

  • Cumulative Layout Shift: 0.594

    0.594

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • 35 images without width and height

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

  • Total Blocking Time: 373 ms

    373 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

4 checks passed
  • Real-user INP: 194 ms

    194 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 640 ms

    640 ms

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

Images and page weight

4 to fix36
  • Page weight: 8.2 MB in 236 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 236 requests on a phone: images 5.7 MB (64), scripts 1.5 MB (126) and fonts 548 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 6 images in older formats

    6 images (4.5 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.

  • An image on the first screen is lazy-loaded

    30ba7cdd-db83-c0cf-343c-5c88e9ffba55 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).

  • About 2.3 g of CO₂ per visit

    2.33 g

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

6 to fixGoogle 8990
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271
  • No H1 headline

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Inicio - Aportes en Línea”. 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.

  • Meta description is long (181 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 63 internal links, 17 external

    The homepage links to 63 pages on aportesenlinea.com and 17 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.aportesenlinea.com/.

  • 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.aportesenlinea.com:443/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.aportesenlinea.com/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 (738 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix70
  • 1 linked page hidden from search

    https://www.aportesenlinea.com/cont%C3%A1ctenos is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share 2 titles

    /, https://www.aportesenlinea.com/empresas/inicio, https://www.aportesenlinea.com/independientes/inicio and https://www.aportesenlinea.com/datos-en-linea/inicio all use the title “Inicio - Aportes en Línea”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.aportesenlinea.com/empresas/inicio, https://www.aportesenlinea.com/qui%C3%A9nes-somos, https://www.aportesenlinea.com/cont%C3%A1ctenos, https://www.aportesenlinea.com/independientes/inicio, https://www.aportesenlinea.com/cont%C3%A1ctenos1 and https://www.aportesenlinea.com/datos-en-linea/inicio and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aportesenlinea.com/puntos-fisicos, whose canonical is https://www.aportesenlinea.com/presencial. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.aportesenlinea.com/empresas/inicio, https://www.aportesenlinea.com/cont%C3%A1ctenos, https://www.aportesenlinea.com/independientes/inicio, https://www.aportesenlinea.com/cont%C3%A1ctenos1, https://www.aportesenlinea.com/datos-en-linea/inicio and https://www.aportesenlinea.com/centro-de-ayuda and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.aportesenlinea.com/cont%C3%A1ctenos1 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8591
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://s.go-mpulse.net/boomerang/W8N2E-C48M4-SNMPD-SSBL9-H29GP' violates the following Content Sec…”.

  • 3 distorted images

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

  • 9 low-resolution images

    9 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 318 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 11 cookies set on arrival

    11

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on aportesenlinea.com, including 18 speed issues, 5 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