Website review, no card needed

superhumans.it logo

superhumans.it website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 77 checks

This review found 33 issues worth fixing on superhumans.it, 11 of them high impact, across 77 checks. The most urgent: page weight: 40.1 MB in 68 requests. 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
4.3 s3.1 sMay 16Jun 63.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.1 s
May 23, 20263.8 s
May 30, 20263.5 s
Jun 6, 20263.2 s

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 superhumans.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. superhumans.it at 2.1 s2.1 s
  2. superhumans.it at 4.2 s4.2 s
  3. superhumans.it at 6.4 s6.4 s
  4. superhumans.it at 8.5 s8.5 s
  5. superhumans.it at 10.6 s10.6 s
  6. superhumans.it at 12.7 s12.7 s
  7. superhumans.it at 14.8 s14.8 s
  8. superhumans.it at 16.9 s16.9 s

Speed

10 to fix56
  • Reduce unused JavaScript

    1.8 s · 439 KiB

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

  • Use efficient cache lifetimes

    450 ms · 22.9 MB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (iubenda, Vimeo and JSDelivr CDN and others), adding 39.1 MB and 398 ms of main-thread time.

  • digitaloceanspaces.com adds 0 ms

    0 ms

    digitaloceanspaces.com costs a phone 0 ms of main-thread work and 29.1 MB 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.

  • Vimeo adds 101 ms

    101 ms

    Vimeo costs a phone 101 ms of main-thread work and 9.9 MB 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.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    513 KiB

    1 image could be 513 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    300 ms

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

  • iubenda adds 286 ms

    286 ms

    iubenda costs a phone 286 ms of main-thread work and 124 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.

  • Main-thread work: 2.4 s

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

  • Reduce unused CSS

    150 ms · 66 KiB

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

  • 7 long tasks on the main thread

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

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix67
  • Speed Index: 18.1 s

    18.1 s

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

  • Largest Contentful Paint: 8.5 s

    8.5 s

    Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We (superhumans) and selected third parties (1) collect per…”. Most of its time is element render delay (9.5 s).

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

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

3 checks passed
  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

1 to fix70
  • Page weight: 40.1 MB in 68 requests

    40.1 MB

    Your homepage downloads 40.1 MB in 68 requests on a phone: media 25.3 MB (3), other files 9.3 MB (18) and images 4.1 MB (17). Under 2 MB keeps phones on slow connections fast.

  • About 11.4 g of CO₂ per visit

    11.36 g

    By the Sustainable Web Design model, a visit to your homepage emits about 11.36 g of CO₂e: 1362.6 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

5 to fixGoogle 8592
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

Google 100100
  • 29 internal links, 12 external

    The homepage links to 29 pages on superhumans.it and 12 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Superhumans is a creative agency based in Rome and Milan, creating integrated campaigns, digital strategies, content, e…”.

  • One H1 headline

    Your main headline reads: “superhumans”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Superhumans | Independent Creative Agency in Rome and Milan”.

  • Canonical URL set

    The canonical URL is http://superhumans.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://superhumans.it/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://superhumans.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 (536 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 3 pages share a title

    https://superhumans.it/work/notte-prima-degli-esami-poste-italiane, https://superhumans.it/work/rebranding-the-right-power-forward and https://superhumans.it/work/a-volte-la-disabilita-e-lultimo-dei-miei-problemi all use the title “Works Archive - superhumans”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://superhumans.it/work/rebranding-the-right-power-forward, https://superhumans.it/work/a-volte-la-disabilita-e-lultimo-dei-miei-problemi, https://superhumans.it/the-language-of-love-behind-the-scenes-of-superhumans-x-tetrabondi-new-campaign, https://superhumans.it/authors/marzia-minnucci and https://superhumans.it/category/creativity have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://superhumans.it/work, whose canonical is https://superhumans.it/it/work. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://superhumans.it/work has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://superhumans.it/people, https://superhumans.it/work and https://superhumans.it/info 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.

  • 12 pages slow to respond

    https://superhumans.it/work, https://superhumans.it/info, https://superhumans.it/it, https://superhumans.it/division/supernow, https://superhumans.it/division/supercut and https://superhumans.it/work/notte-prima-degli-esami-poste-italiane and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

4 to fixGoogle 5483
  • 8 small tap targets

    8 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 614 words of copy

    The homepage carries about 614 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 of them by other companies (measured from a US location before any click).

  • 8 other companies contacted

    Loading the homepage contacts 8 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 superhumans.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
WordPress

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 superhumans.it, including 15 speed 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

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