pulley.com website review

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

Your mobile performance score is 67 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 2.4 MB and 689 ms of main-thread time.

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

website-files.com costs a phone 258 ms of main-thread work and 1.7 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.

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

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

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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.

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

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

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

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pulley's Cap Table Dashboard preview”.

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

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

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

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

Your homepage downloads 2.5 MB in 68 requests on a phone: scripts 927 KiB (29), images 803 KiB (18) and other files 460 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements use prohibited ARIA attributes (1 element).

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 108 pages on pulley.com and 13 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://pulley.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://pulley.com/products/cap-table-management/token-cap-tables and https://pulley.com/products/crypto/token-cap-tables all use the title “Token Cap Table Software | Simplify your Crypto Token Operations with…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://pulley.com/products/cap-table-management/equity-cap-tables, https://pulley.com/products/crypto/token-distribution and https://pulley.com/products/capital-transactions/token-distribution use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://pulley.com/products/compliance/crypto-valuations, whose canonical is https://pulley.com/products/fundraising/crypto-valuations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector') https://pulley.com/:671:35”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

The homepage carries about 905 words of visible text.

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

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

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

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.

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