enea.pl website review

50 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

The HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 1.4 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Reduce initial server response time. Google estimates savings of 1.3 s on a phone.

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

7 third-party services load with your homepage (Google Tag Manager, Cookiebot and Other Google APIs/SDKs and others), adding 1.7 MB and 1.5 s of main-thread time.

About 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

The page has 2,927 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

21 KiB could be saved by minifying JavaScript.

19 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Strony internetowe portalu enea.pl, operator.enea.pl oraz S…”.

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

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

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

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

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

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

shutterstock_2323448587.jpg weighs 9.0 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example shutterstock_2323448587.jpg at 5,368 px wide, shown at 350 px. Resized copies would save about 8.7 MB.

3 images (9.2 MB) 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.

Your homepage downloads 3.3 MB in 94 requests on a phone: scripts 1.8 MB (50), stylesheets 470 KiB (18) and HTML 449 KiB (3). Under 2 MB keeps phones on slow connections fast.

ENEA_magazyn_energii_baner_1280x430_sticker_10-2026_1.png.we is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Some list items are not inside a list.

All page content should be contained by landmarks: 3 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: 2 elements on the page fail this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 4 characters: “Enea”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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 at https://www.enea.pl/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 122 pages on enea.pl and 30 external pages.

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.

There is no /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.

/male-firmy, /biznes, /strona-korporacyjna, /transformacja-energetyczna/enea-eko, /dla-domu/oferta and /dla-domu/urzadzenia and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/transformacja-energetyczna/enea-eko, /enea-search/enea-search-modal, /eneasprzedaz and /klimatyzacje have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 links go through two or more redirects, for example https://moja.enea.pl/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

enea.pl's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,255 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics 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.

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

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