Website review, no card needed
mikunafoods.com website review
Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 86 checks
This review found 33 issues worth fixing on mikunafoods.com, 6 of them high impact, across 86 checks. The most urgent: 9 text elements with low contrast. 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,990 of 125,711 reviewed websitesbeats 93%
- #3,195 of 70,244 online storesbeats 93%
- #3,095 of 63,812 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 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 | 92 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 97 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 122 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Accessibe Accessibility Overlay, Clarity and Klaviyo and others), adding 1.2 MB and 673 ms of main-thread time.
Render-blocking requests
500 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
Shopify adds 98 ms
98 msShopify costs a phone 98 ms of main-thread work and 557 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 JavaScript
150 ms · 149 KiBAbout 149 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 111 KiB7 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
67 KiB11 files are served with short cache lifetimes, so returning visitors download them again (67 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MIKUNA Chocho Plant Protein, a single-ingredient Andean pla…”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 92 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, 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).
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: 129 ms
129 msReal visitors wait 129 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 159 ms
159 msScripts block the page for only 159 ms while loading. 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: 2.9 MB in 268 requests
2.9 MBYour homepage downloads 2.9 MB in 268 requests on a phone: scripts 933 KiB (114), other files 829 KiB (110) and images 586 KiB (23). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
82 KiB2 images are downloaded at several times the size a phone draws them, for example iHerb_logo_black.webp at 1,920 px wide, shown at 107 px. Resized copies would save about 82 KiB.
1 image in older formats
1 image (78 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 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.3 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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
64 form fields without a label
64 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 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. (3 elements).
1 checks passed
48 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: 48 passed and 6 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 short (7 characters)
Your title is only 7 characters: “MIKUNA®”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 8 problems
Structured data found ((untyped), BreadcrumbList, Dataset and FAQPage) but with 8 problems, for example “WebSite: sameAs is not an absolute URL ("facebook.com/mikunafoods")”.
60 internal links, 11 external
The homepage links to 60 pages on mikunafoods.com and 11 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Not Whey. Not Pea. Chocho.”.
Canonical URL set
The canonical URL is https://mikunafoods.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://mikunafoods.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,469 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mikunafoods.com/llms.txt (5 KiB, 18 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://mikunafoods.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://mikunafoods.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
https://mikunafoods.com/products/chocho-plant-protein-by-mikuna and https://mikunafoods.com/products/mikuna-plant-protein all use the title “Chocho Plant Protein – MIKUNA”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://mikunafoods.com/customer_authentication/redirect, https://mikunafoods.com/blogs/journal, https://mikunafoods.com/blogs/journal/tagged/recipes, https://mikunafoods.com/blogs/recipes and https://mikunafoods.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://mikunafoods.com/products/chocho-plant-protein-by-mikuna and https://mikunafoods.com/products/mikuna-plant-protein use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://mikunafoods.com/products/chocho-plant-protein-by-mikuna, whose canonical is https://mikunafoods.com/products/mikuna-plant-protein. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://mikunafoods.com/pages/mikuna-films and https://mikunafoods.com/customer_authentication/redirect 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 20 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
8 small tap targets
8 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,151 words of copy
The homepage carries about 1,151 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP CHOCHO”.
10 calls to action
The homepage has 10 calls to action, for example “Shop now”, “Shop” and “SHOP”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 13 testimonial or review blocks, 10 customer or partner logos, a star rating, 4 trust badges and “Trusted by 24,000+ customers”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
29 other companies contacted
Loading the homepage contacts 29 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 mikunafoods.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Tinyseo Ai Seo Speed · Uppromote Affiliate · Klaviyo Email Marketing Sms · Affliate By Secomapp · cloudfront.net · loox.io
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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Santa Barbara
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on mikunafoods.com, including 10 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.