Website review, no card needed
cgt.it website review
Visit site (opens in a new tab)Reviewed 7 November 202658 issues · 94 checks
This review found 58 issues worth fixing on cgt.it, 23 of them high impact, across 94 checks. The most urgent: improve image delivery. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.5 s |
| Aug 1, 2026 | 5.6 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.5 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.7 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 186 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 208 ms |
| Aug 22, 2026 | 208 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 251 ms |
| Oct 3, 2026 | 259 ms |
| Oct 10, 2026 | 265 ms |
| Oct 17, 2026 | 295 ms |
| Oct 24, 2026 | 291 ms |
| Oct 31, 2026 | 274 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
Improve image delivery
49.5 s · 12.7 MB18 images could be 12.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 49.5 s faster on a phone.
Use efficient cache lifetimes
9.1 s · 2.6 MB103 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Reduce unused JavaScript
8.7 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.8 s
A phone's processor spends 8.8 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,814 HTML elements
The page has 4,814 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.7 MB and 1.9 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.8 s. During a long task the page ignores taps.
Google Tag Manager adds 666 ms
666 msGoogle Tag Manager costs a phone 666 ms of main-thread work and 681 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.
Render-blocking requests
700 ms18 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Google CDN adds 573 ms
573 msGoogle CDN costs a phone 573 ms of main-thread work and 1.1 MB 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.
Reduce unused CSS
600 ms · 75 KiBAbout 75 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.
Facebook adds 318 ms
318 msFacebook costs a phone 318 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.
userway.org adds 77 ms
77 msuserway.org costs a phone 77 ms of main-thread work and 385 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.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 218 ms
218 msYour server sent the HTML in 218 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: 5.7 s
5.7 sReal visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.2 s
8.2 sThe first text or image appears after 8.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 91.7 s
91.7 sYour largest element takes 91.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “div.animsition-loading”.
Speed Index: 19.8 s
19.8 sVisually, the page fills in at 19.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 91.7 s
91.7 sThe page becomes fully interactive after 91.7 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user INP: 282 ms
282 msReal visitors wait 282 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 70% slower for real visitors
+70%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 186 ms to 274 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.2 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.7 MB in 172 requests
26.7 MBYour homepage downloads 26.7 MB in 172 requests on a phone: images 22.8 MB (70), scripts 2.7 MB (50) and other files 616 KiB (23). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (123 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 7.6 g of CO₂ per visit
7.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.57 g of CO₂e: 908.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
ARIA input fields must have an accessible name (3 elements)
ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
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.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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.
22 form fields without a label
22 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor 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 (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://cgt.it/sitemap.xml, so Google discovers your pages only by following links.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
171 internal links, 28 external
The homepage links to 171 pages on cgt.it and 28 external pages.
4 checks passed
Meta description: 97 characters
Your meta description is 97 characters: “Entra per scoprire la tecnologia, i vantaggi e la qualità offerta dai prodotti e dai servizi CGT.”.
Title: 42 characters
Your title is a healthy 42 characters: “CGT: la soluzione ideale per il tuo lavoro”.
Canonical URL set
The canonical URL is https://cgt.it/it/node/1616.
robots.txt in place
robots.txt is in place.
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://cgt.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 (2,381 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://cgt.it/it all use the title “CGT: la soluzione ideale per il tuo lavoro”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://cgt.it/it/prodotti/escavatori-cingolati, https://cgt.it/it/prodotti/escavatori-gommati, https://cgt.it/it/prodotti/mini-escavatori, https://cgt.it/it/prodotti/martelli-idraulici, https://cgt.it/it/prodotti/pale-gommate and https://cgt.it/it/prodotti/pale-cingolate and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://cgt.it/it, whose canonical is https://cgt.it/it/node/1616. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://cgt.it/it has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://cgt.it/it/prodotti/martelli-idraulici, https://cgt.it/it/prodotti/pale-gommate, https://cgt.it/it/prodotti/terne-rigide, https://cgt.it/it/prodotti/attrezzature-pale, https://cgt.it/it/prodotti/attrezzature-escavatori and https://cgt.it/it/prodotti/dumper-articolati and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
15 small tap targets
15 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cgtspa.my.salesforce-scrt.com/embeddedservice/v1/embedded-service-config?orgId=00D…”.
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: 17 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 18-field form
Your longest form asks for 18 fields (12 required). Every extra field lowers completion.
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 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,616 words of copy
The homepage carries about 1,616 words of visible text.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
23 other companies contacted
Loading the homepage contacts 23 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 cgt.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
- Drupal
- Framework
- jQuery
- Hosting
- Imperva
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 58 issues on cgt.it, including 27 speed issues, 6 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.