Website review, no card needed

nucleusdoc.com.ar logo

nucleusdoc.com.ar website review

Visit site (opens in a new tab)Reviewed 8 November 202644 issues · 85 checks

This review found 44 issues worth fixing on nucleusdoc.com.ar, 13 of them high impact, across 85 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
2.2 s1.6 sMay 16Sep 261.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 13, 20262.1 s
Jul 4, 20262.1 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s

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 nucleusdoc.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix53
  • Reduce unused JavaScript

    6.0 s · 999 KiB

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

  • Use efficient cache lifetimes

    3.0 s · 1.5 MB

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

  • Improve image delivery

    8.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, hsappstatic.net and Google Tag Manager and others), adding 2.5 MB and 1.1 s of main-thread time.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 359 ms

    359 ms

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

  • hsappstatic.net adds 302 ms

    302 ms

    hsappstatic.net costs a phone 302 ms of main-thread work and 732 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.

  • Main-thread work: 3.2 s

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

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Render-blocking requests

    300 ms

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

  • Reduce unused CSS

    250 ms · 37 KiB

    About 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • Minify JavaScript

    6 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

5 to fix65
  • First Contentful Paint: 12.8 s

    12.8 s

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

  • Largest Contentful Paint: 42.4 s

    42.4 s

    Your largest element takes 42.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Desarrollamos soluciones tecnológicas para Recursos Humanos…”.

  • Time to Interactive: 45.4 s

    45.4 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 157 ms

    157 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 13.8 MB in 109 requests

    13.8 MB

    Your homepage downloads 13.8 MB in 109 requests on a phone: images 10.5 MB (33), scripts 2.5 MB (36) and other files 401 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    152 KiB

    1 image is downloaded at several times the size a phone draws it, for example imagen_grafico1.png at 1,801 px wide, shown at 360 px. Resized copies would save about 152 KiB.

  • About 3.9 g of CO₂ per visit

    3.91 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

Accessibility

11 to fixGoogle 8689
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 8 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 8571
  • No meta description

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

  • Title is short (14 characters)

    Your title is only 14 characters: “Nucleus | Home”. 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 48 internal links, 41 external

    The homepage links to 48 pages on nucleusdoc.com.ar and 41 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://nucleus.com.ar/.

  • 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://bmoargentina.com.ar/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    45%

    The HTML your server sends has 8,470 of the 18,917 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://nucleus.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.

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

Other pages

4 to fix78
  • 6 pages share 3 titles

    https://nucleus.com.ar/soluciones/administracion-de-personal and https://nucleus.com.ar/nucleus-hr/soluciones/administracion-de-personal all use the title “Nucleus | Administración de personal”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://nucleus.com.ar/soluciones/administracion-de-personal, https://nucleus.com.ar/soluciones/payroll, https://nucleus.com.ar/soluciones/gestion-del-talento, https://nucleus.com.ar/documentos-digitales, https://nucleus.com.ar/gestion-documental-digital/soluciones and https://nucleus.com.ar/firma-digital and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://nucleus.com.ar/nucleus-hr/soluciones/administracion-de-personal, whose canonical is https://nucleus.com.ar/soluciones/administracion-de-personal. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://nucleus.com.ar/soluciones/administracion-de-personal, https://nucleus.com.ar/soluciones/payroll, https://nucleus.com.ar/soluciones/gestion-del-talento, https://nucleus.com.ar/gestion-documental-digital/soluciones, https://nucleus.com.ar/firma-digital and https://nucleus.com.ar/partners and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://nucleus.com.ar/nucleus-hr/soluciones/administracion-de-personal, https://nucleus.com.ar/nucleus-hr/soluciones/payroll, https://nucleus.com.ar/nucleus-hr/soluciones/gestion-del-talento and https://nucleus.com.ar/nucleus-hr took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7389
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 18,917 words of copy

    The homepage carries about 18,917 words of visible text.

2 checks passed
  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 9 of them by other companies (measured from a US location before any click).

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 nucleusdoc.com.ar, 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 44 issues on nucleusdoc.com.ar, including 15 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