Website review, no card needed

aruba.it logo

aruba.it website review

Visit site (opens in a new tab)Reviewed 27 October 202643 issues · 89 checks

This review found 43 issues worth fixing on aruba.it, 13 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s2.1 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
221 ms192 msMay 9Oct 24211 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026196 ms
May 16, 2026198 ms
May 23, 2026197 ms
May 30, 2026196 ms
Jun 6, 2026196 ms
Jun 13, 2026199 ms
Jun 20, 2026200 ms
Jun 27, 2026203 ms
Jul 4, 2026198 ms
Jul 11, 2026195 ms
Jul 18, 2026196 ms
Jul 25, 2026197 ms
Aug 1, 2026202 ms
Aug 8, 2026212 ms
Aug 15, 2026215 ms
Aug 22, 2026216 ms
Aug 29, 2026218 ms
Sep 5, 2026214 ms
Sep 12, 2026213 ms
Sep 19, 2026212 ms
Sep 26, 2026211 ms
Oct 3, 2026211 ms
Oct 10, 2026210 ms
Oct 17, 2026211 ms
Oct 24, 2026211 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

Full-page screenshot of aruba.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aruba.it at 0.5 s0.5 s
  2. aruba.it at 0.9 s0.9 s
  3. aruba.it at 1.4 s1.4 s
  4. aruba.it at 1.8 s1.8 s
  5. aruba.it at 2.3 s2.3 s
  6. aruba.it at 2.7 s2.7 s
  7. aruba.it at 3.2 s3.2 s
  8. aruba.it at 3.6 s3.6 s

Speed

7 to fix60
  • Render-blocking requests

    2.6 s

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

  • 4,881 HTML elements

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused JavaScript

    460 ms · 128 KiB

    About 128 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Reduce unused CSS

    480 ms · 83 KiB

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

  • Use efficient cache lifetimes

    300 ms · 133 KiB

    53 files are served with short cache lifetimes, so returning visitors download them again (133 KiB).

  • 4 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, cookiebot.eu and Usabilla and others), adding 330 KiB and 253 ms of main-thread time.

  • Legacy JavaScript

    100 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Improve image delivery

    63 KiB

    1 image could be 63 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 91 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 248 ms

    248 ms

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

Core Web Vitals

8 to fix100
  • 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: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To offer you an ever better browsing experience, this websi…”.

  • Time to Interactive: 8.9 s

    8.9 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user TTFB: 816 ms

    816 ms

    Real visitors wait 816 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 223 ms

    223 ms

    Scripts block taps and scrolling for 223 ms in total while the page loads. Good is under 200 ms.

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 196 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 179 ms

    179 ms

    Real visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix90
  • 4 images in older formats

    4 images (536 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.4 g of CO₂ per visit

    0.43 g

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

3 checks passed
  • Page weight: 1.5 MB in 69 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 69 requests on a phone: images 820 KiB (32), scripts 456 KiB (18) and fonts 120 KiB (5). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9090
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 3 text elements with low contrast

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

  • 2 images without alt text

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

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

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

8 to fixGoogle 7763
  • No meta description

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

  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “Home | Aruba.it”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 14 links with vague text

    14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 11 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 54 internal links, 145 external

    The homepage links to 54 pages on aruba.it and 145 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://aruba.it/en/home.aspx.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aruba.it/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles) and description. 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://www.aruba.it/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,882 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://www.aruba.it/en/press-kit.aspx is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://www.aruba.it/en/home.aspx and https://www.aruba.it/es/home.aspx all use the title “Home | Aruba.it”, and 1 other title repeat too. 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://www.aruba.it/es/home.aspx has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.aruba.it/en/certifications.aspx and https://www.aruba.it/en/certification.aspx use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aruba.it/en/certification.aspx, whose canonical is https://www.aruba.it/en/certifications.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.aruba.it/es/home.aspx has 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 27 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8191
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Permissions policy violation: picture-in-picture is not allowed in this document.”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 1,262 words of copy

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

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “LEARN MORE”, “Request support” and “Request sales info”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Matomo.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 4 cookies set on arrival

    4

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

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager | Matomo
Hosting
Aruba

Company

Employees
900
Founded
1994
Headquarters
Ponte San Pietro

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on aruba.it, including 15 speed issues, 8 SEO issues and 2 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

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