Website review, no card needed
adibody.it website review
Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 72 checks
This review found 26 issues worth fixing on adibody.it, 8 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. 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
76C- #75,209 of 123,879 reviewed websitesbeats 35%
- #48,194 of 69,698 online storesbeats 26%
- #45,657 of 63,406 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 234 ms |
| May 23, 2026 | 222 ms |
| May 30, 2026 | 219 ms |
| Jun 6, 2026 | 225 ms |
| Jun 13, 2026 | 239 ms |
| Jun 20, 2026 | 248 ms |
| Jun 27, 2026 | 252 ms |
| Jul 4, 2026 | 260 ms |
| Jul 11, 2026 | 242 ms |
| Jul 18, 2026 | 238 ms |
| Jul 25, 2026 | 244 ms |
| Aug 1, 2026 | 254 ms |
| Aug 8, 2026 | 280 ms |
| Aug 15, 2026 | 296 ms |
| Aug 22, 2026 | 308 ms |
| Aug 29, 2026 | 322 ms |
| Sep 5, 2026 | 318 ms |
| Sep 12, 2026 | 309 ms |
| Sep 19, 2026 | 305 ms |
| Sep 26, 2026 | 307 ms |
| Oct 3, 2026 | 315 ms |
| Oct 10, 2026 | 341 ms |
| Oct 17, 2026 | 352 ms |
| Oct 24, 2026 | 348 ms |
| Oct 31, 2026 | 341 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
Speed
Reduce unused JavaScript
1.5 s · 202 KiBAbout 202 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Improve image delivery
150 ms · 1.6 MB3 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 149 KiB9 files are served with short cache lifetimes, so returning visitors download them again (149 KiB).
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Shopify and omnisnippet1.com and others), adding 544 KiB and 500 ms of main-thread time.
Minify JavaScript
170 ms · 11 KiB11 KiB could be saved by minifying JavaScript.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
Duplicated JavaScript
28 KiB28 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
1 checks passed
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.
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.1 s
13.1 sThe page becomes fully interactive after 13.1 s. Good is under 3.8 s.
Real-user INP: 262 ms
262 msReal visitors wait 262 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 234 ms to 341 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 578 ms
578 msReal visitors wait 578 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 42 ms
42 msScripts block the page for only 42 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.2 MB in 201 requests
3.2 MBYour homepage downloads 3.2 MB in 201 requests on a phone: images 1.7 MB (7), other files 746 KiB (96) and scripts 657 KiB (58). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (7 characters)
Your title is only 7 characters: “AdiBody”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
25 internal links, 9 external
The homepage links to 25 pages on adibody.it and 9 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://adibody.com/.
Structured data in place
Structured data found: Organization, ProductGroup and WebSite.
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://adibody.com/sitemap.xml.
AI search readiness
4 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.
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 (324 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://adibody.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://adibody.com/collections/all and https://adibody.com/collections/prodotti all use the title “Prodotti – AdiBody”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://adibody.com/collections/all, https://adibody.com/collections/prodotti, https://adibody.com/products/body-modellante-a-pantaloncino, https://adibody.com/products/costume-modellante-atene, https://adibody.com/pages/contattaci-wa and https://adibody.com/policies/privacy-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://adibody.com/pages/contattaci-wa has no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
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 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Unexpected identifier 'feedback'”.
2 checks passed
Tap targets are thumb-sized
19 of 19 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 289 words of copy
The homepage carries about 289 words of visible text.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
25 other companies contacted
Loading the homepage contacts 25 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 adibody.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
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 adibody.it, including 12 speed issues, 4 SEO issues and 3 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.