Website review, no card needed
prolon.co.uk website review
Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 97 checks
This review found 47 issues worth fixing on prolon.co.uk, 17 of them high impact, across 97 checks. The most urgent: audioeye.com adds 1.9 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #87,215 of 124,967 reviewed websitesbeats 26%
- #54,698 of 70,076 online storesbeats 18%
- #51,364 of 63,690 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 199 ms |
| May 23, 2026 | 203 ms |
| May 30, 2026 | 202 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 201 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 189 ms |
| Aug 8, 2026 | 189 ms |
| Aug 15, 2026 | 201 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 209 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 200 ms |
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
Speed
audioeye.com adds 1.9 s
1.9 saudioeye.com costs a phone 1.9 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.
Render-blocking requests
1.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 11.1 s
A phone's processor spends 11.1 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (audioeye.com, Klaviyo and l5id.com and others), adding 2.1 MB and 3.2 s of main-thread time.
Reduce unused JavaScript
880 KiBAbout 880 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
450 ms · 160 KiBAbout 160 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
539 KiB29 files are served with short cache lifetimes, so returning visitors download them again (539 KiB).
Klaviyo adds 371 ms
371 msKlaviyo costs a phone 371 ms of main-thread work and 639 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.
2,882 HTML elements
The page has 2,882 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 150 ms
150 msShopify costs a phone 150 ms of main-thread work and 388 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.
Legacy JavaScript
88 KiBPolyfills for old browsers add 88 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Improve image delivery
11 KiB1 image could be 11 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.
1 checks passed
Server response: 81 ms
81 msYour server sent the HTML in 81 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Speed Index: 18.3 s
18.3 sVisually, the page fills in at 18.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 33.0 s
33.0 sThe page becomes fully interactive after 33.0 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 956 ms
956 msReal visitors wait 956 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 199 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 391 requests
5.1 MBYour homepage downloads 5.1 MB in 391 requests on a phone: scripts 2.9 MB (220), other files 992 KiB (108) and images 574 KiB (32). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
43 KiB2 images are downloaded at several times the size a phone draws them, for example Frame_1321322778.jpg at 1,200 px wide, shown at 320 px. Resized copies would save about 43 KiB.
About 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
9 text elements with low contrast
9 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).
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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).
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 (12 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (7 elements).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
161 internal links, 8 external
The homepage links to 161 pages on prolon.co.uk and 8 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Clinically tested 5‑day Fasting Mimicking Diet to support weight management, metabolic health and cellular rejuvenation…”.
One H1 headline
Your main headline reads: “Black Month is here”.
Title: 51 characters
Your title is a healthy 51 characters: “ProLon UK | 5‑Day Fasting Mimicking Diet (FMD) Kits”.
Canonical URL set
The canonical URL is https://prolon.co.uk/.
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.co.uk/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,847 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://prolon.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://prolon.co.uk/collections/all and https://prolon.co.uk/pages/fasting-group have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://prolon.co.uk/collections/all, https://prolon.co.uk/pages/fasting-group, https://prolon.co.uk/products/prolon-5-day-kit, https://prolon.co.uk/collections/shop-all and https://prolon.co.uk/products/fasting-shake have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://prolon.co.uk/collections/shop-all took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15123981&Ver=2&mid=7c60a061-1704-4d08-b15c-d8269e2e43c0&bo=1&sid=d753a460d9d311f185cf7f8e5d6e4d0f&vid=d753c590d9d311f19c8aa1e53c25f41e&vids=1&msclkid=N&pi=918639831&lg.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to fetch r.fetch (https://prolon.co.uk/cdn/wpm/sb8a4071cw5df52f02p06561c06md4694b52m.js:1:74498) https://prolon.…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 793 words of copy
The homepage carries about 793 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 NOW” and “Shop Now”.
25 calls to action
The homepage has 25 calls to action, for example “Shop”, “SHOP ALL PRODUCTS” and “SHOP ALL”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 12 customer or partner logos, a star rating, 2 trust badges and “12,000+ reviews”.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and PostHog.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.
37 cookies set on arrival
37Opening the homepage sets 37 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.
61 other companies contacted
Loading the homepage contacts 61 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.co.uk, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Schema Plus For Seo · Intelligems A B Testing · Eg Auto Add To Cart · Triplewhale · Microsoft Clarity · Seowill Ai Seo · Fseo Ai · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Trymry · rechargecdn.com · rise-ai.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
- 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 47 issues on prolon.co.uk, including 23 speed issues, 3 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.