newwestknifeworks.com website review

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

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

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 5.3 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Shopify and others), adding 2.2 MB and 1.6 s of main-thread time.

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

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

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

Hotjar costs a phone 313 ms of main-thread work and 65 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 234 ms of main-thread work and 496 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.

Klaviyo costs a phone 131 ms of main-thread work and 330 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.

Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

208 KiB could be saved by minifying JavaScript.

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

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

8 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

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

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' tap response (inp) went from 146 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.5 MB in 411 requests on a phone: media 19.4 MB (3), scripts 2.8 MB (142) and other files 1.1 MB (174). Under 2 MB keeps phones on slow connections fast.

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

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Your title is 70 characters, so Google will cut it off around 60: “Homepage New West KnifeWorks | Premium-Quality Knives & Custom Cutlery”.

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

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 105 pages on newwestknifeworks.com and 0 external pages.

There is no https://www.newwestknifeworks.com/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.newwestknifeworks.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://www.newwestknifeworks.com/collections/all, https://www.newwestknifeworks.com/customer_authentication/redirect, https://www.newwestknifeworks.com/policies/shipping-policy and https://www.newwestknifeworks.com/pages/early-bird-special have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.newwestknifeworks.com/collections/all, https://www.newwestknifeworks.com/customer_authentication/redirect and https://www.newwestknifeworks.com/pages/early-bird-special have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 carries about 757 words of visible text.

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