innowi.com website review

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

3 images are downloaded at several times the size a phone draws them, for example Rancho-Steves-02-538x1024.webp at 390 px wide, shown at 107 px. Resized copies would save about 66 KiB.

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

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

47 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is only 13 characters: “Home - Innowi”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 70 pages on innowi.com and 12 external pages.

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.

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

https://innowi.com/products/ordering-channel-product, https://innowi.com/products/self-serve-kiosk, https://innowi.com/products/ai-phone-ordering, https://innowi.com/products/table-ordering, https://innowi.com/products/branded-websites and https://innowi.com/products/restaurant-pos and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://innowi.com/products/ordering-channel-product, https://innowi.com/products/self-serve-kiosk, https://innowi.com/products/ai-phone-ordering, https://innowi.com/products/table-ordering, https://innowi.com/products/branded-websites and https://innowi.com/products/restaurant-pos and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://innowi.com/case-studies 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.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,870 words of visible text.

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

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

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