malefusy.pl website review

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

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

8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

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

4 third-party services load with your homepage (Google Tag Manager, mailerlite.com and Google Fonts and others), adding 395 KiB and 125 ms of main-thread time.

1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

About 64 KiB of JavaScript is downloaded but never used on this page.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.1 s).

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

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

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

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

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

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

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.0 MB in 81 requests on a phone: images 2.3 MB (8), scripts 265 KiB (29) and fonts 228 KiB (6). Under 2 MB keeps phones on slow connections fast.

7 images (2.0 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.

2 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

6 links have no real href, so search engines can't follow them.

The homepage links to 32 pages on malefusy.pl and 2 external pages.

There is no https://malefusy.pl/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.

https://malefusy.pl/alergeny, https://malefusy.pl/baby-shower, https://malefusy.pl/rezerwacja-przyjec, https://malefusy.pl/sklep/kawa-bez-spiny-spotaknie-dla-mam-z-dziecmi-fundacja-przy-tobie-x-tyle-frajdy, https://malefusy.pl/sklep/rytmika-nasz-sportowy-fyrtel and https://malefusy.pl/sklep/sensojoga-nasz-sportowy-fyrtel have no meta description, so Google writes the search snippet from whatever text it finds.

https://malefusy.pl/menu, https://malefusy.pl/baby-shower and https://malefusy.pl/kategoria-produktu/wydarzenia have no <h1> headline, so visitors and search engines get no clear main topic.

https://malefusy.pl/kategoria-produktu/wydarzenia has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://malefusy.pl/alergeny, https://malefusy.pl/baby-shower, https://malefusy.pl/urodzinki-dla-dzieci, https://malefusy.pl/kategoria-produktu/wydarzenia, https://malefusy.pl/kontakt and https://malefusy.pl/rezerwacja-przyjec and 3 others took over 3 s to send their HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 476 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 9 cookies (measured from a US location before any click).

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.

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