Website review, no card needed

enegan.it logo

enegan.it website review

Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 88 checks

This review found 42 issues worth fixing on enegan.it, 19 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
8.0 s5.4 sMay 9Oct 246.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.3 s
May 16, 20267.4 s
May 23, 20267.5 s
May 30, 20267.5 s
Jun 6, 20267.7 s
Jun 13, 20267.6 s
Jun 20, 20267.6 s
Jun 27, 20267.7 s
Jul 4, 20267.6 s
Jul 11, 20267.5 s
Jul 18, 20267.4 s
Jul 25, 20267.1 s
Aug 1, 20266.8 s
Aug 8, 20266.7 s
Aug 15, 20266.3 s
Aug 22, 20266.0 s
Aug 29, 20265.9 s
Sep 5, 20265.8 s
Sep 12, 20265.7 s
Sep 19, 20265.8 s
Sep 26, 20265.8 s
Oct 3, 20265.9 s
Oct 10, 20266.1 s
Oct 17, 20266.1 s
Oct 24, 20266.1 s
Real-visitor tap response (INP)75th percentile, phones
194 ms152 msMay 9Oct 24189 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026178 ms
May 16, 2026179 ms
May 23, 2026178 ms
May 30, 2026180 ms
Jun 6, 2026182 ms
Jun 13, 2026181 ms
Jun 20, 2026186 ms
Jun 27, 2026183 ms
Jul 4, 2026182 ms
Jul 11, 2026184 ms
Jul 18, 2026183 ms
Jul 25, 2026183 ms
Aug 1, 2026185 ms
Aug 8, 2026185 ms
Aug 15, 2026184 ms
Aug 22, 2026178 ms
Aug 29, 2026168 ms
Sep 5, 2026161 ms
Sep 12, 2026157 ms
Sep 19, 2026159 ms
Sep 26, 2026160 ms
Oct 3, 2026168 ms
Oct 10, 2026174 ms
Oct 17, 2026183 ms
Oct 24, 2026189 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

Full-page screenshot of enegan.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. enegan.it at 1.3 s1.3 s
  2. enegan.it at 2.6 s2.6 s
  3. enegan.it at 4.0 s4.0 s
  4. enegan.it at 5.3 s5.3 s
  5. enegan.it at 6.6 s6.6 s
  6. enegan.it at 7.9 s7.9 s
  7. enegan.it at 9.2 s9.2 s
  8. enegan.it at 10.5 s10.5 s

Speed

8 to fix45
  • Reduce unused JavaScript

    5.1 s · 919 KiB

    About 919 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Render-blocking requests

    1.6 s

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google CDN and others), adding 1.5 MB and 599 ms of main-thread time.

  • Google Tag Manager adds 352 ms

    352 ms

    Google Tag Manager costs a phone 352 ms of main-thread work and 693 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.

  • Reduce unused CSS

    300 ms · 73 KiB

    About 73 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 CDN adds 82 ms

    82 ms

    Google CDN costs a phone 82 ms of main-thread work and 351 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.

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 199 ms. During a long task the page ignores taps.

  • Improve image delivery

    184 KiB

    2 images could be 184 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    13 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (13 KiB).

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • 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: 6.6 s

    6.6 s

    Real visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.5 s

    3.5 s

    Real visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AZIENDE PIÙ ATTENTE AL CLIMA 2025”. Most of its time is element render delay (8.4 s).

  • Speed Index: 17.5 s

    17.5 s

    Visually, the page fills in at 17.5 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 20.5 s

    20.5 s

    The page becomes fully interactive after 20.5 s. Good is under 3.8 s.

  • Total Blocking Time: 669 ms

    669 ms

    Scripts block taps and scrolling for 669 ms in total while the page loads. Good is under 200 ms.

  • Real-user INP: 207 ms

    207 ms

    Real visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 178 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 17% faster for real visitors

    -17%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.3 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.086

    0.086

    The layout barely moves while loading (CLS 0.086, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 99 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 99 requests on a phone: scripts 2.2 MB (30), images 1.5 MB (33) and other files 471 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • 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

9 to fixGoogle 8086
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 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.

  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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

4 to fixGoogle 9286
  • 11 H1 headlines

    There are 11 <h1> headlines (“CAMPAGNA FACCE”, “ATTENZIONE ALLE TRUFFE” and “RATING A3.1 DI CERVED RATING AGENCY”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.enegan.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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 127 internal links, 17 external

    The homepage links to 127 pages on enegan.it and 17 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Enegan, l’azienda che dà energia alle aziende, il tuo Energy Partner. Primi nel green e nel supporto al tuo business. S…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Enegan, Energy Partner | Luce, Gas, Telefonia, Efficientamento”.

  • Canonical URL set

    The canonical URL is https://www.enegan.it/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://www.enegan.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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

100
  • 3 pages slow to respond

    https://www.enegan.it/offerte-luce-e-gas-business, https://www.enegan.it/offerte-luce-azienda and https://www.enegan.it/efficientamento-energetico-aziende took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.

7 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.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

8 to fix38
  • 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.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 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.

  • 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 22 words

    The homepage has only about 22 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 enegan.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Angular
Hosting
Arubaenterprise

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on enegan.it, including 19 speed issues, 4 SEO issues and 8 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25