Website review, no card needed
orukayak.com website review
Visit site (opens in a new tab)Reviewed 19 November 202650 issues · 89 checks
This review found 50 issues worth fixing on orukayak.com, 26 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
62D- #117,184 of 122,161 reviewed websitesbeats 3%
- #67,884 of 69,033 online storesbeats 1%
- #62,072 of 62,894 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 4.0 s |
| Nov 7, 2026 | 3.9 s |
| Nov 14, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 166 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 174 ms |
| Oct 31, 2026 | 174 ms |
| Nov 7, 2026 | 169 ms |
| Nov 14, 2026 | 158 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
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.3 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Reduce unused JavaScript
42.0 s · 6.4 MBAbout 6.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 42.0 s faster on a phone.
YouTube adds 2.6 s
2.6 sYouTube costs a phone 2.6 s of main-thread work and 9.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
2.9 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Use efficient cache lifetimes
1.5 s · 715 KiB28 files are served with short cache lifetimes, so returning visitors download them again (715 KiB).
Reduce unused CSS
1.5 s · 186 KiBAbout 186 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,174 HTML elements
The page has 3,174 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
14.1 MB14 images could be 14.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Shopify and Google Tag Manager and others), adding 27.5 MB and 3.8 s of main-thread time.
Shopify adds 453 ms
453 msShopify costs a phone 453 ms of main-thread work and 16.6 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 302 ms. During a long task the page ignores taps.
Google Tag Manager adds 249 ms
249 msGoogle Tag Manager costs a phone 249 ms of main-thread work and 370 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
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 26.8 s
26.8 sThe first text or image appears after 26.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 82.0 s
82.0 sYour largest element takes 82.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 38.2 s
38.2 sVisually, the page fills in at 38.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 105.2 s
105.2 sThe page becomes fully interactive after 105.2 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 149 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 29.3 MB in 326 requests
29.3 MBYour homepage downloads 29.3 MB in 326 requests on a phone: images 15.5 MB (52), scripts 11.3 MB (152) and stylesheets 931 KiB (35). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (2.1 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.
An image on the first screen is lazy-loaded
Group_1_2143ddc6-93e2-460e-80b0-605261abb7a0.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
38 KiB1 image is downloaded at several times the size a phone draws it, for example df57d4a97fda976d55fae0c55a8bb3e6.png at 343 px wide, shown at 70 px. Resized copies would save about 38 KiB.
About 8.3 g of CO₂ per visit
8.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.29 g of CO₂e: 995.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 buttons without a name
18 buttons have no accessible name, so screen readers announce just “button”.
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 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.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
8 H1 headlines
There are 8 <h1> headlines (“FROM BOX TO BOAT IN MINUTES”, “FROM BOX TO BOAT IN MINUTES” and “Durable”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
31 internal links, 30 external
The homepage links to 31 pages on orukayak.com and 30 external pages.
3 checks passed
Title: 43 characters
Your title is a healthy 43 characters: “Folding Kayaks That Go Anywhere | Oru Kayak”.
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.orukayak.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.orukayak.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (774 words), so crawlers that don't run JavaScript still read it.
Other pages
6 linked pages are broken
Your homepage links to https://www.orukayak.com/instagram.com/mortske.media, https://www.orukayak.com/instagram.com/wanderlustallgaeu, https://www.orukayak.com/instragram.com/myinnerwild, https://www.orukayak.com/instagram.com/jmurphyphotos, https://www.orukayak.com/instagram.com/spencerwatson.ca and https://www.orukayak.com/instagram.com/outfullsending, which answer with an error. Visitors hit a dead end and search engines drop them.
9 pages without a meta description
https://www.orukayak.com/collections/oru-kayaks, https://www.orukayak.com/collections/all, https://www.orukayak.com/pages/buy-back-program, https://www.orukayak.com/products/gift-card, https://www.orukayak.com/pages/quiz and https://www.orukayak.com/collections/landscape-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 checks passed
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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://oru-kayak.myshopify.com/cdn/shop/files/pandectes-banner-logo.png.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Error: Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full m…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
106 of 130 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 1,221 words of copy
The homepage carries about 1,221 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “SHOP KAYAKS”.
4 calls to action
The homepage has 4 calls to action, for example “SHOP KAYAKS”, “SUBSCRIBE” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager 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.
33 cookies set on arrival
33Opening the homepage sets 33 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.
46 other companies contacted
Loading the homepage contacts 46 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 orukayak.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Remix
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Emeryville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on orukayak.com, including 24 speed issues, 5 SEO issues and 2 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.