Website review, no card needed
petzl.com website review
Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 81 checks
This review found 32 issues worth fixing on petzl.com, 13 of them high impact, across 81 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #21,039 of 116,363 reviewed websitesbeats 77%
- #13,803 of 66,764 online storesbeats 73%
- #13 of 272 Salesforce Commerce Cloud storesbeats 93%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 304 ms |
| May 16, 2026 | 308 ms |
| May 23, 2026 | 309 ms |
| May 30, 2026 | 304 ms |
| Jun 6, 2026 | 304 ms |
| Jun 13, 2026 | 303 ms |
| Jun 20, 2026 | 304 ms |
| Jun 27, 2026 | 304 ms |
| Jul 4, 2026 | 307 ms |
| Jul 11, 2026 | 309 ms |
| Jul 18, 2026 | 308 ms |
| Jul 25, 2026 | 304 ms |
| Aug 1, 2026 | 303 ms |
| Aug 8, 2026 | 302 ms |
| Aug 15, 2026 | 304 ms |
| Aug 22, 2026 | 304 ms |
| Aug 29, 2026 | 301 ms |
| Sep 5, 2026 | 302 ms |
| Sep 12, 2026 | 301 ms |
| Sep 19, 2026 | 303 ms |
| Sep 26, 2026 | 303 ms |
| Oct 3, 2026 | 300 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 112 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
Speed
Improve image delivery
15.3 s · 2.5 MB3 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.3 s faster on a phone.
Use efficient cache lifetimes
3.3 s · 486 KiB27 files are served with short cache lifetimes, so returning visitors download them again (486 KiB).
Reduce unused JavaScript
1.3 s · 245 KiBAbout 245 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
1.2 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 84 KiBAbout 84 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.
6 third-party services on the page
6 third-party services load with your homepage (hcaptcha.com, Optanon and Google Tag Manager and others), adding 554 KiB and 359 ms of main-thread time.
Legacy JavaScript
150 ms · 45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 468 ms of it running JavaScript. That is comfortably low.
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 31.6 s
31.6 sYour largest element takes 31.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 31.6 s
31.6 sThe page becomes fully interactive after 31.6 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 934 ms
934 msReal visitors wait 934 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 63% faster for real visitors
-63%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 304 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 59% faster for real visitors
-59%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 49 ms
49 msScripts block the page for only 49 ms while loading. Good is under 200 ms.
Images and page weight
4 images over 500 KB
4 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.
Page weight: 5.8 MB in 45 requests
5.8 MBYour homepage downloads 5.8 MB in 45 requests on a phone: images 5.0 MB (18), scripts 533 KiB (9) and HTML 106 KiB (1). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (5.0 MB) 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.
About 1.6 g of CO₂ per visit
1.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.64 g of CO₂e: 197.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (25 characters)
Your title is only 25 characters: “Explore Petzl – Petzl USA”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
39 internal links, 13 external
The homepage links to 39 pages on petzl.com and 13 external pages.
6 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “New products, innovative equipment, tech tips and resources, adventure stories and trip reports, field insights, and mo…”.
One H1 headline
Your main headline reads: “Start Exploring with Petzl”.
Canonical URL set
The canonical URL is https://www.petzl.com/us/en.
Structured data in place
Structured data found: Organization and WebPage.
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.petzl.com/fr/fr/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.petzl.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.
3 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 (450 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://www.petzl.com/us/en/professional, https://www.petzl.com/us/en/sport, https://www.petzl.com/us/en/operators and https://www.petzl.com/us/en/tactical all use the title “Explore Petzl Professional – Petzl USA”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.petzl.com/brand/s/Industrial-Excellence has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://www.petzl.com/us/en/professional, https://www.petzl.com/us/en/sport, https://www.petzl.com/us/en/operators and https://www.petzl.com/us/en/tactical use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.petzl.com/us/en/professional, https://www.petzl.com/us/en/sport, https://www.petzl.com/us/en/operators, https://www.petzl.com/brand/s/Industrial-Excellence, https://www.petzl.com/us/en/sport/we-are-petzl/running/facilitating-reparability/-W21--NEWS--Pieces-detachees_SPO_a7CTx0000000FFBMA2.html and https://www.petzl.com/us/en/faq and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.petzl.com/brand/s/Industrial-Excellence has 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.
1 page slow to respond
https://www.petzl.com/brand/s/Industrial-Excellence took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unexpected token '.'”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 307 words of copy
The homepage carries about 307 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Subscribe”, “Help and Contact” and “Join Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
6 other companies contacted
Loading the homepage contacts 6 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 petzl.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Sewan
Company
- Employees
- 77
- Founded
- 1968
- Headquarters
- Crolles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on petzl.com, including 13 speed issues, 3 SEO issues and 3 conversion gaps. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.