etnytrico.com website review

64 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).

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

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

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

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

8 third-party services load with your homepage (Google Maps, Google Tag Manager and SnapWidget and others), adding 4.3 MB and 489 ms of main-thread time.

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

Instagram costs a phone 0 ms of main-thread work and 3.5 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.

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

Google Maps costs a phone 278 ms of main-thread work and 493 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.

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

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

5 KiB could be saved by minifying JavaScript.

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

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.

5 KiB could be saved by minifying CSS.

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

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

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

15 images 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 7.5 MB in 87 requests on a phone: images 6.4 MB (45), scripts 950 KiB (27) and fonts 76 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 20180408_ff8ae2.jpg at 3,333 px wide, shown at 390 px. Resized copies would save about 349 KiB.

2 images (428 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.11 g of CO₂e: 253.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

ARIA role should be appropriate for the element: 52 elements on the page fail this check, rated minor by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 82 characters, so Google will cut it off around 60: “ETERNITY USA TRANSPORTERS ｜エタニティー｜J.CREW、RRL、RALPH LAUREN、THE NORTH FACE等のセレクトショップ”.

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

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

The homepage links to 94 pages on etnytrico.com and 8 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.

There is no https://www.etnytrico.com/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.

robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to https://www.etnytrico.com/product/25339, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.etnytrico.com/category and https://www.etnytrico.com/group all use the title “メンズ＆レディースのアメリカより直接買付によるラルフ、J.CREW等を中心とした通販＆店舗”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.etnytrico.com/category, https://www.etnytrico.com/group, https://www.etnytrico.com/product-group/124, https://www.etnytrico.com/news, https://www.etnytrico.com/help and https://www.etnytrico.com/page/5 and 4 others use the same meta description. A description written for each page earns more clicks.

https://www.etnytrico.com/category, https://www.etnytrico.com/group, https://www.etnytrico.com/product-group/124, https://www.etnytrico.com/news, https://www.etnytrico.com/help and https://www.etnytrico.com/page/5 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.etnytrico.com/category, https://www.etnytrico.com/group, https://www.etnytrico.com/help, https://www.etnytrico.com/page/5, https://www.etnytrico.com/contact and https://www.etnytrico.com/page/12 and 2 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://www.etnytrico.com/page/7 and https://www.etnytrico.com/page/2 took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.etnytrico.com/' was loaded over HTTPS, but requested an insecure script 'http:/…”.

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

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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 397 words of visible text.

Before a visitor clicks anything, the page loads 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 1 cookie (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.