Website review, no card needed

prolon.ch logo

prolon.ch website review

Visit site (opens in a new tab)Reviewed 20 November 202627 issues · 69 checks

This review found 27 issues worth fixing on prolon.ch, 12 of them high impact, across 69 checks. The most urgent: avoid multiple page redirects. 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
2.4 s2.0 sAug 15Sep 52.3 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.3 s
Sep 5, 20262.3 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.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prolon.ch at 0.8 s0.8 s
  2. prolon.ch at 1.6 s1.6 s
  3. prolon.ch at 2.4 s2.4 s
  4. prolon.ch at 3.2 s3.2 s
  5. prolon.ch at 4.0 s4.0 s
  6. prolon.ch at 4.8 s4.8 s
  7. prolon.ch at 5.6 s5.6 s
  8. prolon.ch at 6.3 s6.3 s

Speed

7 to fix42
  • Avoid multiple page redirects

    13.4 s

    The page goes through 1 redirect before it starts loading, costing about 13.4 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    4.5 s · 680 KiB

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 6.7 s

    A phone's processor spends 6.7 s on main-thread work while loading, 3.1 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 (Klaviyo, Shopify and 506.io and others), adding 934 KiB and 507 ms of main-thread time.

  • 12 long tasks on the main thread

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

  • Klaviyo adds 154 ms

    154 ms

    Klaviyo costs a phone 154 ms of main-thread work and 323 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.

  • Reduce unused CSS

    19 KiB

    About 19 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

6 to fix49
  • Largest Contentful Paint: 21.4 s

    21.4 s

    Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “È iniziato il Black Month: Fino al −35% su tutti i prodotti…”.

  • Time to Interactive: 23.0 s

    23.0 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 642 ms

    642 ms

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

  • 1 image without width and height

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 528 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 528 requests on a phone: scripts 1.9 MB (170), other files 1.5 MB (265) and fonts 544 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.36 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9296
  • 20 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

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

  • 2 tap targets too small

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

  • ARIA tooltip elements do not have accessible names.

    ARIA tooltip elements do not have accessible names. (1 element).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

1 to fixGoogle 10099
  • No favicon declared

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

  • 60 internal links, 8 external

    The homepage links to 60 pages on prolon.ch and 8 external pages.

8 checks passed
  • Meta description: 91 characters

    Your meta description is 91 characters: “ProLon® is a food kit that includes all what you need for a 5-days Fasting Mimicking Diet™.”.

  • One H1 headline

    Your main headline reads: “<img src="//www.prolon.ch/cdn/shop/files/prolon-logo-2025_175x.webp?v=1754295773" srcset="//www.prolon.ch/cdn/shop/file…”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “ProLon® - Fast with food. – Prolon.ch”.

  • Canonical URL set

    The canonical URL is https://www.prolon.ch/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.prolon.ch/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.prolon.ch/collections/libro has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.prolon.ch/products/prolon, https://www.prolon.ch/products/prolonnextgen, https://www.prolon.ch/products/reset-next-gen-1-day, https://www.prolon.ch/products/nutrition-bar, https://www.prolon.ch/products/l-protein-bar and https://www.prolon.ch/products/fasting-shake and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://www.prolon.ch/products/prolon, https://www.prolon.ch/products/prolonnextgen, https://www.prolon.ch/products/reset-next-gen-1-day, https://www.prolon.ch/products/nutrition-bar, https://www.prolon.ch/products/l-protein-bar and https://www.prolon.ch/products/fasting-shake and 4 others have 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.

  • 15 internal pages checked

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

5 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.

  • 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

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 556 words of copy

    The homepage carries about 556 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Book "The Longevity Diet"”.

  • 2 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 of them by other companies (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.

  • 38 other companies contacted

    Loading the homepage contacts 38 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.ch, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Triplewhale · mailmunch.co · yotpo.com · chimpstatic.com · rechargecdn.com · dualsidedapp.com

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
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on prolon.ch, including 13 speed issues, 1 SEO issue and 3 conversion gaps. 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