Website review, no card needed

atac.roma.it logo

atac.roma.it website review

Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 87 checks

This review found 46 issues worth fixing on atac.roma.it, 12 of them high impact, across 87 checks. The most urgent: render-blocking 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
3.8 s2.9 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Oct 24, 20263.5 s
Oct 31, 20263.5 s
Nov 7, 20263.6 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
176 ms137 msMay 30Nov 14150 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026142 ms
Jun 6, 2026141 ms
Jun 13, 2026144 ms
Jun 20, 2026155 ms
Jun 27, 2026161 ms
Jul 4, 2026160 ms
Jul 11, 2026160 ms
Jul 18, 2026161 ms
Jul 25, 2026162 ms
Aug 1, 2026171 ms
Aug 8, 2026171 ms
Aug 15, 2026167 ms
Aug 22, 2026161 ms
Aug 29, 2026155 ms
Sep 5, 2026151 ms
Sep 12, 2026146 ms
Sep 19, 2026145 ms
Sep 26, 2026144 ms
Oct 3, 2026144 ms
Oct 10, 2026144 ms
Oct 17, 2026146 ms
Oct 24, 2026147 ms
Oct 31, 2026145 ms
Nov 7, 2026147 ms
Nov 14, 2026150 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 atac.roma.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atac.roma.it at 0.4 s0.4 s
  2. atac.roma.it at 0.9 s0.9 s
  3. atac.roma.it at 1.3 s1.3 s
  4. atac.roma.it at 1.8 s1.8 s
  5. atac.roma.it at 2.2 s2.2 s
  6. atac.roma.it at 2.7 s2.7 s
  7. atac.roma.it at 3.1 s3.1 s
  8. atac.roma.it at 3.6 s3.6 s

Speed

11 to fix63
  • Render-blocking requests

    2.4 s

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (telerik.com and Cookiebot), adding 2.6 MB and 1.0 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • telerik.com adds 762 ms

    762 ms

    telerik.com costs a phone 762 ms of main-thread work and 2.4 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: 63

    63/100

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    620 ms · 239 KiB

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

  • Font display

    300 ms

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

  • Cookiebot adds 270 ms

    270 ms

    Cookiebot costs a phone 270 ms of main-thread work and 157 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.8 s

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

  • 1,990 HTML elements

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

  • Use efficient cache lifetimes

    250 ms · 142 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (142 KiB).

  • Improve image delivery

    27 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • 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

13 to fix0
  • 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 LCP: 4.3 s

    4.3 s

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

  • Time to Interactive: 45.5 s

    45.5 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user INP: 216 ms

    216 ms

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

  • Real-user CLS: 0.21

    0.21

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 520 ms

    520 ms

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizziamo i cookie per personalizzare contenuti ed annunc…”. Most of its time is element render delay (1.9 s).

  • 31 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

1 checks passed
  • Cumulative Layout Shift: 0.028

    0.028

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

Images and page weight

3 to fix53
  • Page weight: 11.6 MB in 87 requests

    11.6 MB

    Your homepage downloads 11.6 MB in 87 requests on a phone: images 7.2 MB (35), scripts 3.4 MB (33) and fonts 780 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.1 MB) 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.

  • 13 images below the first screen load straight away

    13 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.30 g

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

6 to fixGoogle 9393
  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 11 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 4 links without text

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (5 elements).

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 9282
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (210 characters)

    Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • No XML sitemap

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

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 164 internal links, 24 external

    The homepage links to 164 pages on atac.roma.it and 24 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Home page”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “ATAC S.p.A. | Azienda per la mobilità”.

  • Canonical URL set

    The canonical URL is https://www.atac.roma.it/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

3 to fix69
  • 2 linked pages are broken

    Your homepage links to https://www.atac.roma.it/%7B%7BcurrentItemRoute.ViewRouteUrl%7D%7D and https://www.atac.roma.it/%7B%7Broute.ViewRouteUrl%7D%7D, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://www.atac.roma.it/cosa-ne-pensi and https://www.atac.roma.it/tempo-reale/lavori-programmati/dettaglio/%7B%7BlavoroProgrammato.UrlName%7D%7D have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://www.atac.roma.it/tempo-reale, https://www.atac.roma.it/tempo-reale/domani-20-novembre--in-programma-3-manifestazioni.-i-dettagli, https://www.atac.roma.it/tempo-reale/domenica-22-novembre--32--edizione--corri-alla-garbatella----tutte-le-informazioni-sul-trasporto-pubblico, https://www.atac.roma.it/tempo-reale/il-20-novembre-sciopero-di-24-ore--le-info, https://www.atac.roma.it/tempo-reale/a-casal-bruciato--dal-9-novembre-la-linea-448-estende-il-percorso and https://www.atac.roma.it/tempo-reale/anno-scolastico-2026-2027---torna-la-rete-dedicata-agli-studenti---abbonamento-metrebus-annuale-under-19-a-50-euro and 1 other use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.atac.roma.it/tempo-reale/lavori-programmati/dettaglio/%7B%7BlavoroProgrammato.UrlName%7D%7D has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 104 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 to fixGoogle 9693
  • 7 small tap targets

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

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • No console errors

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

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

    The homepage carries about 392 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Matomo.

  • Direct contact links

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

Privacy and tracking

  • 16 cookies set on arrival

    16

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

  • 3 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Hosting
Radware Ltd

Company

Employees
11,046
Founded
1909
Headquarters
Rome

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on atac.roma.it, including 24 speed issues, 5 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

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
atac.roma.it website review: scores and fixes | Programmable