Your browser URL is www.bmcars.pl, however your Page Rule only covers bmcars.pl which is a different hostname. Try changing your rule to match on *bmcars.pl (with a wildcard), then use Trace to confirm your updated rule is being invoked on the URL you’re testing correctly.
Okay, so your rule seems to be applied correctly. When I visit https://www.bmcars.pl/wp-admin/, I don’t see any requests to https://www.bmcars.pl/cdn-cgi/zaraz/, confirming that Zaraz is disabled on that page:
However, when checking https://www.bmcars.pl/, I do see a request to https://www.bmcars.pl/cdn-cgi/zaraz/, meaning Zaraz is still loading on the main page:
From your Trace screenshot, the only rule invoked is your Page Rule. However, the rule appears under the name FPW Zaraz Enabled, even though the action applied is actually Disable Zaraz. This is a bug, and we will fix it.
One more thing: your cache rule cannot be triggered at all. It uses a filter ‘Hostname equals bmcars.pl/wp-admin’*, but:
the hostname condition only applies to the domain (not the path);
operator “equals” requires exact match and doesn’t support wildcards.
Because of this, the rule will never match any requests. If you’re trying to apply a rule to bmcars.pl/wp-admin*, you’ll need to use URI Full wildcard http*://bmcars.pl/wp-admin* instead.