Website review, no card needed
cira.it website review
Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 77 checks
This review found 33 issues worth fixing on cira.it, 9 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 97 ms |
| May 16, 2026 | 102 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 101 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 84 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 85 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
Render-blocking requests
3.0 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
550 ms · 96 KiB10 files are served with short cache lifetimes, so returning visitors download them again (96 KiB).
Document request latency
550 ms · 22 KiBThe HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
541 msReduce initial server response time. Google estimates savings of 541 ms on a phone.
Reduce unused CSS
450 ms · 80 KiBAbout 80 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.
Server response: 641 ms
641 msYour server takes 641 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
Improve image delivery
51 KiB4 images could be 51 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (JSDelivr CDN, Cloudflare CDN and Google Fonts), adding 216 KiB and 23 ms of main-thread time.
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
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 21 ms of it running JavaScript. That is comfortably low.
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.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “EASN2026, il CIRA al panel europeo su start-up e innovazion…”. Most of its time is resource load duration (3.6 s).
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 4.3 s
4.3 sThe page becomes fully interactive after 4.3 s. Good is under 3.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 97 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 52% faster for real visitors
-52%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image below the first screen load straight away
1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.1 g of CO₂ per visit
0.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.15 g of CO₂e: 17.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 535 KiB in 17 requests
535 KiBYour homepage downloads 535 KiB in 17 requests on a phone: images 244 KiB (6), fonts 116 KiB (1) and stylesheets 108 KiB (6). That is a lean page.
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
Main landmark should not be contained in another landmark (1 element)
Main 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 main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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. (2 elements).
2 checks passed
Every image has alt text
All 10 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 short (48 characters)
Your meta description is only 48 characters: “Benvenuto| Centro Italiano Ricerche Aerospaziali”. 70 to 160 characters is enough to sell the click.
47 internal links, 8 external
The homepage links to 47 pages on cira.it and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “CIRA - Centro Italiano Ricerche Aerospaziali”.
Title: 48 characters
Your title is a healthy 48 characters: “Benvenuto| Centro Italiano Ricerche Aerospaziali”.
Canonical URL set
The canonical URL is https://www.cira.it/.
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.cira.it/sitemap.xml.
AI search readiness
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.cira.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 (362 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages point its canonical at the homepage
https://www.cira.it/area-fornitori, https://www.cira.it/area-fornitori/albo-fornitori, https://www.cira.it/area-fornitori/bandi, https://www.cira.it/area-fornitori/manifestazioni, https://www.cira.it/contatti and https://www.cira.it/it/chi-siamo and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
12 pages without a meta description
https://www.cira.it/area-fornitori, https://www.cira.it/area-fornitori/bandi, https://www.cira.it/area-fornitori/manifestazioni, https://www.cira.it/contatti, https://www.cira.it/it/aeronautica and https://www.cira.it/it/spazio and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://www.cira.it/en 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.
4 pages slow to respond
https://www.cira.it/it/spazio, https://www.cira.it/it/elenco-news, https://www.cira.it/it/elenco-eventi and https://www.cira.it/it/lavora-con-noi took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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.
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
8 small tap targets
8 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css' violates the following Conten…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 238 words
The homepage has only about 238 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
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.
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.
1 checks passed
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 cira.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
- Asn Idc T.No.Om.I.Nc
Company
- Founded
- 1984
- Headquarters
- Capua
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 cira.it, including 16 speed issues, 2 SEO issues and 6 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.