Website review, no card needed

gcpglobal.com logo

gcpglobal.com website review

Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 79 checks

This review found 28 issues worth fixing on gcpglobal.com, 11 of them high impact, across 79 checks. The most urgent: render-blocking 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
3.5 s2.5 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.4 s
May 23, 20263.2 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20262.6 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20262.7 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20262.9 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
240 ms56 msMay 23Oct 378 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026219 ms
May 30, 2026212 ms
Jun 6, 2026183 ms
Jun 13, 2026180 ms
Sep 19, 202677 ms
Sep 26, 202677 ms
Oct 3, 202678 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 gcpglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gcpglobal.com at 0.6 s0.6 s
  2. gcpglobal.com at 1.3 s1.3 s
  3. gcpglobal.com at 1.9 s1.9 s
  4. gcpglobal.com at 2.6 s2.6 s
  5. gcpglobal.com at 3.2 s3.2 s
  6. gcpglobal.com at 3.8 s3.8 s
  7. gcpglobal.com at 4.5 s4.5 s
  8. gcpglobal.com at 5.1 s5.1 s

Speed

5 to fix66
  • Render-blocking requests

    2.3 s

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

  • Reduce unused JavaScript

    1.1 s · 455 KiB

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

  • Reduce unused CSS

    1.1 s · 202 KiB

    About 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 66

    66/100

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

  • Google Tag Manager adds 394 ms

    394 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Clarity and Google/Doubleclick Ads and others), adding 703 KiB and 457 ms of main-thread time.

  • Improve image delivery

    200 ms · 93 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    14 KiB

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

  • Use efficient cache lifetimes

    10 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (10 KiB).

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 51 ms

    51 ms

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

Core Web Vitals

9 to fix50
  • 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 FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “El software GRC que transforma tus riesgos en oportunidades”.

  • Time to Interactive: 10.3 s

    10.3 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 215 ms

    215 ms

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

3 checks passed
  • 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 64% faster for real visitors

    -64%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 219 ms to 78 ms 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).

Images and page weight

1 to fix70
  • Page weight: 15.8 MB in 73 requests

    15.8 MB

    Your homepage downloads 15.8 MB in 73 requests on a phone: media 13.4 MB (1), images 961 KiB (35) and scripts 901 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 4.5 g of CO₂ per visit

    4.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.47 g of CO₂e: 536.5 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9094
  • 13 text elements with low contrast

    13 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 (8 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Headings should not be empty (3 elements)

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

  • Headings skip levels

    Headings skip levels (h2 → h5), 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. (8 elements).

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, SearchAction and WebPage) but with 1 problem, for example “Organization: missing name”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 30 internal links, 4 external

    The homepage links to 30 pages on gcpglobal.com and 4 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “ORCA GRC es una plataforma que centraliza la gestión de riesgos, cumplimiento y terceros, automatizando controles y mej…”.

  • One H1 headline

    Your main headline reads: “El software GRC que transforma tus riesgos en oportunidades”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Software GRC para Gobierno, Riesgo y Cumplimiento | ORCA GRC”.

  • Canonical URL set

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

  • 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://orcagrc.com/sitemaps.xml.

AI search readiness

100
4 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 url, logo, sameAs (social profiles) and description; name and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://orcagrc.com/llms.txt (3 KiB, 25 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://orcagrc.com/blog/author/jose is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://orcagrc.com/nosotros, https://orcagrc.com/especialista-orca, https://orcagrc.com/blog/author/jose and https://orcagrc.com/blog/incumplimiento-de-contrato have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://orcagrc.com/manufactura, https://orcagrc.com/nosotros, https://orcagrc.com/especialista-orca, https://orcagrc.com/blog/author/jose, https://orcagrc.com/blog/https-blog-orcagrc-com-pasos-evaluacion-seleccion-proveedores and https://orcagrc.com/blog/incumplimiento-de-contrato have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 554 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “WhatsApp Contact”.

  • 1 call to action

    The homepage has 1 call to action, for example “Solicitar Demo”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 gcpglobal.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
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on gcpglobal.com, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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