Website review, no card needed

acmilan.com logo

acmilan.com website review

Visit site (opens in a new tab)Reviewed 18 October 202633 issues · 80 checks

This review found 33 issues worth fixing on acmilan.com, 14 of them high impact, across 80 checks. The most urgent: mobile performance score: 37. 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
5.5 s2.1 sApr 25Oct 102.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.1 s
May 2, 20265.0 s
May 9, 20264.9 s
May 16, 20264.8 s
May 23, 20264.8 s
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.6 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.4 s
Jul 11, 20264.1 s
Jul 18, 20263.7 s
Jul 25, 20263.4 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
248 ms154 msApr 25Oct 10195 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026237 ms
May 2, 2026225 ms
May 9, 2026221 ms
May 16, 2026213 ms
May 23, 2026212 ms
May 30, 2026221 ms
Jun 6, 2026217 ms
Jun 13, 2026218 ms
Jun 20, 2026220 ms
Jun 27, 2026227 ms
Jul 4, 2026180 ms
Jul 11, 2026177 ms
Jul 18, 2026171 ms
Jul 25, 2026165 ms
Aug 1, 2026165 ms
Aug 8, 2026167 ms
Aug 15, 2026166 ms
Aug 22, 2026172 ms
Aug 29, 2026186 ms
Sep 5, 2026187 ms
Sep 12, 2026191 ms
Sep 19, 2026191 ms
Sep 26, 2026193 ms
Oct 3, 2026195 ms
Oct 10, 2026195 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

Full-page screenshot of acmilan.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. acmilan.com at 0.6 s0.6 s
  2. acmilan.com at 1.2 s1.2 s
  3. acmilan.com at 1.8 s1.8 s
  4. acmilan.com at 2.4 s2.4 s
  5. acmilan.com at 2.9 s2.9 s
  6. acmilan.com at 3.5 s3.5 s
  7. acmilan.com at 4.1 s4.1 s
  8. acmilan.com at 4.7 s4.7 s

Speed

9 to fix37
  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

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

  • Improve image delivery

    1.6 MB

    14 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    900 ms · 666 KiB

    About 666 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 1.0 MB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google/Doubleclick Ads, Optanon and instana.io and others), adding 1.5 MB and 447 ms of main-thread time.

  • Google/Doubleclick Ads adds 295 ms

    295 ms

    Google/Doubleclick Ads costs a phone 295 ms of main-thread work and 1.2 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.

  • 14 long tasks on the main thread

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

  • 1,814 HTML elements

    The page has 1,814 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 22 KiB

    Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

8 to fix67
  • 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: 10.5 s

    10.5 s

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

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Real-user INP: 215 ms

    215 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 591 ms

    591 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

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

    -51%

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

3 to fix53
  • Page weight: 5.6 MB in 142 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 142 requests on a phone: images 2.8 MB (54), scripts 1.9 MB (44) and fonts 577 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

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

  • About 1.6 g of CO₂ per visit

    1.60 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8892
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

  • Orphan list items

    Some list items are not inside a list.

  • 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. (4 elements).

2 checks passed
  • Every image has alt text

    All 105 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 8586
  • Title is short (25 characters)

    Your title is only 25 characters: “AC Milan | Sito Ufficiale”. 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.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 92 internal links, 57 external

    The homepage links to 92 pages on acmilan.com and 57 external pages.

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Visita il sito ufficiale dell'Associazione Calcio Milan: tutte le ultime notizie su squadra e società, info su partite,…”.

  • One H1 headline

    Your main headline reads: “AC Milan | Sito Ufficiale”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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.acmilan.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (575 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://www.acmilan.com/en/news/videos/social/2026-10-16/an-unforgettable-night-for-ciss3, https://www.acmilan.com/en/news/videos/social/2026-10-14/pavlovic-still-in-rossonero, https://www.acmilan.com/en/news/videos/social/2026-10-10/franco-baresi-s-mural, https://www.acmilan.com/en/news/videos/social/2026-10-04/mike-claims-the-cover-of-the-month-crown, https://www.acmilan.com/en/news/videos/social/2026-10-02/puli-for-september-s-goal-of-the-month and https://www.acmilan.com/en/news/videos/social/2026-09-20/the-first-one-san-siro and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.acmilan.com/en/news/videos/social/2026-10-16/an-unforgettable-night-for-ciss3, https://www.acmilan.com/en/news/videos/social/2026-10-14/pavlovic-still-in-rossonero, https://www.acmilan.com/en/news/videos/social/2026-10-10/franco-baresi-s-mural, https://www.acmilan.com/en/news/videos/social/2026-10-04/mike-claims-the-cover-of-the-month-crown, https://www.acmilan.com/en/news/videos/social/2026-10-02/puli-for-september-s-goal-of-the-month and https://www.acmilan.com/en/news/videos/social/2026-09-20/the-first-one-san-siro and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 10084
  • 1 broken image

    1 image failed to load on a phone, for example https://www.acmilan.com/_next/image?url=https%3A%2F%2Fassets-eu-01.kc-usercontent.com%3A443%2F006f7528-416b-01e4-8ef2-ab6ab3f4e177%2F1b5007a7-584b-4e5a-ad80-ebc5951d08af%2F2026.10.16-TM-Atalanta-wide..

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    39 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • 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 370 words of copy

    The homepage carries about 370 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “BUY NOW”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “BUY NOW”, “Buy Now” and “See schedule”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Analytics (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 acmilan.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

Company

Founded
1899
Headquarters
Milan

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 acmilan.com, including 17 speed issues, 4 SEO issues and 2 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