onward.co.jp website review

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

14 images could be 766 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

Your mobile performance score is 53 (desktop: 61). Pages that score under 90 lose visitors before the first paint.

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

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

5 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Analytics and others), adding 499 KiB and 390 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

6 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “当社ウェブサイトのメンテナンスのため、ウェブサイトの表示やサービスに不具合が生じる可能性があります。 お客様にはご不便…”.

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 3.0 MB in 78 requests on a phone: images 2.3 MB (39), scripts 475 KiB (11) and fonts 76 KiB (5). Under 2 MB keeps phones on slow connections fast.

19 images (1.4 MB) 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.

6 images are downloaded at several times the size a phone draws them, for example 3f3757ec278a8f62f67886ac0127c86a50ae71e5.jpg at 1,228 px wide, shown at 89 px. Resized copies would save about 436 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 101.0 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: 1 element on the page fails this check, rated critical by axe-core.

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

All page content should be contained by landmarks: 14 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.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.onward.co.jp/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at onward.co.jp/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 35 pages on onward.co.jp and 17 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.onward.co.jp/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://www.onward.co.jp/members is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.onward.co.jp/company, https://www.onward.co.jp/brandlist, https://www.onward.co.jp/news, https://www.onward.co.jp/shop, https://www.onward.co.jp/contact and https://www.onward.co.jp/ir and 7 others use the same meta description. A description written for each page earns more clicks.

https://www.onward.co.jp/company, https://www.onward.co.jp/brandlist, https://www.onward.co.jp/recruit, https://www.onward.co.jp/contact, https://www.onward.co.jp/ir and https://www.onward.co.jp/news/2026/07/creators.html and 6 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 31 found) and read each the way a search engine does.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 ()”.

10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

There is no form on the homepage, so every lead has to click through to another page first.

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