alogic.jp website review

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

8 third-party services load with your homepage (Shopify, ZenDesk and reamaze.com and others), adding 1.2 MB and 1.3 s of main-thread time.

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

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

About 629 KiB of JavaScript is downloaded but never used on this page.

Shopify costs a phone 539 ms of main-thread work and 607 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.

ZenDesk costs a phone 337 ms of main-thread work and 386 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.

reamaze.com costs a phone 309 ms of main-thread work and 216 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.

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

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

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

4 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 148 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-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 185 requests on a phone: scripts 1.2 MB (57), other files 762 KiB (63) and images 628 KiB (41). Under 2 MB keeps phones on slow connections fast.

4 images (227 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.

1 image further down the page (34 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 0.80 g of CO₂e: 96.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

20 images have no alt text, which hurts accessibility and image search.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 183 pages on alogic.jp and 21 external pages.

https://alogic.jp/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://alogic.jp/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://alogic.jp/customer_authentication/redirect and https://alogic.jp/collections/%E3%82%A2%E3%83%BC%E3%83%A0%E3%82%92%E7%9B%A3%E8%A6%96%E3%81%97%E3%81%BE%E3%81%99 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://alogic.jp/collections/%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC, whose canonical is https://alogic.jp/collections/%e3%83%a2%e3%83%8b%e3%82%bf%e3%83%bc. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://alogic.jp/customer_authentication/redirect and https://alogic.jp/collections/%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC have no <h1> headline, so visitors and search engines get no clear main topic.

https://alogic.jp/collections/%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC, https://alogic.jp/collections/aspekt%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC, https://alogic.jp/collections/%E3%82%A6%E3%83%AB%E3%83%88%E3%83%A9%E3%82%A6%E3%82%A3%E3%83%89%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC, https://alogic.jp/collections/%E3%83%90%E3%83%B3%E3%83%89%E3%83%AB%E3%82%92%E7%9B%A3%E8%A6%96%E3%81%97%E3%81%BE%E3%81%99, https://alogic.jp/collections/27-%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC%E3%83%90%E3%83%B3%E3%83%89%E3%83%AB and https://alogic.jp/collections/32-%E3%83%A2%E3%83%8B%E3%82%BF%E3%83%BC%E3%83%90%E3%83%B3%E3%83%89%E3%83%AB and 5 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.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The page uses urgency cues (a countdown or limited-time wording).

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