mixedemotion.net website review

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

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

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

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

4 third-party services load with your homepage (postscript.io, Shopify and JSDelivr CDN and others), adding 3.4 MB and 252 ms of main-thread time.

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

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

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

About 112 KiB of JavaScript is downloaded but never used on this page.

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

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.

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

Your 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 text “Γ”.

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

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

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

Your homepage downloads 17.6 MB in 91 requests on a phone: media 12.3 MB (1), images 4.4 MB (62) and scripts 535 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example 1_f550966b-3afe-44a7-8f59-62aab3532918.jpg at 3,983 px wide, shown at 390 px. Resized copies would save about 2.6 MB.

1 image (2.4 MB) 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.

1A96DED2-B1C7-4832-ABC0-F5EA50A8C6B3.jpg 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 4.97 g of CO₂e: 597.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 images have no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 136 pages on mixedemotion.net and 0 external pages.

There is no https://mixedemotion.net/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://mixedemotion.net/pages/coming-soon-1 has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was 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 966 words of visible text.

Opening the homepage sets 7 cookies, 1 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.