Website review, no card needed

innoenergy.com logo

innoenergy.com website review

Visit site (opens in a new tab)Reviewed 30 October 202627 issues · 78 checks

This review found 27 issues worth fixing on innoenergy.com, 7 of them high impact, across 78 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
7.0 s2.7 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.5 s
May 16, 20266.5 s
May 23, 20266.5 s
May 30, 20266.4 s
Jun 6, 20266.3 s
Jun 13, 20265.9 s
Jun 20, 20265.5 s
Jun 27, 20264.2 s
Jul 4, 20263.6 s
Jul 11, 20263.5 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20264.6 s
Sep 5, 20265.8 s
Sep 12, 20265.8 s
Sep 19, 20266.0 s
Sep 26, 20265.6 s
Oct 3, 20264.8 s
Oct 10, 20264.6 s
Oct 17, 20263.9 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
263 ms101 msMay 9Oct 24149 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026242 ms
May 16, 2026235 ms
May 23, 2026237 ms
May 30, 2026244 ms
Jun 6, 2026230 ms
Jun 13, 2026218 ms
Jun 20, 2026200 ms
Jun 27, 2026170 ms
Jul 4, 2026151 ms
Jul 11, 2026151 ms
Jul 18, 2026136 ms
Jul 25, 2026128 ms
Aug 1, 2026120 ms
Aug 8, 2026128 ms
Aug 15, 2026123 ms
Aug 22, 2026138 ms
Aug 29, 2026171 ms
Sep 5, 2026195 ms
Sep 12, 2026194 ms
Sep 19, 2026216 ms
Sep 26, 2026192 ms
Oct 3, 2026175 ms
Oct 10, 2026172 ms
Oct 17, 2026150 ms
Oct 24, 2026149 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 innoenergy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. innoenergy.com at 0.6 s0.6 s
  2. innoenergy.com at 1.1 s1.1 s
  3. innoenergy.com at 1.7 s1.7 s
  4. innoenergy.com at 2.2 s2.2 s
  5. innoenergy.com at 2.8 s2.8 s
  6. innoenergy.com at 3.3 s3.3 s
  7. innoenergy.com at 3.9 s3.9 s
  8. innoenergy.com at 4.4 s4.4 s

Speed

8 to fix58
  • Reduce unused JavaScript

    2.3 s · 444 KiB

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

  • Use efficient cache lifetimes

    800 ms · 279 KiB

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

  • Mobile performance score: 58

    58/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Hubspot and Cookiebot and others), adding 841 KiB and 546 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 111 KiB

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

  • Google Tag Manager adds 301 ms

    301 ms

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • 1,743 HTML elements

    The page has 1,743 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    216 KiB

    5 images could be 216 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 21 KiB

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

  • 11 long tasks on the main thread

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

8 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: 14.3 s

    14.3 s

    Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website or its third-party tools use cookies to person…”.

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

    9.3 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 229 ms

    229 ms

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

6 checks passed
  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 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 TTFB: 661 ms

    661 ms

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

  • Tap response (INP) got 37% faster for real visitors

    -37%

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

  • Largest content (LCP) got 41% faster for real visitors

    -41%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.5 s to 3.8 s 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: 5.7 MB in 62 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 62 requests on a phone: media 2.8 MB (3), scripts 1.0 MB (12) and fonts 922 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.61 g

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

3 to fixGoogle 9296
  • 12 buttons without a name

    12 buttons have no accessible name, so screen readers announce just “button”.

  • 5 links without text

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

  • 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 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 49 internal links, 6 external

    The homepage links to 49 pages on innoenergy.com and 6 external pages.

8 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “InnoEnergy is industrialising clean tech innovation for a net zero economy. We invest in startups and build industrial …”.

  • One H1 headline

    Your main headline reads: “Transitioning global energy Transforming every industry”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “InnoEnergy - Industrialising clean tech innovation”.

  • Canonical URL set

    The canonical URL is https://innoenergy.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://innoenergy.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://innoenergy.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 (890 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 8 pages without a meta description

    https://innoenergy.com/skillsinstitute/contact, https://innoenergy.com/portfolio/hardt/265770, https://innoenergy.com/portfolio/verkor/265685, https://innoenergy.com/portfolio/corpower-ocean/265713, https://innoenergy.com/portfolio/gravithy/265764 and https://innoenergy.com/portfolio/skeleton/265857 and 2 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://innoenergy.com/company-building, whose canonical is https://innoenergy.com/companybuilder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://innoenergy.com/portfolio/skeleton/265857 and https://innoenergy.com/portfolio/ecop-technologies-gmbh/265778 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://innoenergy.com/skillsinstitute/contact 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.

  • 4 pages slow to respond

    https://innoenergy.com/about-us/our-ecosystem, https://innoenergy.com/portfolio/gravithy/265764, https://innoenergy.com/portfolio/skeleton/265857 and https://innoenergy.com/portfolio/flexidao/265756 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 42 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.

  • 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 9687
  • 4 small tap targets

    4 of 17 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”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 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 1,346 words of copy

    The homepage carries about 1,346 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: “Contact us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact us”, “Learn more about who we are” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, 1 customer or partner logo, 1 trust badge and “540 + Companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 innoenergy.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
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

Company

Headquarters
Eindhoven

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on innoenergy.com, including 16 speed issues, 1 SEO issue 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