Website review, no card needed
grivel.com website review
Visit site (opens in a new tab)Reviewed 9 November 202624 issues · 78 checks
This review found 24 issues worth fixing on grivel.com, 7 of them high impact, across 78 checks. The most urgent: page weight: 15.3 MB in 280 requests. 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
88B- #5,711 of 120,337 reviewed websitesbeats 93%
- #3,135 of 68,137 online storesbeats 93%
- #3,035 of 62,092 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 196 ms |
| May 23, 2026 | 215 ms |
| May 30, 2026 | 244 ms |
| Jun 6, 2026 | 262 ms |
| Jun 13, 2026 | 262 ms |
| Jun 20, 2026 | 267 ms |
| Jun 27, 2026 | 270 ms |
| Jul 4, 2026 | 274 ms |
| Jul 11, 2026 | 279 ms |
| Jul 18, 2026 | 278 ms |
| Jul 25, 2026 | 272 ms |
| Aug 1, 2026 | 265 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 259 ms |
| Aug 22, 2026 | 250 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 158 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 155 ms |
| Oct 31, 2026 | 157 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
5,930 HTML elements
The page has 5,930 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
300 ms · 373 KiBAbout 373 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Google Tag Manager and others), adding 1.1 MB and 533 ms of main-thread time.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 154 ms
154 msKlaviyo costs a phone 154 ms of main-thread work and 422 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 241 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
128 KiB20 files are served with short cache lifetimes, so returning visitors download them again (128 KiB).
Improve image delivery
73 KiB4 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “G20+ LT”.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 292 ms
292 msScripts block taps and scrolling for 292 ms in total while the page loads. Good is under 200 ms.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 589 ms
589 msReal visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 196 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 15.3 MB in 280 requests
15.3 MBYour homepage downloads 15.3 MB in 280 requests on a phone: media 11.9 MB (4), scripts 1.3 MB (114) and other files 842 KiB (115). Under 2 MB keeps phones on slow connections fast.
About 4.3 g of CO₂ per visit
4.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.35 g of CO₂e: 521.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
130 internal links, 12 external
The homepage links to 130 pages on grivel.com and 12 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Grivel designs and manufactures precision mountain equipment, shaped for traction and refined through continuous iterat…”.
One H1 headline
Your main headline reads: “G20+ LT”.
Title: 48 characters
Your title is a healthy 48 characters: “Grivel | Precision Mountain Equipment Since 1818”.
Canonical URL set
The canonical URL is https://grivel.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://grivel.com/sitemap.xml.
AI search readiness
4 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 (332 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://grivel.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without an H1
https://grivel.com/collections/mountaineering, https://grivel.com/collections/rock-climbing, https://grivel.com/collections/ice-climbing, https://grivel.com/collections/ski-mountaineering, https://grivel.com/products/spartan-x-30 and https://grivel.com/collections/ice-axes and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://grivel.com/collections/mountaineering, https://grivel.com/collections/rock-climbing, https://grivel.com/collections/ice-climbing, https://grivel.com/collections/ski-mountaineering, https://grivel.com/collections/trail-running and https://grivel.com/products/spartan-x-30 and 2 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
22 small tap targets
22 of 83 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 359 words of copy
The homepage carries about 359 words of visible text.
4 checks passed
19 calls to action
The homepage has 19 calls to action, for example “Try again”, “shop all ice axes” and “shop all crampons”.
7 short forms
7 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 2 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 2 of them by other companies (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.
33 other companies contacted
Loading the homepage contacts 33 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 grivel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Lucky Orange · Regios Discounts · Itable · Klaviyo Email Marketing Sms · Judge Me Reviews · Hulk Form Builder · Smart Seo · Gorgias Live Chat Helpdesk · Stack Discounts Pro · Oc Openai Ads Chatgpt Pixel · Restockrocket · amazonaws.com · webgains.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 1818
- Headquarters
- Courmayeur
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on grivel.com, including 11 speed 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.