Website review, no card needed
iltempo.it website review
Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 86 checks
This review found 38 issues worth fixing on iltempo.it, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.6 s |
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 236 ms |
| May 2, 2026 | 230 ms |
| May 9, 2026 | 229 ms |
| May 16, 2026 | 222 ms |
| May 23, 2026 | 219 ms |
| May 30, 2026 | 218 ms |
| Jun 6, 2026 | 222 ms |
| Jun 13, 2026 | 236 ms |
| Jun 20, 2026 | 251 ms |
| Jun 27, 2026 | 264 ms |
| Jul 4, 2026 | 268 ms |
| Jul 11, 2026 | 260 ms |
| Jul 18, 2026 | 247 ms |
| Jul 25, 2026 | 250 ms |
| Aug 1, 2026 | 257 ms |
| Aug 8, 2026 | 256 ms |
| Aug 15, 2026 | 252 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 233 ms |
| Sep 5, 2026 | 246 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 274 ms |
| Oct 3, 2026 | 274 ms |
| Oct 10, 2026 | 282 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
Speed
Reduce unused JavaScript
2.9 s · 951 KiBAbout 951 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
1.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 30
30/100Your mobile performance score is 30 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Stripe and InMobi and others), adding 1.3 MB and 822 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 518 KiB10 files are served with short cache lifetimes, so returning visitors download them again (518 KiB).
Reduce unused CSS
450 ms · 93 KiBAbout 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
InMobi adds 143 ms
143 msInMobi costs a phone 143 ms of main-thread work and 355 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 231 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
Improve image delivery
142 KiB8 images could be 142 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 30. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need.
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: 122 ms
122 msYour server sent the HTML in 122 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.8 s
9.8 sYour largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Papa Leone torna all’Angelus dopo l’intervento al polmone: …”.
Time to Interactive: 18.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 773 ms
773 msScripts block taps and scrolling for 773 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.259
0.259The layout shifts by 0.259 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 286 ms
286 msReal visitors wait 286 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 236 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 435 ms
435 msReal visitors wait 435 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.0 MB in 76 requests
3.0 MBYour homepage downloads 3.0 MB in 76 requests on a phone: scripts 1.8 MB (21), images 595 KiB (17) and fonts 290 KiB (3). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
L4QPPDCAIFCW7NXPLJJJKG4CPE.jpg 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).
About 0.8 g of CO₂ per visit
0.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 101.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
186 internal links, 15 external
The homepage links to 186 pages on iltempo.it and 15 external pages.
7 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Leggi le ultime notizie su Il Tempo. Rimani aggiornato con le news di politica, attualità, mondo e spettacoli.”.
One H1 headline
Your main headline reads: “Il Tempo”.
Title: 58 characters
Your title is a healthy 58 characters: “Il Tempo - notizie di politica, esteri, economia e cronaca”.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.iltempo.it/arc/outboundfeeds/sitemap-index/?outputType=xml.
AI search readiness
No llms.txt
There is no https://www.iltempo.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.
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 description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,440 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.iltempo.it/video/sport/un-battito-bove-alla-presentazione-sono-legato-alla-roma-e-allitalia-ma-oggi-sono-felice has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “No auth token provided for resizer”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,458 words of copy
The homepage carries about 1,458 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).
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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 iltempo.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 1944
- Headquarters
- Rome
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on iltempo.it, including 16 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.