Website review, no card needed

mikunisushi.com logo

mikunisushi.com website review

Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 85 checks

This review found 38 issues worth fixing on mikunisushi.com, 9 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
2.8 s1.5 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.6 s
Jul 18, 20262.3 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
100 ms65 msMay 9Oct 2471 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202669 ms
May 16, 202669 ms
May 23, 202669 ms
May 30, 202670 ms
Jun 6, 202670 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202670 ms
Jul 11, 202672 ms
Jul 18, 202679 ms
Jul 25, 202684 ms
Aug 1, 202687 ms
Aug 8, 202688 ms
Aug 15, 202689 ms
Aug 22, 202692 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202691 ms
Sep 26, 202687 ms
Oct 3, 202679 ms
Oct 10, 202675 ms
Oct 17, 202671 ms
Oct 24, 202671 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 mikunisushi.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mikunisushi.com at 0.4 s0.4 s
  2. mikunisushi.com at 0.8 s0.8 s
  3. mikunisushi.com at 1.1 s1.1 s
  4. mikunisushi.com at 1.5 s1.5 s
  5. mikunisushi.com at 1.9 s1.9 s
  6. mikunisushi.com at 2.3 s2.3 s
  7. mikunisushi.com at 2.6 s2.6 s
  8. mikunisushi.com at 3.0 s3.0 s

Speed

10 to fix66
  • Improve image delivery

    7.1 s · 1.5 MB

    5 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (audioeye.com, Optanon and WordPress and others), adding 882 KiB and 948 ms of main-thread time.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 238 KiB

    About 238 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • audioeye.com adds 639 ms

    639 ms

    audioeye.com costs a phone 639 ms of main-thread work and 297 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

    450 ms · 145 KiB

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

  • Reduce unused CSS

    300 ms · 71 KiB

    About 71 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.

  • Optanon adds 212 ms

    212 ms

    Optanon costs a phone 212 ms of main-thread work and 364 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.

  • Main-thread work: 2.3 s

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

  • Legacy JavaScript

    250 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

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

    68 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “JOIN THE MIKUNI KOKI CLUB! EARN POINTS WITH EVERY QUALIFYIN…”.

  • Time to Interactive: 14.0 s

    14.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +3%

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

9 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.5 s

    1.5 s

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

  • Real-user INP: 68 ms

    68 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 475 ms

    475 ms

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

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

    -27%

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

  • Total Blocking Time: 87 ms

    87 ms

    Scripts block the page for only 87 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.023

    0.023

    The layout barely moves while loading (CLS 0.023, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 16.1 MB in 68 requests

    16.1 MB

    Your homepage downloads 16.1 MB in 68 requests on a phone: media 13.5 MB (1), images 1.8 MB (14) and scripts 568 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    70 KiB

    1 image is downloaded at several times the size a phone draws it, for example Mikuni_Logo_Tagline-Blue.png at 2,000 px wide, shown at 148 px. Resized copies would save about 70 KiB.

  • 2 images in older formats

    2 images (148 KiB) 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.

  • About 4.6 g of CO₂ per visit

    4.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.57 g of CO₂e: 548.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

8 to fixGoogle 8189
  • Certain ARIA roles must be contained by particular parents (6 elements)

    Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements marked as presentational should be consistently ignored (6 elements)

    Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

4 to fixGoogle 9284
  • Title is short (19 characters)

    Your title is only 19 characters: “Home - Mikuni Sushi”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Brand, BreadcrumbList, Organization and WebPage) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 29 internal links, 10 external

    The homepage links to 29 pages on mikunisushi.com and 10 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Since 1987, Mikuni has been innovating fresh Japanese dishes and serving eclectic sushi in a lively dining experience. …”.

  • One H1 headline

    Your main headline reads: “Japanese Tradition. American Innovation.”.

  • Canonical URL set

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

  • 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://mikunisushi.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://mikunisushi.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.

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 (378 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix69
  • 3 linked pages hidden from search

    https://mikunisushi.com/home-video-transcript, https://mikunisushi.com/terms-conditions and https://mikunisushi.com/privacy-policy-2 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    https://mikunisushi.com/menus, https://mikunisushi.com/menus/dinner, https://mikunisushi.com/menus/lunch-menu and https://mikunisushi.com/menus/dinner-for-two all use the title “Menus Archive - Mikuni Sushi”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://mikunisushi.com/locations, https://mikunisushi.com/home-video-transcript, https://mikunisushi.com/terms-conditions and https://mikunisushi.com/privacy-policy-2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://mikunisushi.com/menus, https://mikunisushi.com/menus/dinner, https://mikunisushi.com/menus/lunch-menu and https://mikunisushi.com/menus/dinner-for-two use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://mikunisushi.com/menus/dinner, whose canonical is https://mikunisushi.com/menus. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://mikunisushi.com/home-video-transcript, https://mikunisushi.com/terms-conditions and https://mikunisushi.com/privacy-policy-2 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://mikunisushi.com/shop, https://mikunisushi.com/menus, https://mikunisushi.com/menus/dinner, https://mikunisushi.com/menus/lunch-menu and https://mikunisushi.com/menus/dinner-for-two 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 and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    18 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: “over 80,000 active members”. 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 429 words of copy

    The homepage carries about 429 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Order” and “LEARN MORE”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Shop” and “Order”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mikunisushi.com, 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
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on mikunisushi.com, including 15 speed issues, 4 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