pipe.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.

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

6 third-party services load with your homepage (YouTube, Google Tag Manager and Cookiebot and others), adding 2.4 MB and 826 ms of main-thread time.

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

YouTube costs a phone 693 ms of main-thread work and 2.0 MB 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.

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 78 requests on a phone: scripts 2.4 MB (33), images 332 KiB (20) and fonts 258 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://pipe.com/assets/img/pipe-logo-light.svg")”.

The homepage links to 58 pages on pipe.com and 12 external pages.

There is no https://pipe.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://pipe.com/small-businesses has no <title>, so Google invents the link text in results.

https://pipe.com/small-businesses has no meta description, so Google writes the search snippet from whatever text it finds.

https://pipe.com/contact/sales, https://pipe.com/small-businesses, https://pipe.com/resources and https://pipe.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://pipe.com/contact/sales and https://pipe.com/careers 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.

https://pipe.com/small-businesses, https://pipe.com/developers and https://pipe.com/about took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 144 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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

Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

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