phenq.pl website review

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

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

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

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

8 third-party services load with your homepage (Hotjar, OptiMonk and Shopify and others), adding 1.0 MB and 685 ms of main-thread time.

Hotjar costs a phone 258 ms of main-thread work and 65 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.

OptiMonk costs a phone 141 ms of main-thread work and 309 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.

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

Shopify costs a phone 73 ms of main-thread work and 309 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

17 KiB JavaScript is shipped twice across bundles.

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

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 8.5 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 9.8 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.0 MB in 338 requests on a phone: other files 1.3 MB (215), scripts 989 KiB (76) and images 579 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image (115 KiB) is 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.

1 image further down the page (115 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

<dt> and <dd> elements must be contained by a <dl>: 12 elements on the page fail this check, rated serious by axe-core.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is 84 characters, so Google will cut it off around 60: “PhenQ Tabletki na odchudzanie | Tabletki na odchudzanie bez recepty – PhenQ (Polska)”.

There are 3 <h1> headlines (“PhenQ – naturalny suplement wspomagający kontrolę…”, “Pięć mocnych tabletek na odchudzanie w jednej” and “Uzyskaj idealną figurę szybko i łatwo”). One clear main headline is easier for people and search engines.

The homepage links to 17 pages on phenq.pl and 31 external pages.

Your homepage links to /a/withdrawal, which answers with an error. Visitors hit a dead end and search engines drop it.

/policies/refund-policy, /policies/privacy-policy and /policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: u is not a function”.

2 images are served at too low a resolution for sharp phone screens.

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: 61 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 3,282 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar and Klaviyo (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 15 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.