The technical quality of a website is not an aesthetic opinion.

This page is the technical report for comune.genova.it (category Companies). It separates perceived identity (design, brand fame) from the raw technical data measured with Google PageSpeed Insights and from source-code analysis: the same parameters, in the same order, as the Audit 360° tool.

⚡ Performance
2° su 4
category average 62
🧠 AI Readiness
2° su 4
category average 14
🌱 CO₂ (lower is better)
2° su 4
category average 1.04 g
Performance (Lighthouse)
57
out of 100
Carbon Footprint
0.403g
CO₂ per single visit
AI Readiness (Graph) LLM
0
out of 100

Summary: what works and what doesn't

Assessment generated from the values measured on comune.genova.it in the latest test: every item has a verifiable reference threshold.

✅ Strengths

  • Page weight kept in check (1.53 MB).

⚠️ Priorities for action

  • Hosting not verified as "green": with a certified provider emissions would drop by about 89%.

Detailed Audit Data

The six audit areas with the parameters recorded in the latest scan. Open the deep-dives to see every value.

⚡ Performance and Core Web Vitals

Performance Score: 57 / 100
First Contentful Paint: 3.6 s
Largest Contentful Paint: 7.0 s
Total Blocking Time: —
Cumulative Layout Shift: —
Total Page Weight: 1.53 MB
Accessibility
—
Best Practices
—
Technical SEO
—
Lab metrics and server
Speed Index: —
Server response (TTFB): —
DOM nodes: —
Network requests: —
Weight in KB: 1567 KB
Simulated device: MOBILE
Real-user data (Chrome UX Report)

Value not recorded in this test.

What slows the page down

Value not recorded in this test.

🌱 Sustainability

Renewable Hosting: ❌ Not verified
Hosting provider: —
CO₂ per visit: 0.403 g
Annual emissions (10k visits): 4.0 kg
Calculation details
CO₂ per 1,000 visits: 403.0 g
CO₂ per 100,000 visits: 40 kg
Applied carbon intensity: 442 g/kWh
Method: Sustainable Web Design (SWDM)
Date recorded: 09/10/2026

📝 On-page SEO

Title length: —
Meta description length: —
Canonical: —
H1 / H2 headings: —
Structure and content
Language (lang): —
Mobile viewport: —
Indexable: —
Hreflang: —
OpenGraph / Twitter tags: —
Images without alt: —
Internal / external links: —
Words in text: —
HTML weight: —

🔍 Semantic Markup

Syntax Status: NESSUNO
JSON-LD errors: 0
JSON-LD blocks: —
Robots & Sitemap: ✅ / ❌
Detected entities and types
Schema.org types (total): —
Microdata / RDFa: —
Top-level entities:
Nessuno
Robots.txt and Sitemap
Robots.txt: ✅ Present
Disallow rules: —
XML Sitemap: ❌ Missing

🧠 Knowledge Graph

Main Entity: ❌ Missing
Crawl Optimization: 0 / 100
Topical Authority: 0 / 100
Overall AI Readiness: 0 / 100
Knowledge Graph details
Architecture: None
sameAs links: —
knowsAbout competences: —
significantLink: —
isPartOf/hasPart hierarchy: —
about/mentions: —
Entities described: —
@ids to entities outside the page: —
Possible @id typos (same page): —

🛡️ Basic security

HTTPS: —
HSTS: —
Content-Security-Policy: —
Security headers: —
All checks
X-Content-Type-Options: —
Anti-clickjacking (XFO / frame-ancestors): —
Referrer-Policy: —
Redirect on the tested URL: —

Overall Assessment

Performance Analysis

Based on the simulations run, the technical architecture of the site stays below the acceptability threshold: the site works but loses visits on every load.

Dive into the technical performance analysis
Performance sits in a middle band that feels acceptable but is not: Core Web Vitals fail on at least one axis and mobile suffers. There is concrete room for recovery and, within weeks, the score can climb above 80. Discipline on assets, correct caching and attention to render-blocking components are what closes the gap.

It is worth remembering that low performance is not isolated: it severely affects real SEO ranking, increases the cost per click (CPC) of Google Ads campaigns, and depresses conversion rate.

Semantics for Artificial Intelligence

On the semantic and structured-data side (essential for LLMs like ChatGPT, Gemini and Claude), the domain is not readable by LLMs: no semantic structure for ChatGPT, Gemini and Perplexity.

Dive into the semantic and Knowledge Graph analysis
A score near zero means generative models cannot extract entities or cite the brand in answers. In a world where AI is becoming the primary access point to information, this is a huge competitive risk. A systemic intervention is needed: structured data, authoritative content, coherent ontology.

The detected Knowledge Graph infrastructure is classified as: None, with a Schema.org markup status of NESSUNO.

Improvement Plan

Six concrete actions for each metric, in order of impact. Metrics in the critical band should be tackled first.

🎯 Performance Insufficient

  1. Enable Brotli/Gzip compression for HTML, CSS and JS.
  2. Convert all images to WebP or AVIF and set explicit dimensions.
  3. Move rendering of non-critical components to the server (SSR/SSG).
  4. Reduce HTTP requests: bundle CSS and JS, use sprites where it makes sense.
  5. Confirm the hosting copes with traffic: slow shared CPUs mean high TTFB.
  6. Monitor real Core Web Vitals via CrUX or in-house RUM, not just synthetic tests.

🌱 Sustainability (CO₂) Insufficient

  1. Introduce a CO₂ budget for every new page published.
  2. Prefer external video platforms (YouTube) with lazy embed.
  3. Use responsive images (srcset) to avoid unnecessary downloads on mobile.
  4. Replace JS animations with CSS when possible (less CPU, less energy).
  5. Periodically verify your provider's Green Web Badge.
  6. Communicate the ESG results: digital sustainability is a brand asset.

🔍 Semantic Markup Insufficient

  1. Add secondary entities (Person, Place, Event) to enrich the graph.
  2. Link articles and products to their author via Person schema.
  3. Introduce speakable for content optimised for voice assistants.
  4. Verify consistency between schema and visible content (no invented data).
  5. Monitor rich results in Search Console to catch regressions.
  6. Update the schema whenever the company offering changes.

🧠 AI Readiness Out of Standard

  1. Publish an explicit corporate knowledge graph (entities + relations).
  2. Add authoritative pages on who you are, services and case studies.
  3. Structure content in Q&A blocks: LLMs prefer explicit questions.
  4. Use complete structured data on every page (Organization, WebSite, FAQPage).
  5. Cite authoritative sources: LLMs reward verifiable content.
  6. Monitor brand mentions on ChatGPT/Perplexity to measure progress.

The Alternative: WAA Enterprise Framework

While most traditional CMSs (WordPress, Magento, etc.) suffer from severe architectural bottlenecks that cost organic visibility, advanced JAMStack frameworks like IM Web (WAA) systematically guarantee near-100/100 performance, near-zero CO₂ emissions and native readiness (Semantic Graph) to feed Artificial Intelligence databases.

→ Back to the Analysis tool