ntfy.pl website review

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

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

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

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

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

6 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

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

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

3 third-party services load with your homepage (Cookiebot, Google Tag Manager and Sentry), adding 438 KiB and 164 ms of main-thread time.

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.

2 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 6.1 MB in 368 requests on a phone: images 2.8 MB (96), scripts 2.1 MB (113) and other files 566 KiB (115). Under 2 MB keeps phones on slow connections fast.

desktop.png weighs 671 KiB. On a phone connection a single image that size takes seconds.

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

5 images are downloaded at several times the size a phone draws them, for example mobile-1.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 287 KiB.

9 images further down the page (349 KiB) 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 1.73 g of CO₂e: 207.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

85 elements use ARIA attributes their role does not allow, which confuses screen readers.

22 buttons have no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

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: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 74 characters, so Google will cut it off around 60: “Nice To Fit You - Dieta z wyborem menu - Wybieraj codziennie z 70 posiłków”.

The homepage links to 74 pages on ntfy.pl and 16 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 https://ntfy.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://ntfy.pl/sklep-select/oferta-jesienna is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://ntfy.pl/kontakt, https://ntfy.pl/diety-z-wyborem, https://ntfy.pl/pakiety-wyboru-menu, https://ntfy.pl/select, https://ntfy.pl/faq and https://ntfy.pl/dostawa and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ntfy.pl/kontakt, https://ntfy.pl/pakiety-wyboru-menu, https://ntfy.pl/faq and https://ntfy.pl/wybor-oferty have no <h1> headline, so visitors and search engines get no clear main topic.

https://ntfy.pl/wybor-oferty 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.

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

1 image failed to load on a phone, for example blob:https://ntfy.pl/cb8ad229-9f10-441c-9b5c-d0cb71d32693.

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

Large scripts ship without source maps.

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.

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 1,298 words of visible text.

Before a visitor clicks anything, the page loads 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 2 cookies (measured from a US location before any click).

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