puppet.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Optimizely and storylane.io and others), adding 2.3 MB and 1.1 s of main-thread time.

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

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

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

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

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

storylane.io costs a phone 122 ms of main-thread work and 1.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.

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

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

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

Desktop scores 86 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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 0.42 (75th percentile). Good is under 0.1.

Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Secure, Scalable Automation Built for the Modern Enterprise…”.

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

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

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 177 requests on a phone: scripts 1.8 MB (61), images 1.4 MB (69) and stylesheets 127 KiB (10). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example temp-customer-national-security-agency-nsa.svg at 1,200 px wide, shown at 100 px. Resized copies would save about 473 KiB.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 link inside paragraphs relies on colour alone to stand out.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 84 pages on puppet.com and 38 external pages.

There is no /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.

/solutions/government, /professional-services/black-belt/contact, /customers/case-studies and /resources/podcasts have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /customers/case-studies, whose canonical is /customers. 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 34 found) and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'webrtc'.”.

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

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

1 link to other sites is dead, for example https://www.puppet-assessment.com/ (404).

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

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

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

Social proof on the homepage: 58 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 515 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 and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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