Website review, no card needed
itineris.net website review
Visit site (opens in a new tab)Reviewed 19 November 202624 issues · 66 checks
This review found 24 issues worth fixing on itineris.net, 7 of them high impact, across 66 checks. The most urgent: render-blocking requests. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 121 ms |
| Oct 31, 2026 | 130 ms |
| Nov 7, 2026 | 133 ms |
| Nov 14, 2026 | 136 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
Render-blocking requests
1.7 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 421 KiBAbout 421 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
450 ms · 209 KiBAbout 209 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.
8 third-party services on the page
8 third-party services load with your homepage (Cookiebot, Facebook and Google CDN and others), adding 2.5 MB and 339 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 243 KiB8 files are served with short cache lifetimes, so returning visitors download them again (243 KiB).
2,195 HTML elements
The page has 2,195 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
b-cdn.net adds 0 ms
0 msb-cdn.net costs a phone 0 ms of main-thread work and 1.8 MB 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.
Google CDN adds 64 ms
64 msGoogle CDN costs a phone 64 ms of main-thread work and 352 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.
Improve image delivery
120 KiB2 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 420 ms of it running JavaScript. That is comfortably low.
Server response: 264 ms
264 msYour server sent the HTML in 264 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 136 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-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.057
0.057The layout barely moves while loading (CLS 0.057, good is under 0.1).
Total Blocking Time: 66 ms
66 msScripts block the page for only 66 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 196 requests
4.1 MBYour homepage downloads 4.1 MB in 196 requests on a phone: images 2.2 MB (68), scripts 1.3 MB (101) and fonts 318 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 138.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
4 elements have a tabindex above 0, which scrambles the keyboard order.
1 checks passed
Every image has alt text
All 56 images in the HTML carry an alt attribute.
SEO
4 H1 headlines
There are 4 <h1> headlines (“UMAX Utility Suite”, “100% focused on utilities” and “Careers at Itineris”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
117 internal links, 4 external
The homepage links to 117 pages on itineris.net and 4 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Future-proof your utility with UMAX by Itineris: AI-powered CIS, CRM & ERP solutions to streamline operations and delig…”.
Title: 50 characters
Your title is a healthy 50 characters: “Itineris | AI-powered CIS, CRM & ERP for utilities”.
Canonical URL set
The canonical URL is https://itineris.net/.
Structured data in place
Structured data found: ImageObject, Organization, Place, 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://itineris.net/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://itineris.net/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.
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.
Other pages
1 linked page is broken
Your homepage links to https://itineris.net/global/solutionsforutilities/umax-and-ai, which answers with an error. Visitors hit a dead end and search engines drop it.
14 pages without an H1
https://itineris.net/global/news-and-insights, https://itineris.net/global/contact-us, https://itineris.net/north-america, https://itineris.net/global/solutionsforutilities, https://itineris.net/global/solutionsforutilities/umax-customer-platform and https://itineris.net/global/solutionsforutilities/umax-real-time and 8 others 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 59 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,122 words of copy
The homepage carries about 1,122 words of visible text.
5 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact us”, “Contact Us” and “Learn more about UMAX & AI”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 29 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Phone number on the homepage
Your phone number is on the homepage.
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 itineris.net, 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
- Combell NV
Company
- Headquarters
- Sint-Martens-Latem
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 itineris.net, including 16 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.