Website review, no card needed

indigo.pt logo

indigo.pt website review

Visit site (opens in a new tab)Reviewed 22 October 202626 issues · 71 checks

This review found 26 issues worth fixing on indigo.pt, 9 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of indigo.pt (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. indigo.pt at 1.4 s1.4 s
  2. indigo.pt at 2.7 s2.7 s
  3. indigo.pt at 4.1 s4.1 s
  4. indigo.pt at 5.4 s5.4 s
  5. indigo.pt at 6.8 s6.8 s
  6. indigo.pt at 8.1 s8.1 s
  7. indigo.pt at 9.5 s9.5 s
  8. indigo.pt at 10.8 s10.8 s

Speed

5 to fix57
  • Use efficient cache lifetimes

    1.1 s · 1.0 MB

    49 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

  • Render-blocking requests

    1.5 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Reduce unused JavaScript

    1.1 s · 237 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    447 KiB

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

  • 6 third-party services on the page

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

  • Reduce unused CSS

    150 ms · 30 KiB

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

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 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.6 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 9.7 s

    9.7 s

    Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (8.9 s).

  • Speed Index: 18.0 s

    18.0 s

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

  • Time to Interactive: 11.1 s

    11.1 s

    The page becomes fully interactive after 11.1 s. Good is under 3.8 s.

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • 20 images without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 63 ms

    63 ms

    Scripts block the page for only 63 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix83
  • 5 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (545 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.

  • About 0.5 g of CO₂ per visit

    0.55 g

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

    1.9 MB

    Your homepage downloads 1.9 MB in 63 requests on a phone: images 1.1 MB (30), scripts 588 KiB (17) and fonts 179 KiB (4). 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

4 to fixGoogle 8893
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (14 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Indigo - Digital Transformation accelerated by OutSystems Low-Code”.

  • Meta description is long (240 characters)

    Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No robots.txt

    There is no robots.txt at indigo.pt/robots.txt, the first file search crawlers ask for.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 30 internal links, 3 external

    The homepage links to 30 pages on indigo.pt and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://indigo.pt/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://indigo.pt/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

4 to fix81
  • 2 pages share a title

    https://indigo.pt/about-us and https://indigo.pt/indigo-multimedia-hub all use the title “About Indigo - Digital Transformation accelerated by OutSystems”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://indigo.pt/fundo-europeu-desenvolvimento has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://indigo.pt/about-us and https://indigo.pt/indigo-multimedia-hub use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://indigo.pt/about-us, https://indigo.pt/indigo-multimedia-hub, https://indigo.pt/careers-indigo, https://indigo.pt/contact-us-indigo, https://indigo.pt/indigo-free-edition-campaign and https://indigo.pt/fundo-europeu-desenvolvimento and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://indigo.pt/about-us, https://indigo.pt/indigo-multimedia-hub, https://indigo.pt/careers-indigo and https://indigo.pt/contact-us-indigo took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    8 pages of 12 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • 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 477 words of copy

    The homepage carries about 477 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”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Start Your AI-Enabled Journey”.

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics, HubSpot and Cloudflare Web Analytics.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

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

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 indigo.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on indigo.pt, including 10 speed issues, 5 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

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