seisukeknife.com website review

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

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

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

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

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

8 third-party services load with your homepage (Amazon Web Services, YouTube and Shopify and others), adding 3.6 MB and 2.7 s of main-thread time.

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

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

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

YouTube costs a phone 505 ms of main-thread work and 992 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.

Amazon Web Services costs a phone 560 ms of main-thread work and 28 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.

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

Google Tag Manager costs a phone 376 ms of main-thread work and 487 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 407 ms. During a long task the page ignores taps.

route.com costs a phone 289 ms of main-thread work and 542 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.

21 KiB could be saved by minifying JavaScript.

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

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

9 KiB could be saved by minifying CSS.

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.

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.

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

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 7.6 MB in 408 requests on a phone: scripts 4.0 MB (134), images 2.0 MB (46) and other files 1.0 MB (174). Under 2 MB keeps phones on slow connections fast.

5 images (862 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.

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

5 images are downloaded at several times the size a phone draws them, for example c_pick-up02.webp at 1,600 px wide, shown at 390 px. Resized copies would save about 222 KiB.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

The homepage links to 325 pages on seisukeknife.com and 8 external pages.

https://seisukeknife.com/pages/shipping-delivery, https://seisukeknife.com/collections/kitchen-knives-1, https://seisukeknife.com/collections/gyuto-chefs-knife, https://seisukeknife.com/collections/santoku-all-purpose-knives, https://seisukeknife.com/collections/petty-utility and https://seisukeknife.com/collections/nakiri-vegetable and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://seisukeknife.com/collections/bunka-knife has 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 121 found) and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset')”.

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

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 1,242 words of visible text.

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