Website review, no card needed

pipingrock.com logo

pipingrock.com website review

Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 90 checks

This review found 34 issues worth fixing on pipingrock.com, 11 of them high impact, across 90 checks. The most urgent: fails Core Web Vitals for real visitors. 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.6 s2.5 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
588 ms408 msMay 16Oct 31466 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026444 ms
May 23, 2026448 ms
May 30, 2026454 ms
Jun 6, 2026463 ms
Jun 13, 2026467 ms
Jun 20, 2026470 ms
Jun 27, 2026480 ms
Jul 4, 2026488 ms
Jul 11, 2026493 ms
Jul 18, 2026483 ms
Jul 25, 2026455 ms
Aug 1, 2026438 ms
Aug 8, 2026429 ms
Aug 15, 2026446 ms
Aug 22, 2026481 ms
Aug 29, 2026518 ms
Sep 5, 2026545 ms
Sep 12, 2026562 ms
Sep 19, 2026567 ms
Sep 26, 2026553 ms
Oct 3, 2026538 ms
Oct 10, 2026522 ms
Oct 17, 2026505 ms
Oct 24, 2026497 ms
Oct 31, 2026466 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

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

How it loaded on a phone

  1. pipingrock.com at 0.8 s0.8 s
  2. pipingrock.com at 1.6 s1.6 s
  3. pipingrock.com at 2.4 s2.4 s
  4. pipingrock.com at 3.2 s3.2 s
  5. pipingrock.com at 4.1 s4.1 s
  6. pipingrock.com at 4.9 s4.9 s
  7. pipingrock.com at 5.7 s5.7 s
  8. pipingrock.com at 6.5 s6.5 s

Speed

10 to fix58
  • Main-thread work: 5.4 s

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

  • 4,316 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and Clarity and others), adding 1.9 MB and 896 ms 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

    824 KiB

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

  • Render-blocking requests

    600 ms

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

  • Reduce unused CSS

    300 ms · 108 KiB

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

  • Shopify adds 297 ms

    297 ms

    Shopify costs a phone 297 ms of main-thread work and 722 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 175 ms

    175 ms

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

  • rebuyengine.com adds 112 ms

    112 ms

    rebuyengine.com costs a phone 112 ms of main-thread work and 295 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.

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    40 KiB

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

  • Improve image delivery

    33 KiB

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

  • Use efficient cache lifetimes

    29 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

    33 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Time to Interactive: 25.1 s

    25.1 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Real-user INP: 347 ms

    347 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 912 ms

    912 ms

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

  • Total Blocking Time: 541 ms

    541 ms

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 444 ms to 466 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.091

    0.091

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

Images and page weight

2 to fix64
  • Page weight: 6.7 MB in 412 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 412 requests on a phone: other files 3.1 MB (151), scripts 2.0 MB (141) and images 1.1 MB (93). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    SportSupp_412x230_23dd0f1c-e849-492e-944f-1d7caf150582.jpg 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).

  • About 1.9 g of CO₂ per visit

    1.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.90 g of CO₂e: 228.1 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 are sized for phones

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

Accessibility

6 to fixGoogle 8892
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 8 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 6 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Elements marked as presentational should be consistently ignored (15 elements)

    Elements marked as presentational should be consistently ignored: 15 elements on the page fail this check, rated minor by axe-core.

  • 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 169 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 375 internal links, 2 external

    The homepage links to 375 pages on pipingrock.com and 2 external pages.

7 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “With Piping Rock®, You Can Save Up To 25% On Vitamins, Supplements, Essential Oils & More!”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Highest Quality Supplements, Vitamins and Health Products”.

  • Canonical URL set

    The canonical URL is https://www.pipingrock.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Product 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.pipingrock.com/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.pipingrock.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.pipingrock.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.pipingrock.com/policies/privacy-policy, https://www.pipingrock.com/policies/terms-of-service, https://www.pipingrock.com/pages/loyalty-program and https://www.pipingrock.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.pipingrock.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 9284
  • 3 broken images

    3 images failed to load on a phone, for example https://pipingrock.com/cdn/shop/t/214/assets/PIP-logo-Website_SPACE_Tagline.svg?v=103807066674097198451753378734.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    112 of 125 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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.

  • About 1,278 words of copy

    The homepage carries about 1,278 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Crazy Deals – Shop now” and “SHOP NOW”.

  • 38 calls to action

    The homepage has 38 calls to action, for example “Shop All Products”, “Shop All Vitamins” and “Shop All Supplements”.

  • 25 short forms

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

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks, a star rating and 27 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 pipingrock.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
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Employees
1,346
Headquarters
Ronkonkoma

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on pipingrock.com, including 18 speed issues, 1 SEO issue and 1 conversion gap. 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