Website review, no card needed

innobasque.eus logo

innobasque.eus website review

Visit site (opens in a new tab)Reviewed 18 October 202624 issues · 67 checks

This review found 24 issues worth fixing on innobasque.eus, 13 of them high impact, across 67 checks. The most urgent: page weight: 15.1 MB in 56 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
10.7 s2.4 sApr 25Oct 104.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.9 s
May 2, 20264.3 s
May 9, 20264.5 s
May 16, 20264.3 s
May 23, 20264.6 s
May 30, 20264.4 s
Jun 6, 20264.3 s
Jun 13, 20268.0 s
Jun 20, 20268.7 s
Jun 27, 20269.3 s
Jul 4, 20269.8 s
Jul 11, 20268.0 s
Jul 18, 20267.3 s
Jul 25, 20267.2 s
Aug 1, 20267.1 s
Aug 8, 20266.6 s
Aug 15, 20265.9 s
Aug 22, 20265.3 s
Aug 29, 20263.8 s
Sep 5, 20263.9 s
Sep 12, 20263.4 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
255 ms135 msApr 25Oct 10184 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026156 ms
May 2, 2026149 ms
May 9, 2026155 ms
May 16, 2026155 ms
May 23, 2026159 ms
May 30, 2026171 ms
Jun 6, 2026178 ms
Jun 13, 2026210 ms
Jun 20, 2026231 ms
Jun 27, 2026230 ms
Jul 4, 2026241 ms
Jul 11, 2026222 ms
Jul 18, 2026191 ms
Jul 25, 2026186 ms
Aug 1, 2026191 ms
Aug 8, 2026174 ms
Aug 15, 2026156 ms
Aug 22, 2026162 ms
Aug 29, 2026167 ms
Sep 5, 2026183 ms
Sep 12, 2026174 ms
Sep 19, 2026171 ms
Sep 26, 2026162 ms
Oct 3, 2026175 ms
Oct 10, 2026184 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 innobasque.eus (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. innobasque.eus at 0.5 s0.5 s
  2. innobasque.eus at 1.0 s1.0 s
  3. innobasque.eus at 1.5 s1.5 s
  4. innobasque.eus at 2.0 s2.0 s
  5. innobasque.eus at 2.4 s2.4 s
  6. innobasque.eus at 2.9 s2.9 s
  7. innobasque.eus at 3.4 s3.4 s
  8. innobasque.eus at 3.9 s3.9 s

Speed

  • 4 third-party services on the page

    4 third-party services load with your homepage (Cloudflare, Google/Doubleclick Ads and Unpkg and others), adding 20 KiB and 7 ms of main-thread time.

  • 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: 0.6 s

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

  • Server response: 130 ms

    130 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.7 s

    4.7 s

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

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

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 10 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user INP: 198 ms

    198 ms

    Real visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • 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.1 MB in 56 requests

    15.1 MB

    Your homepage downloads 15.1 MB in 56 requests on a phone: media 8.4 MB (5), images 5.7 MB (28) and fonts 735 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 4.3 g of CO₂ per visit

    4.28 g

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

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

  • 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 9691
  • 6 text elements with low contrast

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

  • [role="img"] and [role="image"] elements must have alternative text (4 elements)

    [role="img"] and [role="image"] elements must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 14 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 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 10088
  • 2 H1 headlines

    There are 2 <h1> headlines (“Soy … que busca …” and “Enterprise Europe Network”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.innobasque.eus/sitemap_index.xml, so Google discovers your pages only by following links.

  • 135 internal links, 19 external

    The homepage links to 135 pages on innobasque.eus and 19 external pages.

5 checks passed
  • Meta description: 89 characters

    Your meta description is 89 characters: “Casos prácticos, tendencias, podcast... síguenos y da tu primer paso hacia la innovación.”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Agencia Vasca de la Innovación, Innobasque”.

  • Canonical URL set

    The canonical URL is https://www.innobasque.eus/.

  • Structured data in place

    Structured data found: Article, Organization, Person, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://www.innobasque.eus/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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.innobasque.eus/area/alimentacion, https://www.innobasque.eus/area/corporativo and https://www.innobasque.eus/area/ecoinnovacion have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.innobasque.eus/global-innovation-day has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.innobasque.eus/eu and https://www.innobasque.eus/te-acompanamos-a-innovar took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.innobasque.eus/.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

2 checks passed
  • Tap targets are thumb-sized

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

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

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

    The homepage carries about 767 words of visible text.

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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, 1 of them by other companies (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.

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 innobasque.eus, 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

Company

Founded
2007
Headquarters
Vizcaya Technology Park

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on innobasque.eus, including 7 speed issues, 3 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