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

This page is the technical report for vinted.it (category E-commerce). 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
9° su 12
category average 41
🧠 AI Readiness
5° su 12
category average 7
🌱 CO₂ (lower is better)
2° su 12
category average 0.64 g
Performance (Lighthouse)
29
out of 100
Carbon Footprint
0.097g
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 vinted.it in the latest test: every item has a verifiable reference threshold.

✅ Strengths

  • Hosting certified as renewable-powered: carbon intensity of 50 g/kWh instead of 442.

⚠️ Priorities for action

  • A 3.25 MB page: above 2 MB you pay in load time and CO₂ emissions.

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: 29 / 100
First Contentful Paint: 3.5 s
Largest Contentful Paint: 9.5 s
Total Blocking Time: —
Cumulative Layout Shift: —
Total Page Weight: 3.25 MB
Accessibility
—
Best Practices
—
Technical SEO
—
Lab metrics and server
Speed Index: —
Server response (TTFB): —
DOM nodes: —
Network requests: —
Weight in KB: 3328 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: ✅ Certified
Hosting provider: —
CO₂ per visit: 0.097 g
Annual emissions (10k visits): 1.0 kg
Calculation details
CO₂ per 1,000 visits: 97.0 g
CO₂ per 100,000 visits: 10 kg
Applied carbon intensity: 50 g/kWh
Method: Sustainable Web Design (SWDM)
Date recorded: 07/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: VALIDO
JSON-LD errors: 0
JSON-LD blocks: —
Robots & Sitemap: ✅ / ❌
Detected entities and types
Schema.org types (total): —
Microdata / RDFa: —
Top-level entities:
WebPage
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: Fragmented
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 shows severe structural issues directly hurting ranking, CPC and conversion rate.

Dive into the technical performance analysis
Rendering is well above Google's thresholds: LCP and FCP are out of range, and the site loads blocking assets sequentially. The result is penalised ranking, higher cost-per-click on paid campaigns, and compressed conversion rate. The required work is structural, not cosmetic: reduce asset weight, defer non-critical scripts, and address hosting if TTFB remains high.

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: Fragmented, with a Schema.org markup status of VALIDO.

Improvement Plan

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

🎯 Performance Severe Issues

  1. Open Lighthouse, identify the three heaviest bottlenecks, and tackle them one at a time.
  2. Enable Brotli/Gzip on HTML, CSS and JS at the server level.
  3. Preload critical fonts and the main LCP image.
  4. Reduce the DOM below 1,500 nodes: long lists need virtualisation.
  5. Set long-lived Cache-Control on all hashed assets.
  6. If TTFB exceeds 800ms, change hosting or move to SSR/SSG.

🌱 Sustainability (CO₂) Fair

  1. Publish the carbon footprint on a /sustainability page for transparency.
  2. Introduce a CO₂ budget for every new page published.
  3. Replace JS animations with CSS when possible.
  4. Periodically verify your provider's Green Web Badge.
  5. Use responsive images (srcset) on all main pages.
  6. Reduce the size of videos hosted on the domain.

🔍 Semantic Markup Excellent

  1. Keep a register of published entities to avoid duplication.
  2. Extend the schema with advanced properties and explicit relations.
  3. Integrate data with Wikidata to strengthen recognition.
  4. Document the ontological model for the editorial team.
  5. Regularly test the graph with the Schema Markup Validator.
  6. Consider exposing the graph as static JSON-LD (faster to parse).

🧠 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