loveamika.ca website review

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

About 461 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 2.4 s.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

8 third-party services load with your homepage (Shopify, gotolstoy.com and Google Tag Manager and others), adding 3.9 MB and 1.2 s of main-thread time.

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

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

Shopify costs a phone 685 ms of main-thread work and 2.2 MB 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.

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

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

gotolstoy.com costs a phone 146 ms of main-thread work and 409 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.

Vimeo costs a phone 28 ms of main-thread work and 550 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.

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

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.

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

Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a blonde model holds 'soft hair stars' an amika holiday hai…”.

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

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

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

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

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

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

1 image 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 112 ms to 108 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 3.3 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.2 MB in 278 requests on a phone: images 4.0 MB (67), scripts 2.3 MB (127) and other files 1.1 MB (63). Under 2 MB keeps phones on slow connections fast.

3ffb2c10a306a0b7c47f9e0a31e20163886f5521-628x628.gif weighs 934 KiB. On a phone connection a single image that size takes seconds.

6 images further down the page (163 KiB) 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 2.33 g of CO₂e: 279.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

16 tap targets are too small or too close together to hit reliably with a finger.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 115 pages on loveamika.ca and 18 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

The HTML your server sends has 648 of the 1,152 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

https://loveamika.ca/pages/offers has no <h1> headline, so visitors and search engines get no clear main topic.

https://loveamika.ca/collections/styling took over 3 s to send its HTML from our server.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Failed to execute 'appendChild' on 'Node': Unexpected token 'import'”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Ads (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 27 cookies, 2 of them by other companies (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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.