Website review, no card needed
nextdeal.it website review
Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 76 checks
This review found 33 issues worth fixing on nextdeal.it, 10 of them high impact, across 76 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Render-blocking requests
1.5 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Improve image delivery
1.1 s · 200 KiB3 images could be 200 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused JavaScript
1.1 s · 187 KiBAbout 187 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 35 KiB2 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
Reduce unused CSS
300 ms · 77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 280 ms
280 msGoogle Tag Manager costs a phone 280 ms of main-thread work and 313 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.
1,632 HTML elements
The page has 1,632 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Cookiebot and zoho.eu and others), adding 529 KiB and 466 ms of main-thread time.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
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.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 519 ms of it running JavaScript. That is comfortably low.
Server response: 113 ms
113 msYour server sent the HTML in 113 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Entra nel Futuro Digitale SOLUZIONI E SERVIZI PER L'AUTOMAZ…”.
Time to Interactive: 9.0 s
9.0 sThe page becomes fully interactive after 9.0 s. Good is under 3.8 s.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 240 ms
240 msScripts block taps and scrolling for 240 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.021
0.021The layout barely moves while loading (CLS 0.021, good is under 0.1).
Images and page weight
4 images below the first screen load straight away
4 images further down the page (353 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (384 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.5 MB in 57 requests
1.5 MBYour homepage downloads 1.5 MB in 57 requests on a phone: images 881 KiB (30), scripts 543 KiB (12) and stylesheets 73 KiB (5). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
35 images without alt text
35 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Nextdeal - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
4 H1 headlines
There are 4 <h1> headlines (“Zoho Partner dal 2018”, “Zia Agent Studio” and “ChatGPT - Claude - Zoho Catalyst”). One clear main headline is easier for people and search engines.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
47 internal links, 1 external
The homepage links to 47 pages on nextdeal.it and 1 external page.
4 checks passed
Canonical URL set
The canonical URL is https://www.nextdeal.it/.
Structured data in place
Structured data found: Organization.
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.nextdeal.it/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.nextdeal.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 contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (505 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages without an H1
https://www.nextdeal.it/zoho-crm, https://www.nextdeal.it/zoho-ai-agent-factory, https://www.nextdeal.it/zoho-crm-competence-center, https://www.nextdeal.it/zoho-crm-prezzo-in-offerta, https://www.nextdeal.it/digital-automation and https://www.nextdeal.it/crm-forza-di-vendita and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.nextdeal.it/pratiche-e-adempimenti took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 14 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 “Access to XMLHttpRequest at 'https://webfonts.zoho.eu/css?family=Arimo:400,700/Nunito/Karla:400/Lato:300,700,400/Lora/S…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 517 words of copy
The homepage carries about 517 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 nextdeal.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
- Zoho Sites 2.0, https://zoho.com/sites
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- ZOHO Corporation B.V
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 nextdeal.it, including 13 speed issues, 4 SEO issues 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.