Website review, no card needed

prolon.ae logo

prolon.ae website review

Visit site (opens in a new tab)Reviewed 6 November 202642 issues · 88 checks

This review found 42 issues worth fixing on prolon.ae, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.8 s3.3 sAug 29Oct 33.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 29, 20263.4 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.4 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of prolon.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prolon.ae at 0.4 s0.4 s
  2. prolon.ae at 0.8 s0.8 s
  3. prolon.ae at 1.1 s1.1 s
  4. prolon.ae at 1.5 s1.5 s
  5. prolon.ae at 1.9 s1.9 s
  6. prolon.ae at 2.3 s2.3 s
  7. prolon.ae at 2.6 s2.6 s
  8. prolon.ae at 3.0 s3.0 s

Speed

10 to fix58
  • Render-blocking requests

    1.3 s

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

  • audioeye.com adds 1.1 s

    1.1 s

    audioeye.com costs a phone 1.1 s of main-thread work and 309 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 6.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, Shopify and l5id.com and others), adding 1.5 MB and 1.9 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Reduce unused JavaScript

    728 KiB

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

  • Reduce unused CSS

    600 ms · 125 KiB

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

  • Use efficient cache lifetimes

    414 KiB

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

  • 2,227 HTML elements

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

  • Shopify adds 177 ms

    177 ms

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    48 KiB

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

  • Duplicated JavaScript

    14 KiB

    14 KiB JavaScript is shipped twice across bundles.

  • Improve image delivery

    13 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix54
  • Largest Contentful Paint: 9.6 s

    9.6 s

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

  • Time to Interactive: 27.3 s

    27.3 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Total Blocking Time: 434 ms

    434 ms

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.045

    0.045

    The layout barely moves while loading (CLS 0.045, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 5.2 MB in 361 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 361 requests on a phone: scripts 2.4 MB (195), images 1.4 MB (48) and other files 762 KiB (90). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (525 KiB) 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.

  • 1 image far larger than shown

    20 KiB

    1 image is downloaded at several times the size a phone draws it, for example Frame_1321322776.jpg at 1,200 px wide, shown at 320 px. Resized copies would save about 20 KiB.

  • About 1.5 g of CO₂ per visit

    1.47 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

12 to fixGoogle 8385
  • 3 buttons without a name

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

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 7 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (2 elements).

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • All page content should be contained by landmarks (18 elements)

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (10 elements).

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9280
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Prolon® | The 5-day longevity & weight-loss program | Try it now! – Prolon ME”.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Live Longer. Feel Better Now!”, “"Prolon is my first choice for patients looking f…” and ““I love the science supporting Prolon, and I love…”). One clear main headline is easier for people and search engines.

  • Meta description is long (266 characters)

    Your meta description is 266 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No favicon declared

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 78 internal links, 7 external

    The homepage links to 78 pages on prolon.ae and 7 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://prolon.ae/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://prolon.ae/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,400 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://prolon.ae/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://prolon.ae/pages/science-v2 and https://prolon.ae/pages/fasting-mimicking-diet have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15123981&Ver=2&mid=d7464575-795e-47aa-8098-f70b10260e4c&bo=1&sid=32a53f20da0811f19eb8378f35cac38e&vid=32a56050da0811f199de1de73e285053&vids=1&msclkid=N&pi=918639831&lg.

  • 3 small tap targets

    3 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 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 ()”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No risk reducer

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

  • About 515 words of copy

    The homepage carries about 515 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP PROLON”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop”, “SIGN UP” and “SHOP ALL PRODUCTS”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 12 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and PostHog.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (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.

  • 30 cookies set on arrival

    30

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

  • No consent tool detected

    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.

  • 63 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at prolon.ae, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Triplewhale · Pagefly Ai Page Builder · Impact Com · Klaviyo Email Marketing Sms · Upcart · nice-team.net · cashewpayments.com · snapchat.com · rechargecdn.com · loox.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Vue.js
E-commerce
Shopify
Analytics
Google Analytics | PostHog | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on prolon.ae, including 15 speed issues and 5 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25