Programmable

Website review, no card needed

socado.com logo

socado.com website review

Visit site (opens in a new tab)Reviewed 21 October 202618 issues · 61 checks

This review found 18 issues worth fixing on socado.com, 7 of them high impact, across 61 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

81B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.4 s1.7 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
106 ms86 msMay 2Oct 1793 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202694 ms
May 9, 202694 ms
May 16, 202691 ms
May 23, 202688 ms
May 30, 202691 ms
Jun 6, 202689 ms
Jun 13, 202696 ms
Jun 20, 2026101 ms
Jun 27, 2026102 ms
Jul 4, 2026104 ms
Jul 11, 202695 ms
Jul 18, 2026100 ms
Jul 25, 202696 ms
Aug 1, 202697 ms
Aug 8, 202697 ms
Aug 15, 202691 ms
Aug 22, 202693 ms
Sep 5, 202695 ms
Sep 12, 202694 ms
Sep 19, 202697 ms
Sep 26, 202699 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202693 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

www.socado.com (opens in a new tab)
Full-page screenshot of socado.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. socado.com at 0.4 s0.4 s
  2. socado.com at 0.8 s0.8 s
  3. socado.com at 1.1 s1.1 s
  4. socado.com at 1.5 s1.5 s
  5. socado.com at 1.9 s1.9 s
  6. socado.com at 2.3 s2.3 s
  7. socado.com at 2.6 s2.6 s
  8. socado.com at 3.0 s3.0 s

Speed

100

  • Document request latency

    2 KiB

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

3 checks passed

  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100 (desktop: 71). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.0 s

    A phone's processor spends 0.0 s on main-thread work while loading, 4 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

2 to fix100

  • 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 TTFB: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 94 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

11 checks passed

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 92 ms

    92 ms

    Real visitors wait 92 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Momentaneamente non disponibile per manutenzione. Riprova f…”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

100

  • About 0.00 g of CO₂ per visit

    0.00 g

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

1 checks passed

  • Page weight: 3 KiB in 1 request

    3 KiB

    Your homepage downloads 3 KiB in 1 request on a phone: HTML 3 KiB (1). That is a lean page.

Accessibility

4 to fixGoogle 7775

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 5 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: 5 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8262

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • Title is short (13 characters)

    Your title is only 13 characters: “Home - Socado”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://www.socado.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at socado.com/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 58 internal links, 4 external

    The homepage links to 58 pages on socado.com and 4 external pages.

4 checks passed

  • Meta description: 134 characters

    Your meta description is 134 characters: “Since 1975, Socado has been making chocolate in Verona: pralines, chocolate bars, and spreads. Discover Socado’s qualit…”.

  • Canonical URL set

    The canonical URL is https://www.socado.com/en/.

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

AI search readiness

100
2 checks passed

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

  • llms.txt published

    The site publishes https://www.socado.com/llms.txt (1 KiB, 20 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70

  • 11 linked pages are broken

    Your homepage links to https://www.socado.com/en/chi-siamo, https://www.socado.com/en/sostenibilita-e-certificazioni, https://www.socado.com/en/praline-socado, https://www.socado.com/en/il-fondatore, https://www.socado.com/en/natale and https://www.socado.com/en/idee-regalo and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages without an H1

    https://www.socado.com/en/private-label, https://www.socado.com/en/chocolate-passion, https://www.socado.com/en/news and https://www.socado.com/en/contatti have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.socado.com/en/private-label, https://www.socado.com/en/chocolate-passion, https://www.socado.com/en/news and https://www.socado.com/en/contatti took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 (Service Unavailable)”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57

  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 9 words

    The homepage has only about 9 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Learn more”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

  • 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 socado.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
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on socado.com, including 2 speed issues, 5 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

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