Website review, no card needed
almavivagroup.com website review
Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 55 checks
This review found 34 issues worth fixing on almavivagroup.com, 13 of them high impact, across 55 checks. The most urgent: mobile performance score: 40. 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
57FClosest 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.5 s
4.1 s
4.7 s
Speed
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.4 MB20 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
460 ms · 89 KiBAbout 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 410 ms. During a long task the page ignores taps.
Reduce unused CSS
310 ms · 40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Use efficient cache lifetimes
35 KiB1 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 9 ms of main-thread time.
Phones get a much slower page than desktops
Desktop scores 77 but mobile only 40. 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.25
1.25For real visitors the layout shifts by 1.25 (75th percentile). Good is under 0.1.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 1.535
1.535The layout shifts by 1.535 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 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 (3.9 s).
Real-user TTFB: 952 ms
952 msReal visitors wait 952 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 229 ms
229 msScripts block taps and scrolling for 229 ms in total while the page loads. Good is under 200 ms.
1 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 6.8 MB in 78 requests
6.8 MBYour homepage downloads 6.8 MB in 78 requests on a phone: images 4.2 MB (32), media 1.9 MB (1) and scripts 347 KiB (30). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.91 g of CO₂e: 229.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
37 tap targets too small
37 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
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
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
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
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
1Opening 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 almavivagroup.com, 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
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 almavivagroup.com, including 17 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.