Website review, no card needed

procapslabs.com logo

procapslabs.com website review

Visit site (opens in a new tab)Reviewed 17 November 202645 issues · 88 checks

This review found 45 issues worth fixing on procapslabs.com, 20 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of procapslabs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. procapslabs.com at 1.2 s1.2 s
  2. procapslabs.com at 2.4 s2.4 s
  3. procapslabs.com at 3.6 s3.6 s
  4. procapslabs.com at 4.8 s4.8 s
  5. procapslabs.com at 6.0 s6.0 s
  6. procapslabs.com at 7.1 s7.1 s
  7. procapslabs.com at 8.3 s8.3 s
  8. procapslabs.com at 9.5 s9.5 s

Speed

12 to fix49
  • Use efficient cache lifetimes

    1.1 s · 2.3 MB

    68 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.5 s · 286 KiB

    About 286 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • audioeye-services.com adds 1.6 s

    1.6 s

    audioeye-services.com costs a phone 1.6 s of main-thread work and 293 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.

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.8 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-services.com, Google Tag Manager and Klaviyo and others), adding 1.7 MB and 2.6 s of main-thread time.

  • Improve image delivery

    750 ms · 1.4 MB

    35 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused JavaScript

    750 ms · 680 KiB

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

  • Minify CSS

    600 ms · 100 KiB

    100 KiB could be saved by minifying CSS.

  • Google Tag Manager adds 488 ms

    488 ms

    Google Tag Manager costs a phone 488 ms of main-thread work and 740 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.

  • Klaviyo adds 123 ms

    123 ms

    Klaviyo costs a phone 123 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.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    47 KiB

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • 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: 196 ms

    196 ms

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

Core Web Vitals

11 to fix33
  • 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 LCP: 7.2 s

    7.2 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 14.4 s

    14.4 s

    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 “ProCaps supplements”.

  • Time to Interactive: 23.5 s

    23.5 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user CLS: 0.12

    0.12

    For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 450 ms

    450 ms

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

  • 2 images without width and height

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

2 checks passed
  • Real-user INP: 127 ms

    127 ms

    Real visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix52
  • Page weight: 6.5 MB in 286 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 286 requests on a phone: images 2.3 MB (71), scripts 1.9 MB (69) and other files 1.8 MB (129). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    banner2-mobile-test is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    56 KiB

    2 images are downloaded at several times the size a phone draws them, for example find-your-formula-mobile-1200x1500.jpg at 1,200 px wide, shown at 350 px. Resized copies would save about 56 KiB.

  • 12 images below the first screen load straight away

    12 images further down the page (333 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.84 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 8789
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 19 text elements with low contrast

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

  • 4 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 26 elements on the page fail 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.

  • Alternative text of images should not be repeated as text (14 elements)

    Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 61 internal links, 5 external

    The homepage links to 61 pages on procapslabs.com and 5 external pages.

7 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “ProCaps Laboratories by Andrew Lessman. Your choice for all natural, additive free, premium vitamin and supplement form…”.

  • One H1 headline

    Your main headline reads: “The supplement brand trusted for over 45 years.”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Andrew Lessman | ProCaps Laboratories”.

  • Structured data in place

    Structured data found: OnlineStore 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://procapslabs.com/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.

2 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 (520 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 15 pages share a meta description

    https://procapslabs.com/collections/all-products, https://procapslabs.com/collections/best-sellers, https://procapslabs.com/specials, https://procapslabs.com/collections/wellness-essentials, https://procapslabs.com/collections/healthy-aging and https://procapslabs.com/collections/energy-metabolism and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5216656&tm=gtm002&Ver=2&mid=755a16f7-1a1b-40d5-901e-3bc3cb4d1e8d&bo=1&sid=c320a690e25e11f189c6db44c480ff6c&vid=c320b2e0e25e11f1b6956dd2089b87cf&vids=1&msclkid=N&pi=918.

  • 6 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 476 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more about ProCaps” and “LEARN MORE”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “SHOP”, “Shop All” and “Shop all products →”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

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

  • 32 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

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 procapslabs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Azure

Hiring

Hiring
32 open roles
Teams
Engineering (10), Production (5), Warehouse (5), Media/Creative (4)
Job board
workable

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on procapslabs.com, including 23 speed issues, 2 SEO issues and 2 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