ams-web.jp website review

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

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

About 121 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

About 52 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.

4 third-party services load with your homepage (Google Tag Manager, Shopify and Vimeo and others), adding 190 KiB and 63 ms of main-thread time.

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

5 KiB could be saved by minifying CSS.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

Your largest element takes 7.3 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 7.3 s. Good is under 3.8 s.

The layout shifts by 0.158 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

2 images are downloaded at several times the size a phone draws them, for example 1_7bf7a060-4b09-4c87-81be-449e1e9a0eb5_large.jpg at 480 px wide, shown at 130 px. Resized copies would save about 39 KiB.

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

Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Your title is only 7 characters: “アットカグ公式”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 36 characters: “北欧系から西海岸系までおしゃれな家具をご販売！オフィス系の収納用品も充実”. 70 to 160 characters is enough to sell the click.

Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

3 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 96 pages on ams-web.jp and 2 external pages.

https://ams-web.jp/collections/%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/1%E4%BA%BA%E6%8E%9B%E3%81%91%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/2%E4%BA%BA%E6%8E%9B%E3%81%91%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/%E5%BA%A7%E6%A4%85%E5%AD%90-%E9%AB%98%E5%BA%A7%E6%A4%85%E5%AD%90-%E3%82%B9%E3%83%84%E3%83%BC%E3%83%AB, https://ams-web.jp/collections/%E5%BF%9C%E6%8E%A5%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC and https://ams-web.jp/collections/%E3%82%B3%E3%83%BC%E3%83%8A%E3%83%BC%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://ams-web.jp/collections/%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, whose canonical is https://ams-web.jp/collections/%e3%82%bd%e3%83%95%e3%82%a1%e3%83%bc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ams-web.jp/collections/%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/1%E4%BA%BA%E6%8E%9B%E3%81%91%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/2%E4%BA%BA%E6%8E%9B%E3%81%91%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/3%E4%BA%BA%E6%8E%9B%E3%81%91%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC, https://ams-web.jp/collections/%E5%BA%A7%E6%A4%85%E5%AD%90-%E9%AB%98%E5%BA%A7%E6%A4%85%E5%AD%90-%E3%82%B9%E3%83%84%E3%83%BC%E3%83%AB and https://ams-web.jp/collections/%E5%BF%9C%E6%8E%A5%E3%82%BD%E3%83%95%E3%82%A1%E3%83%BC 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.

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

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

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

1 image is served at too low a resolution for sharp phone screens.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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 8 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 and Google Tag Manager (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 9 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.