Website review, no card needed

almaviva.it logo

almaviva.it website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 57 checks

This review found 33 issues worth fixing on almaviva.it, 13 of them high impact, across 57 checks. The most urgent: mobile performance score: 34. 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
5.2 s4.2 sSep 26Oct 314.3 s
Show as table
DateReal-visitor load time (LCP)
Sep 26, 20265.1 s
Oct 3, 20264.9 s
Oct 10, 20264.8 s
Oct 17, 20264.7 s
Oct 24, 20264.6 s
Oct 31, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
144 ms129 msSep 26Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
Sep 26, 2026142 ms
Oct 3, 2026131 ms
Oct 10, 2026131 ms
Oct 17, 2026135 ms
Oct 24, 2026131 ms
Oct 31, 2026138 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 almaviva.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. almaviva.it at 0.6 s0.6 s
  2. almaviva.it at 1.2 s1.2 s
  3. almaviva.it at 1.9 s1.9 s
  4. almaviva.it at 2.5 s2.5 s
  5. almaviva.it at 3.1 s3.1 s
  6. almaviva.it at 3.7 s3.7 s
  7. almaviva.it at 4.4 s4.4 s
  8. almaviva.it at 5.0 s5.0 s

Speed

6 to fix34
  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    1.4 MB

    16 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 long tasks on the main thread

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

  • Render-blocking requests

    600 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Reduce unused JavaScript

    460 ms · 89 KiB

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

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • Use efficient cache lifetimes

    35 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (35 KiB).

  • 1 third-party service on the page

    1 third-party service load with your homepage (gruppoalmaviva.it), adding 35 KiB and 15 ms of main-thread time.

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 1.27

    1.27

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Cumulative Layout Shift: 1.708

    1.708

    The layout shifts by 1.708 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 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 (4.6 s).

  • Real-user TTFB: 886 ms

    886 ms

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

  • Total Blocking Time: 538 ms

    538 ms

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

  • Time to Interactive: 6.8 s

    6.8 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user INP: 144 ms

    144 ms

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix33
  • Page weight: 5.6 MB in 75 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 75 requests on a phone: images 3.0 MB (29), media 1.9 MB (1) and scripts 347 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.58 g

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

Accessibility

3 to fixGoogle 9685
  • 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.

  • 44 tap targets too small

    44 tap targets are too small or too close together to hit reliably with a finger.

1 checks passed
  • 7 automated accessibility rules passed

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

SEO

5 to fixGoogle 10073
  • No H1 headline

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

  • Title is short (20 characters)

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

4 checks passed
  • Meta description: 70 characters

    Your meta description is 70 characters: “Almaviva provides innovative digital solutions and technology services”.

  • 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://www.almavivagroup.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://www.almavivagroup.com/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.

Best practices

1 to fixGoogle 10092
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “ERROR TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 almaviva.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Hosting
AWS

Company

Founded
2005
Headquarters
Rome

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on almaviva.it, including 16 speed issues, 5 SEO issues and 6 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