Website review, no card needed
inteligogroup.com website review
Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 75 checks
This review found 34 issues worth fixing on inteligogroup.com, 11 of them high impact, across 75 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Render-blocking requests
2.8 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused JavaScript
1.9 s · 402 KiBAbout 402 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
600 ms · 91 KiB2 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
450 ms · 149 KiBAbout 149 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Minify JavaScript
290 ms · 64 KiB64 KiB could be saved by minifying JavaScript.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 197 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Other Google APIs/SDKs), adding 205 KiB and 103 ms of main-thread time.
Duplicated JavaScript
100 ms · 2 KiB2 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
Use efficient cache lifetimes
45 KiB18 files are served with short cache lifetimes, so returning visitors download them again (45 KiB).
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 687 ms of it running JavaScript. That is comfortably low.
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner_inicio_mobile”.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.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.
Total Blocking Time: 234 ms
234 msScripts block taps and scrolling for 234 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
2 images in older formats
2 images (166 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.
1 image below the first screen load straight away
1 image further down the page (59 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 63.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 156 requests
1.9 MBYour homepage downloads 1.9 MB in 156 requests on a phone: scripts 1.2 MB (78), images 430 KiB (20) and stylesheets 180 KiB (21). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<svg> elements with an img or image role must have alternative text (4 elements)
<svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 checks passed
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 5 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 (22 characters)
Your title is only 22 characters: “Inicio - Inteligogroup”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to devpublicagroup.inteligobank.com, not inteligogroup.com, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (6 characters)
Your meta description is only 6 characters: “Inicio”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
40 internal links, 26 external
The homepage links to 40 pages on inteligogroup.com and 26 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Desarrollamos el futuro de nuestros clientes para que puedan disfrutar del presente”.
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://www.inteligogroup.com:443/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://inteligogroup.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.
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,556 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share 4 titles
https://inteligogroup.com/nosotros and https://inteligogroup.com/quienes-somos all use the title “Quiénes somos - Inteligogroup”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://inteligogroup.com/contacto and https://inteligogroup.com/formulario-de-contacto have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://inteligogroup.com/nosotros and https://inteligogroup.com/quienes-somos use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://inteligogroup.com/servicos-financieros, whose canonical is https://inteligogroup.com/servicios-financieros. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 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.
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 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://www.inteligogroup.com/o/inteligo-webpublic-group-theme/images/icons/icons.svg from f…”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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 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: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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,172 words of copy
The homepage carries about 1,172 words of visible text.
2 checks passed
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
2 other companies contacted
Loading the homepage contacts 2 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 inteligogroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Analytics
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on inteligogroup.com, including 12 speed issues, 5 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.