urasta.jp website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and growave.io and others), adding 992 KiB and 737 ms of main-thread time.

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

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

Google Tag Manager costs a phone 274 ms of main-thread work and 322 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.

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

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

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

Polyfills for old browsers add 6 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.

Your largest element takes 60.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “<strong>Music Unites Cultures<https://urasta.jp/strong>”.

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

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

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

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 13.1 MB in 161 requests on a phone: fonts 10.2 MB (11), images 1.3 MB (27) and scripts 1,007 KiB (88). Under 2 MB keeps phones on slow connections fast.

brian-lundquist-QyZkLMiwn2Q-unsplash.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).

1 image is downloaded at several times the size a phone draws it, for example donbruh_3d71bf9e-8051-41a2-aff1-6cfd83a52c9c.jpg at 1,100 px wide, shown at 84 px. Resized copies would save about 66 KiB.

1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

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.

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

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

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

There are 3 <h1> headlines (“”, “” and “Brand Culture Produce”). One clear main headline is easier for people and search engines.

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

The homepage links to 267 pages on urasta.jp and 14 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.

https://urasta.jp/apps/my/courses/list has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://urasta.jp/pages/%E3%83%A6%E3%83%A9%E3%82%B9%E3%82%BF%E3%81%A8%E3%81%AF, whose canonical is https://urasta.jp/pages/%e3%83%a6%e3%83%a9%e3%82%b9%e3%82%bf%e3%81%a8%e3%81%af. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://urasta.jp/apps/my/courses/list has no <h1> headline, so visitors and search engines get no clear main topic.

https://urasta.jp/collections, https://urasta.jp/pages/%E3%83%A6%E3%83%A9%E3%82%B9%E3%82%BF%E3%81%A8%E3%81%AF, https://urasta.jp/pages/%E3%83%AD%E3%82%B0%E3%82%A4%E3%83%B3%E6%96%B9%E6%B3%95%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6, https://urasta.jp/pages/contact, https://urasta.jp/apps/my/courses/list and https://urasta.jp/products/ca-free1 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 41 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: the server responded with a status of 404 ()”.

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.

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

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