Website review, no card needed

infocaformacion.com logo

infocaformacion.com website review

Visit site (opens in a new tab)Reviewed 23 October 202644 issues · 84 checks

This review found 44 issues worth fixing on infocaformacion.com, 14 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
5.0 s2.6 sMay 2Oct 32.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.3 s
May 9, 20264.4 s
May 16, 20264.5 s
May 23, 20264.5 s
May 30, 20264.8 s
Sep 19, 20263.2 s
Oct 3, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
125 ms105 msMay 2Oct 3107 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026121 ms
May 9, 2026123 ms
May 16, 2026119 ms
May 23, 2026116 ms
May 30, 2026119 ms
Oct 3, 2026107 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 infocaformacion.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. infocaformacion.com at 1.4 s1.4 s
  2. infocaformacion.com at 2.8 s2.8 s
  3. infocaformacion.com at 4.3 s4.3 s
  4. infocaformacion.com at 5.7 s5.7 s
  5. infocaformacion.com at 7.1 s7.1 s
  6. infocaformacion.com at 8.5 s8.5 s
  7. infocaformacion.com at 9.9 s9.9 s
  8. infocaformacion.com at 11.4 s11.4 s

Speed

10 to fix46
  • Use efficient cache lifetimes

    4.2 s · 3.9 MB

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

  • Render-blocking requests

    4.0 s

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

  • Mobile performance score: 46

    46/100

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

  • Improve image delivery

    600 ms · 702 KiB

    10 images could be 702 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and clientify.net and others), adding 882 KiB and 753 ms of main-thread time.

  • Google CDN adds 669 ms

    669 ms

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

  • Reduce unused CSS

    450 ms · 137 KiB

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

  • Reduce unused JavaScript

    517 KiB

    About 517 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.9 s

    A phone's processor spends 3.9 s on main-thread work while loading, 1.6 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).

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 46. 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix51
  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your 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 text “INFOCA Tu proveedor de formación”.

  • Time to Interactive: 16.0 s

    16.0 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 552 ms

    552 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 121 ms to 107 ms 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
  • Largest content (LCP) got 30% faster for real visitors

    -30%

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

3 to fix45
  • Page weight: 12.9 MB in 173 requests

    12.9 MB

    Your homepage downloads 12.9 MB in 173 requests on a phone: media 7.8 MB (1), images 3.0 MB (28) and scripts 1.1 MB (55). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    FORMACION-SUBVENCIONADA.png weighs 705 KiB. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (1.9 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.

  • 2 images below the first screen load straight away

    2 images further down the page (57 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.7 g of CO₂ per visit

    3.65 g

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

9 to fixGoogle 8991
  • 3 text elements with low contrast

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

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

  • 7 links without text

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 8578
  • No meta description

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

  • Title is short (23 characters)

    Your title is only 23 characters: “Home - Infoca Formación”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Fórmate con Infoca”, “Infoca” and “Infoca”). One clear main headline is easier for people and search engines.

  • 51 internal links, 20 external

    The homepage links to 51 pages on infocaformacion.com and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://infocaformacion.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

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

  • 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://infocaformacion.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

5 to fix53
  • 1 linked page is broken

    Your homepage links to https://infocaformacion.com/quienes-somos, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages share 2 titles

    https://infocaformacion.com/jardineria and https://infocaformacion.com/cursos/jardineria all use the title “Jardinería - Infoca Formación”, and 1 other title 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://infocaformacion.com/jardineria, https://infocaformacion.com/mantenimiento, https://infocaformacion.com/formacion-acreditada, https://infocaformacion.com/empresas/planes-para-empresas, https://infocaformacion.com/nuestros-clientes and https://infocaformacion.com/certificacion and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://infocaformacion.com/cursos/jardineria, whose canonical is https://infocaformacion.com/jardineria. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://infocaformacion.com/empresas/formacion-bonificada-empresas and https://infocaformacion.com/contacto have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://infocaformacion.com/empresas/formacion-bonificada-empresas, https://infocaformacion.com/blog, https://infocaformacion.com/curso/legionella, https://infocaformacion.com/curso/fitosanitarios-cualificado, https://infocaformacion.com/cursos/jardineria and https://infocaformacion.com/cursos/mantenimiento took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 175 words

    The homepage has only about 175 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.

Privacy and tracking

  • 10 cookies set on arrival

    10

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 infocaformacion.com, 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
jQuery
E-commerce
WooCommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on infocaformacion.com, including 16 speed issues, 3 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

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