Website review, no card needed
axera.it website review
Visit site (opens in a new tab)Reviewed 3 November 202627 issues · 78 checks
This review found 27 issues worth fixing on axera.it, 15 of them high impact, across 78 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 6.0 s |
| May 30, 2026 | 5.7 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 130 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 133 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 151 ms |
| Oct 31, 2026 | 146 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.4 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 279 KiBAbout 279 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
600 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Use efficient cache lifetimes
350 ms · 249 KiB32 files are served with short cache lifetimes, so returning visitors download them again (249 KiB).
Legacy JavaScript
350 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Facebook adds 276 ms
276 msFacebook costs a phone 276 ms of main-thread work and 267 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Facebook, Google CDN and exetera.com and others), adding 369 KiB and 381 ms of main-thread time.
Minify JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
Improve image delivery
17 KiB1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 744 ms of it running JavaScript. That is comfortably low.
Server response: 252 ms
252 msYour server sent the HTML in 252 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.
Real-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “csd2026 hero”. Most of its time is resource load delay (7.7 s).
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 121 ms
121 msReal visitors wait 121 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.
Largest content (LCP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.0 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 132 ms
132 msScripts block the page for only 132 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 49.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 95 requests
1.4 MBYour homepage downloads 1.4 MB in 95 requests on a phone: scripts 804 KiB (42), images 208 KiB (6) and fonts 197 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
135 internal links, 11 external
The homepage links to 135 pages on axera.it and 11 external pages.
8 checks passed
Meta description: 116 characters
Your meta description is 116 characters: “Quattro realtà complementari nel settore TLC/ICT fanno squadra per sostenere lo sviluppo delle aziende del Triveneto”.
One H1 headline
Your main headline reads: “CYBER SECURITY DAY”.
Title: 40 characters
Your title is a healthy 40 characters: “Axera Spa | TLC & ICT Business Solutions”.
Canonical URL set
The canonical URL is https://www.axera.it/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.axera.it/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.axera.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (965 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.axera.it/chi-siamo/certificazioni has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.axera.it/connettivita/fibra-fttc-xdsl and https://www.axera.it/connettivita/custom-dual-banda have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.axera.it/chi-siamo/manifesto, https://www.axera.it/chi-siamo/lavora-con-noi, https://www.axera.it/chi-siamo/certificazioni, https://www.axera.it/connettivita/fibra-fttc-xdsl and https://www.axera.it/connettivita/custom-dual-banda took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
5 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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 459 words of copy
The homepage carries about 459 words of visible text.
3 checks passed
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
9 cookies set on arrival
9Opening the homepage sets 9 cookies (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.
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 axera.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Axera SpA
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on axera.it, including 17 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.