Website review, no card needed
lekiusa.com website review
Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 86 checks
This review found 39 issues worth fixing on lekiusa.com, 16 of them high impact, across 86 checks. The most urgent: main-thread work: 16.4 s. 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
73C- #85,594 of 114,925 reviewed websitesbeats 22%
- #54,473 of 66,341 online storesbeats 15%
- #51,174 of 60,682 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 150 ms |
| Nov 7, 2026 | 151 ms |
| Nov 14, 2026 | 147 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
Main-thread work: 16.4 s
A phone's processor spends 16.4 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,198 HTML elements
The page has 5,198 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (withremark.com, Klaviyo and Facebook and others), adding 1.9 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
300 ms · 512 KiBAbout 512 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.
withremark.com adds 496 ms
496 mswithremark.com costs a phone 496 ms of main-thread work and 653 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.
Klaviyo adds 474 ms
474 msKlaviyo costs a phone 474 ms of main-thread work and 398 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.
Use efficient cache lifetimes
50 ms · 347 KiB81 files are served with short cache lifetimes, so returning visitors download them again (347 KiB).
Reduce unused CSS
300 ms · 76 KiBAbout 76 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 362 ms. During a long task the page ignores taps.
Facebook adds 290 ms
290 msFacebook costs a phone 290 ms of main-thread work and 274 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.
Clarity adds 266 ms
266 msClarity costs a phone 266 ms of main-thread work and 28 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.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Improve image delivery
31 KiB3 images could be 31 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
19 KiB19 KiB could be saved by minifying JavaScript.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
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
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: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Total Blocking Time: 797 ms
797 msScripts block taps and scrolling for 797 ms in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 111 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.229
0.229The layout shifts by 0.229 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 542 ms
542 msReal visitors wait 542 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 5.8 MB in 578 requests
5.8 MBYour homepage downloads 5.8 MB in 578 requests on a phone: images 2.3 MB (138), scripts 1.9 MB (158) and other files 1.2 MB (260). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
705 KiB3 images are downloaded at several times the size a phone draws them, for example 65620731_X.png at 3,840 px wide, shown at 133 px. Resized copies would save about 705 KiB.
1 image in older formats
1 image (445 KiB) is 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.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.65 g of CO₂e: 198.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (18 elements)
[role="img"] and [role="image"] elements must have alternative text: 18 elements on the page fail this check, rated serious by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 28 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 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 long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “LEKI USA #1 in Trekking poles, Trail Running Poles, Ski Poles & Gloves”.
437 internal links, 42 external
The homepage links to 437 pages on lekiusa.com and 42 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Top Quality and World Leading Trekking Poles, Trail Running Poles, Running Gloves, Ski Poles & Winter Gloves, and More …”.
One H1 headline
Your main headline reads: “ANSWER THE CALL OF WINTER.”.
Canonical URL set
The canonical URL is https://lekiusa.com/.
Structured data in place
Structured data found: OnlineStore, 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://lekiusa.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, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,815 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lekiusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://lekiusa.com/collections/poles has no <title>, so Google invents the link text in results.
1 page without a meta description
https://lekiusa.com/collections/poles has no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://lekiusa.com/collections/poles, https://lekiusa.com/collections/winter-for-poles, https://lekiusa.com/collections/alpine-skiing, https://lekiusa.com/collections/race-gear, https://lekiusa.com/collections/touring-backcountry and https://lekiusa.com/collections/mountaineering-skimo and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://lekiusa.com/collections/touring-backcountry and https://lekiusa.com/collections/trail-running 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 112 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.
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.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'parentNode')”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
22 of 27 tappable elements near the top are at least 24 px.
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: 1 customer or partner logo. 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.
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 948 words of copy
The homepage carries about 948 words of visible text.
3 checks passed
46 calls to action
The homepage has 46 calls to action, for example “Get a Grip”, “Submit your search request” and “Quick Buy”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
36 other companies contacted
Loading the homepage contacts 36 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 lekiusa.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Hulk Contact Form Builder · Comparable Products · Yoast Seo · Klaviyo Email Marketing Sms · Labeler · Microsoft Clarity · Customer Group Pricing · Back In Stock · Expertvoice · withremark.com · axtrics.com · insprd.tech
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on lekiusa.com, including 21 speed issues, 1 SEO issue 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.