prolon.me website review

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

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

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

8 third-party services load with your homepage (Clarity, Shopify and Google CDN and others), adding 1.1 MB and 451 ms of main-thread time.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

4 images could be 254 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Other Google APIs/SDKs costs a phone 22 ms of main-thread work and 506 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.

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. 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 67 ms. During a long task the page ignores taps.

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.

Your largest element takes 14.4 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 14.5 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.0 MB in 230 requests on a phone: other files 1.3 MB (130), scripts 867 KiB (53) and images 674 KiB (29). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (30 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.86 g of CO₂e: 103.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Form elements should have a visible label: 3 elements on the page fail 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: 22 elements on the page fail this check, rated moderate by axe-core.

8 visible links have no text or label, so screen readers cannot say where they go.

There are 2 <h1> headlines (“Prolon KSA Prolon KSA” and “برولون الجيل الجديد - برنامج مكافحة الشيخوخة وإنق…”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 29 pages on prolon.me and 4 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.

Your homepage links to https://www.prolon.me/%3Cspan%20class='notranslate'%3E%7B%7B%20link%20%7D%7D%3C/span%3E, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.prolon.me/products/prolon-next-gen-5-day-anti-aging-weightloss-program and https://www.prolon.me/products/prolon-original all use the title “برولون الجيل الجديد - برنامج مكافحة الشيخوخة وإنقاص الوزن لمدة 5 أيام…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.prolon.me/pages/the-science, https://www.prolon.me/collections/all, https://www.prolon.me/policies/refund-policy, https://www.prolon.me/policies/privacy-policy, https://www.prolon.me/policies/terms-of-service and https://www.prolon.me/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.prolon.me/products/prolon-next-gen-5-day-anti-aging-weightloss-program and https://www.prolon.me/products/prolon-original use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.prolon.me/pages/the-science, whose canonical is https://www.prolon.me/pages/scientific-research. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.prolon.me/pages/the-science and https://www.prolon.me/pages/returns-refunds have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.prolon.me/collections/all 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 10 pages linked from your homepage and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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.

The homepage has only about 32 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 18 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.