ottocast.jp website review

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

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google CDN, automizely.com and loloyal.com and others), adding 2.3 MB and 2.0 s of main-thread time.

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

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

Google CDN costs a phone 546 ms of main-thread work and 742 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.

automizely.com costs a phone 540 ms of main-thread work and 514 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.

loloyal.com costs a phone 350 ms of main-thread work and 393 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.

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

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

91 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

About 33 KiB of CSS is downloaded but never applied on this page.

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 could be saved by minifying CSS.

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

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

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

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

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

2 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-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.3 MB in 395 requests on a phone: fonts 4.3 MB (16), images 4.2 MB (55) and scripts 2.2 MB (118). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example ottocast-mini-sale_2.jpg at 3,000 px wide, shown at 354 px. Resized copies would save about 961 KiB.

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

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

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

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

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

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

45 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.

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

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

Your <h1> is empty.

The homepage links to 155 pages on ottocast.jp and 12 external pages.

https://ottocast.jp/pages/mini-3-crown, https://ottocast.jp/collections/syouhinichiran, https://ottocast.jp/pages/cloud-sim and https://ottocast.jp/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ottocast.jp/products/%E8%BF%94%E5%93%81%E9%80%81%E6%96%99%E4%BF%9D%E9%99%BA, whose canonical is https://ottocast.jp/products/%e8%bf%94%e5%93%81%e9%80%81%e6%96%99%e4%bf%9d%e9%99%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ottocast.jp/pages/mini-3-crown, https://ottocast.jp/collections/syouhinichiran, https://ottocast.jp/pages/cloud-sim, https://ottocast.jp/pages/about-us, https://ottocast.jp/pages/car and https://ottocast.jp/pages/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://ottocast.jp/blogs/news, https://ottocast.jp/pages/about-us, https://ottocast.jp/pages/contact and https://ottocast.jp/collections/ottocast-srceen 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 65 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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