Website review, no card needed
sodalisgroup.com website review
Visit site (opens in a new tab)Reviewed 26 October 202626 issues · 72 checks
This review found 26 issues worth fixing on sodalisgroup.com, 12 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.3 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 138 ms |
| May 9, 2026 | 130 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 113 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 97 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 99 ms |
| Sep 19, 2026 | 83 ms |
| Sep 26, 2026 | 83 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 78 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
How it loaded on a phone
1.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.8 s
7.8 s
Speed
Use efficient cache lifetimes
11.3 s · 92.7 MB153 files are served with short cache lifetimes, so returning visitors download them again (92.7 MB).
Improve image delivery
9.6 s · 4.1 MB11 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.6 s faster on a phone.
Render-blocking requests
3.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 37). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 105 KiBAbout 105 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
300 ms · 53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,865 HTML elements
The page has 1,865 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Cookiebot, Google Tag Manager and Google Fonts), adding 395 KiB and 150 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.
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: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 206 ms of it running JavaScript. That is comfortably low.
Server response: 160 ms
160 msYour server sent the HTML in 160 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 48.3 s
48.3 sYour largest element takes 48.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 51.5 s
51.5 sThe page becomes fully interactive after 51.5 s. Good is under 3.8 s.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
89 images without width and height
89 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 70 ms
70 msReal visitors wait 70 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 348 ms
348 msReal visitors wait 348 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 138 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 93.1 MB in 167 requests
93.1 MBYour homepage downloads 93.1 MB in 167 requests on a phone: images 92.5 MB (148), scripts 448 KiB (6) and fonts 75 KiB (3). Under 2 MB keeps phones on slow connections fast.
40 images over 500 KB
40 images weigh 50.9 MB together. On a phone connection a single image that size takes seconds.
39 images far larger than shown
25.1 MB39 images are downloaded at several times the size a phone draws them, for example 8009518498578_Milano Red Mat_rossetto_modella.png at 2,480 px wide, shown at 230 px. Resized copies would save about 25.1 MB.
40 images in older formats
40 images (50.9 MB) 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.
37 images below the first screen load straight away
37 images further down the page (46.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 26.4 g of CO₂ per visit
26.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 26.39 g of CO₂e: 3166.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 143 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
153 internal links, 4 external
The homepage links to 153 pages on sodalisgroup.com and 4 external pages.
6 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Ideiamo, realizziamo e sviluppiamo piccole grandi creazioni di Benessere per un presente e un futuro migliori.”.
One H1 headline
Your main headline reads: “Creatori di Benessere”.
Title: 37 characters
Your title is a healthy 37 characters: “Sodalis Group - Creatori di benessere”.
Canonical URL set
The canonical URL is https://sodalisgroup.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://sodalisgroup.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.
No llms.txt
There is no https://sodalisgroup.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 (4,297 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://sodalisgroup.com/filosofia and https://sodalisgroup.com/news have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 145 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
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: 2 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 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 618 words of copy
The homepage carries about 618 words of visible text.
1 checks passed
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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
5 other companies contacted
Loading the homepage contacts 5 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 sodalisgroup.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
- 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 sodalisgroup.com, including 12 speed issues, 2 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.