miyokos.com website review

About 571 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.

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

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

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

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

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

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (POWr, Shopify and Google Tag Manager and others), adding 833 KiB and 545 ms of main-thread time.

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

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

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

11 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PICNIC READY SUMMER VIBES ONLY: SNACK, SHARE, REPEAT! Picni…”.

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

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

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

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

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

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

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

Your homepage downloads 5.9 MB in 232 requests on a phone: images 3.5 MB (48), scripts 1.4 MB (89) and other files 620 KiB (65). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example butter-slider_1920x1188.webp at 1,920 px wide, shown at 296 px. Resized copies would save about 1.9 MB.

16 images (5.0 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.

7 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 41 pages on miyokos.com and 0 external pages.

A phone browser shows 1,051 words, but the HTML your server sends has only 274. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your homepage links to https://www.miyokos.com/blogs/blog/have-you-ever-thought-about-the-impact-of-pizza and https://www.miyokos.com/collections/food-service, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.miyokos.com/collections/all, https://www.miyokos.com/collections/plant-milk-cheese-spread, https://www.miyokos.com/pages/about-us, https://www.miyokos.com/pages/our-mission, https://www.miyokos.com/pages/making-an-impact and https://www.miyokos.com/pages/our-craft and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miyokos.com/collections/all, https://www.miyokos.com/collections/plant-milk-euro-butter, https://www.miyokos.com/collections/plant-milk-oat-milk-butter, https://www.miyokos.com/collections/plant-milk-cream-cheese, https://www.miyokos.com/collections/plant-milk-cheese-spread and https://www.miyokos.com/pages/about-us and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,051 words of visible text.

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

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

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