Website review, no card needed
okendo.io website review
Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 77 checks
This review found 27 issues worth fixing on okendo.io, 8 of them high impact, across 77 checks. The most urgent: page weight: 58.3 MB in 202 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
91A- #1,463 of 116,180 reviewed websitesbeats 98%
- #670 of 66,745 online storesbeats 98%
- #642 of 60,924 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 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.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 240 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 222 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 187 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 259 ms |
| Aug 1, 2026 | 258 ms |
| Aug 8, 2026 | 242 ms |
| Aug 15, 2026 | 235 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 214 ms |
| Oct 3, 2026 | 192 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 226 ms |
| Oct 24, 2026 | 215 ms |
| Oct 31, 2026 | 239 ms |
| Nov 7, 2026 | 168 ms |
| Nov 14, 2026 | 150 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
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Improve image delivery
1.9 MB23 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
661 KiBAbout 661 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
303 KiB19 files are served with short cache lifetimes, so returning visitors download them again (303 KiB).
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Intercom, Facebook and Hubspot and others), adding 868 KiB and 430 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Minify JavaScript
37 KiB37 KiB could be saved by minifying JavaScript.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 50.6 s
50.6 sThe page becomes fully interactive after 50.6 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
11 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 544 ms
544 msReal visitors wait 544 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 240 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 199 ms
199 msScripts block the page for only 199 ms while loading. Good is under 200 ms.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Turn shoppers into Superfans”.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 58.3 MB in 202 requests
58.3 MBYour homepage downloads 58.3 MB in 202 requests on a phone: media 43.3 MB (9), images 13.3 MB (119) and scripts 1.6 MB (36). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
12 images far larger than shown
1.7 MB12 images are downloaded at several times the size a phone draws them, for example loyalty.png at 661 px wide, shown at 156 px. Resized copies would save about 1.7 MB.
7 images in older formats
7 images (2.8 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.
10 images below the first screen load straight away
10 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 16.5 g of CO₂ per visit
16.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.53 g of CO₂e: 1984.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 130 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Turn shoppers into Superfans” and “Scale your community across channels”). One clear main headline is easier for people and search engines.
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
90 internal links, 34 external
The homepage links to 90 pages on okendo.io and 34 external pages.
6 checks passed
Title: 36 characters
Your title is a healthy 36 characters: “Okendo - Customer Marketing Platform”.
Canonical URL set
The canonical URL is https://okendo.io/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://okendo.io/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://okendo.io/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (834 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://okendo.io/quizzes, https://okendo.io/surveys, https://okendo.io/referrals, https://okendo.io/inspiration, https://okendo.io/customer-stories/dixxon and https://okendo.io/customer-stories/terra-kaffe and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://okendo.io/book-a-demo, https://okendo.io/customer-stories/dixxon, https://okendo.io/customer-stories/terra-kaffe and https://okendo.io/customer-stories/neiwai have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 384 words of copy
The homepage carries about 384 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo”.
16 calls to action
The homepage has 16 calls to action, for example “Pricing”, “Book a demo” and “View pricing”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and 17 trust badges.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 11 of them by other companies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 okendo.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- WP Engine
Hiring
- Hiring
- 6 open roles
- Teams
- ENT Success (3), SMB Onboarding (3)
- Job board
- lever
- Careers page
- okendo.io/careers (opens in a new tab)
Company
- Employees
- 180
- Headquarters
- Sydney
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on okendo.io, including 10 speed issues, 2 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.