pipefy.com website review

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

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

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

4 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.7 MB and 1.5 s of main-thread time.

Google Tag Manager costs a phone 877 ms of main-thread work and 1,001 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.

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

About 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With Al Agents, workflows and no-code, the future starts in…”.

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

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

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

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

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

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

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

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

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

The layout shifts by 0.137 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 12.7 MB in 163 requests on a phone: media 9.3 MB (2), scripts 1.8 MB (48) and images 979 KiB (40). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Software-Report-2-1-1-1.png at 1,000 px wide, shown at 96 px. Resized copies would save about 284 KiB.

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

2 images (68 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 118 pages on pipefy.com and 25 external pages.

robots.txt blocks Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/ai-agents has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187203164&tm=gtm002&Ver=2&mid=b60cd504-ceaf-48d1-b37b-0c8c5e660ea3&bo=3&sid=01e7aca0d34811f18a75d3fc03627a10&vid=01e7cf10d34811f1a20aab1ec9fa9157&vids=0&msclkid=N&pi=9.

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

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

pipefy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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