Website review, no card needed
innowave.tech website review
Visit site (opens in a new tab)Reviewed 17 November 202615 issues · 55 checks
This review found 15 issues worth fixing on innowave.tech, 5 of them high impact, across 55 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- 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.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.3 s |
| Jun 6, 2026 | 5.5 s |
| Jun 13, 2026 | 5.5 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.5 s |
| Jul 18, 2026 | 5.3 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.4 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.3 s |
| Oct 31, 2026 | 4.5 s |
| Nov 7, 2026 | 4.7 s |
| Nov 14, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 132 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 105 ms |
| Oct 24, 2026 | 106 ms |
| Oct 31, 2026 | 106 ms |
| Nov 7, 2026 | 104 ms |
| Nov 14, 2026 | 110 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.1 s
3.1 sReal visitors wait 3.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.3 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 2.3 MB
2.3 MBYour homepage downloads 2.3 MB on a phone, 1.5 MB of it images (63%). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (460 KiB) 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 (64 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 78.7 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
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Homepage InnoWave - InnoWave”. Between 30 and 65 characters leaves room to say what you do and for whom.
5 H1 headlines
There are 5 <h1> headlines (“The Human Side of Innovation | EP. 4. Leadership,…”, “From Sensor Signal to Self-Running Enterprise: Ho…” and “The hard part isn’t adopting AI, it’s knowing wha…”). One clear main headline is easier for people and search engines.
123 internal links, 12 external
The homepage links to 123 pages on innowave.tech and 12 external pages.
6 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “InnoWave is a AI-driven globalconsulting companyWe empower business to shape the future through a culture of innovation.”.
Canonical URL set
The canonical URL is https://innowave.tech/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://innowave.tech/wp-sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://innowave.tech/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,213 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages slow to respond
https://innowave.tech/digital-experiences and https://innowave.tech/data-intelligence took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
7 checks passed
Linked pages load
2 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 2 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 14 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
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 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,008 words of copy
The homepage carries about 1,008 words of visible text.
5 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Get in touch”, “GET IN TOUCH” and “Contact Us”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 10 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
5 other companies contacted
Loading the homepage contacts 5 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 innowave.tech, 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 Tag Manager
- Hosting
- netcup GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on innowave.tech, including 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.