Website review, no card needed

olukai.com logo

olukai.com website review

Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 88 checks

This review found 39 issues worth fixing on olukai.com, 18 of them high impact, across 88 checks. The most urgent: main-thread work: 42.1 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s2.0 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20263.1 s
Jul 11, 20263.3 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
1.8 s426 msMay 30Nov 14583 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.0 s
Aug 22, 2026993 ms
Aug 29, 2026951 ms
Sep 5, 2026912 ms
Sep 12, 2026932 ms
Sep 19, 2026966 ms
Sep 26, 2026891 ms
Oct 3, 2026813 ms
Oct 10, 2026685 ms
Oct 17, 2026593 ms
Oct 24, 2026606 ms
Oct 31, 2026606 ms
Nov 7, 2026602 ms
Nov 14, 2026583 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

Full-page screenshot of olukai.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. olukai.com at 0.5 s0.5 s
  2. olukai.com at 1.0 s1.0 s
  3. olukai.com at 1.5 s1.5 s
  4. olukai.com at 2.0 s2.0 s
  5. olukai.com at 2.6 s2.6 s
  6. olukai.com at 3.1 s3.1 s
  7. olukai.com at 3.6 s3.6 s
  8. olukai.com at 4.1 s4.1 s

Speed

11 to fix28
  • Main-thread work: 42.1 s

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

  • Use efficient cache lifetimes

    1.4 s · 460 KiB

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

  • 11,814 HTML elements

    The page has 11,814 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Render-blocking requests

    1.1 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 5.7 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.9 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Shopify adds 448 ms

    448 ms

    Shopify costs a phone 448 ms of main-thread work and 1.1 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.

  • Improve image delivery

    523 KiB

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

  • Google Tag Manager adds 438 ms

    438 ms

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

  • Reduce unused CSS

    170 ms · 53 KiB

    About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify JavaScript

    100 KiB

    100 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    53 KiB

    Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need.

  • 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: 25 ms

    25 ms

    Your server sent the HTML in 25 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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 INP: 576 ms

    576 ms

    Real visitors wait 576 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Total Blocking Time: 9.8 s

    9.8 s

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

  • Time to Interactive: 37.6 s

    37.6 s

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

  • Largest Contentful Paint: 6.8 s

    6.8 s

    Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 10.6 s

    10.6 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.139

    0.139

    The layout shifts by 0.139 while loading, so content jumps under the reader's thumb. Good is under 0.1.

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 343 ms

    343 ms

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

  • Tap response (INP) got 63% faster for real visitors

    -63%

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

  • Largest content (LCP) got 25% faster for real visitors

    -25%

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

Images and page weight

2 to fix63
  • Page weight: 6.3 MB in 365 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 365 requests on a phone: scripts 2.8 MB (181), images 2.6 MB (84) and other files 288 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (197 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.8 g of CO₂ per visit

    1.80 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8892
  • Elements must only use permitted ARIA attributes (24 elements)

    Elements must only use permitted ARIA attributes: 24 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

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

  • 113 images without alt text

    113 images have no alt text, which hurts accessibility and image search.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h3 and h1 → h3), 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. (15 elements).

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • 4 H1 headlines

    There are 4 <h1> headlines (“OluKai”, “The Season of Comfort” and “The Season of Comfort”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 347)”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 220 internal links, 20 external

    The homepage links to 220 pages on olukai.com and 20 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Durable, Handmade, Premium Footwear. 1-Year Product Guarantee, Best-In-Class Customer Service, 30-Day Free Exchanges & …”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “OluKai Hawaiian-Inspired, Premium Footwear - Official Site”.

  • Canonical URL set

    The canonical URL is https://olukai.com/.

  • 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://olukai.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://olukai.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 (610 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://olukai.com/pages/upper-left-refer has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://olukai.com/collections/best-sellers, https://olukai.com/pages/faq-category/returns-and-exchanges, https://olukai.com/collections/mens-best-sellers, https://olukai.com/collections/mens-new-arrivals and https://olukai.com/collections/men-all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://olukai.com/pages/accessibility-statement, https://olukai.com/pages/upper-left-refer, https://olukai.com/pages/faq-category/returns-and-exchanges, https://olukai.com/pages/store-locator, https://olukai.com/products/olukai-e-gift-card and https://olukai.com/collections/mens-holiday-gift-guide 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 92 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=16004143&Ver=2&mid=e5d75535-ec5e-454b-88ac-fe40fe2f0fa2&bo=1&sid=1e607db0e43411f19b205d2fcb9a8996&vid=1e6089c0e43411f19726fd8bd2c9d339&vids=1&msclkid=N&pi=918639831&lg.

  • 13 small tap targets

    13 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_CLOSED”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 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 650 words of copy

    The homepage carries about 650 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 36 calls to action

    The homepage has 36 calls to action, for example “Contact”, “Shop All Styles” and “Shop All Men's”.

  • 7 short forms

    7 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks and 85 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • 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

1 to fix
  • 15 trackers load before any consent

    15

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 10 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.

  • 64 cookies set on arrival

    64

    Opening the homepage sets 64 cookies, 5 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.

  • 91 other companies contacted

    Loading the homepage contacts 91 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 olukai.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 21 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Tapcart Mobile App · Wyllo Formerly Nofraud · Nudge Olukai · Klaviyo Email Marketing Sms · Analyzify Ga4 Ads Tracking · Postscript Sms Marketing · Microsoft Clarity · Gdpr Cookie Consent · Applovin Shop Integration · Rivo Loyalty Rewards Referrals · Test Sms · cloudfront.net · unpkg.com · fbot.me · noibu.com · govx.com · googleapis.com · getredo.com · useamp.com · global-e.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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

Hiring

Hiring
59 open roles
Teams
OluKai Retail (16), Melin Retail (12), Roark Retail (9), OluKai Creative (2)
Job board
bamboohr

Company

Employees
170
Headquarters
Irvine

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 olukai.com, including 19 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
olukai.com website review: scores and fixes | Programmable