Website review, no card needed

21adv.it logo

21adv.it website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 71 checks

This review found 31 issues worth fixing on 21adv.it, 15 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of 21adv.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 21adv.it at 1.2 s1.2 s
  2. 21adv.it at 2.5 s2.5 s
  3. 21adv.it at 3.7 s3.7 s
  4. 21adv.it at 5.0 s5.0 s
  5. 21adv.it at 6.2 s6.2 s
  6. 21adv.it at 7.4 s7.4 s
  7. 21adv.it at 8.7 s8.7 s
  8. 21adv.it at 9.9 s9.9 s

Speed

10 to fix64
  • Use efficient cache lifetimes

    1.8 s · 6.2 MB

    36 files are served with short cache lifetimes, so returning visitors download them again (6.2 MB).

  • Render-blocking requests

    3.4 s

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

  • Reduce unused JavaScript

    1.2 s · 872 KiB

    About 872 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Main-thread work: 5.6 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 178 KiB

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

  • Improve image delivery

    783 KiB

    3 images could be 783 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, iubenda and Other Google APIs/SDKs and others), adding 963 KiB and 598 ms of main-thread time.

  • Google CDN adds 485 ms

    485 ms

    Google CDN costs a phone 485 ms of main-thread work and 742 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Font display

    450 ms

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

  • 6 long tasks on the main thread

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

  • Document request latency

    41 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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: 206 ms

    206 ms

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

Core Web Vitals

4 to fix75
  • Speed Index: 17.0 s

    17.0 s

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

  • Time to Interactive: 18.8 s

    18.8 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “21adv”.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 145 ms

    145 ms

    Scripts block the page for only 145 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

5 to fix28
  • Page weight: 9.6 MB in 57 requests

    9.6 MB

    Your homepage downloads 9.6 MB in 57 requests on a phone: images 7.0 MB (13), scripts 1.7 MB (18) and other files 383 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    [email protected] weighs 652 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (952 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.

  • 3 images far larger than shown

    31 KiB

    3 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,080 px wide, shown at 354 px. Resized copies would save about 31 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (301 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.7 g of CO₂ per visit

    2.73 g

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

Accessibility

6 to fixGoogle 9392
  • 2 tap targets too small

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

  • 6 images without alt text

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

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

    All page content should be contained by landmarks: 5 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 12 internal links, 2 external

    The homepage links to 12 pages on 21adv.it and 2 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Pubblicità, marketing, strategia, consulenza creativa, web design e digital, ci prendiamo cura di ogni aspetto per una …”.

  • One H1 headline

    Your main headline reads: “21adv”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “21adv | Comunicazione efficace dalla A alla Z”.

  • Canonical URL set

    The canonical URL is https://www.21adv.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://www.21adv.it/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.21adv.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.

3 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 (235 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.21adv.it/progetti, https://www.21adv.it/servizi, https://www.21adv.it/history and https://www.21adv.it/contatti have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.21adv.it/progetti has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.21adv.it/servizi, https://www.21adv.it/contatti, https://www.21adv.it/privacy and https://www.21adv.it/cookie have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • 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 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 275 words of copy

    The homepage carries about 275 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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

Upkeep, stack and company

  • The footer still says © 2017.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on 21adv.it, including 14 speed issues, 1 SEO issue 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

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