wearemikra.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, Clarity and rebuyengine.com and others), adding 1.2 MB and 1.2 s of main-thread time.

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

alia-prod.com costs a phone 631 ms of main-thread work and 263 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.

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

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

rebuyengine.com costs a phone 161 ms of main-thread work and 332 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.

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

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

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.

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

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.9 MB in 304 requests on a phone: scripts 1.2 MB (93), other files 1.0 MB (174) and images 413 KiB (10). Under 2 MB keeps phones on slow connections fast.

formuila_7f6c3890-fa9b-4b5c-a848-a5039dfe1312.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

15 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h6, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 5 characters: “Mikra”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 58 pages on wearemikra.com and 2 external pages.

https://wearemikra.com/collections/hydrate and https://wearemikra.com/products/hydrate all use the title “Hydrate – Mikra”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wearemikra.com/collections/all-products, https://wearemikra.com/policies/privacy-policy, https://wearemikra.com/policies/refund-policy and https://wearemikra.com/blogs/blog/tagged/health-wellness have no meta description, so Google writes the search snippet from whatever text it finds.

https://wearemikra.com/collections/hydrate, https://wearemikra.com/collections/all-products, https://wearemikra.com/pages/meet-mikra, https://wearemikra.com/pages/ingredients-1, https://wearemikra.com/pages/faqs and https://wearemikra.com/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: “Trusted by 10,000+ Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 116 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Opening the homepage sets 21 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.