fallook.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Facebook and loox.io and others), adding 1.1 MB and 823 ms of main-thread time.

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

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

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

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

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

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.

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 7.1 MB in 454 requests on a phone: images 4.1 MB (47), other files 1.4 MB (210) and scripts 1.2 MB (178). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example IMG_5457_16babab4-f2e9-4c57-afef-54833441ccb2.png at 2,672 px wide, shown at 390 px. Resized copies would save about 184 KiB.

2 images (320 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.

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

13 elements hidden from screen readers can still receive keyboard focus.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 14 characters: “秋の尚品 – Fallook”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 204 pages on fallook.com and 0 external pages.

Your homepage links to https://fallook.com/collections/cat-dog, which answers with an error. Visitors hit a dead end and search engines drop it.

https://fallook.com/collections/all, https://fallook.com/collections/shopstyles-bags, https://fallook.com/collections/streetstyle-gorices, https://fallook.com/collections/pet/top, https://fallook.com/collections/pet-bag/bag-%E3%83%90%E3%83%83%E3%82%B0 and https://fallook.com/collections/pet-staff and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://fallook.com/collections/all, https://fallook.com/collections/shopstyles-bags, https://fallook.com/collections/shopstyle-clothes, https://fallook.com/collections/streetstyle-gorices, https://fallook.com/collections/pet/top and https://fallook.com/collections/pet-bag/bag-%E3%83%90%E3%83%83%E3%82%B0 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://fallook.com/collections/all, https://fallook.com/collections/shopstyles-bags, https://fallook.com/collections/shopstyle-clothes, https://fallook.com/collections/streetstyle-gorices, https://fallook.com/collections/pet/top and https://fallook.com/collections/pet-bag/bag-%E3%83%90%E3%83%83%E3%82%B0 and 8 others 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.

https://fallook.com/collections/pet/top, https://fallook.com/collections/pet-bag/bag-%E3%83%90%E3%83%83%E3%82%B0, https://fallook.com/collections/personalized-memorial-pet-with-photo and https://fallook.com/collections/pet-staff took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://fallook.com/.

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 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 47 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 15 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.