knifeaid.com website review

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

Hotjar costs a phone 2.0 s of main-thread work and 270 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Hotjar, Wunderkind and Klaviyo and others), adding 3.3 MB and 6.2 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.

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

Wunderkind costs a phone 946 ms of main-thread work and 849 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 871 ms of main-thread work and 511 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.

rebuyengine.com costs a phone 756 ms of main-thread work and 691 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 605 ms of main-thread work and 618 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 621 ms. During a long task the page ignores taps.

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

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

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

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

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

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

Your homepage downloads 119.0 MB in 456 requests on a phone: media 113.2 MB (8), scripts 2.8 MB (192) and images 1.5 MB (59). Under 2 MB keeps phones on slow connections fast.

KNIFEAID_243-mobile-BG.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

10 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/Knifeaid_logo.svg")”.

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

The homepage links to 47 pages on knifeaid.com and 5 external pages.

https://knifeaid.com/products/choose-a-mail-in-knife-sharpening-package is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://knifeaid.com/products/knife-sharpening, https://knifeaid.com/products/choose-a-mail-in-knife-sharpening-package and https://knifeaid.com/products/knife-sharpening-6-pack all use the title “Professional Knife Sharpening Services | Knife Aid”. Search engines can't tell which page to show for a search, so each competes with the others.

https://knifeaid.com/pages/jose-andres, https://knifeaid.com/collections/all and https://knifeaid.com/pages/what-we-sharpen have no meta description, so Google writes the search snippet from whatever text it finds.

https://knifeaid.com/products/knife-sharpening, https://knifeaid.com/products/choose-a-mail-in-knife-sharpening-package and https://knifeaid.com/products/knife-sharpening-6-pack use the same meta description. A description written for each page earns more clicks.

https://knifeaid.com/products/knife-sharpening, https://knifeaid.com/pages/jose-andres, https://knifeaid.com/pages/how-knife-sharpening-works, https://knifeaid.com/products/choose-a-mail-in-knife-sharpening-package, https://knifeaid.com/products/knife-sharpening-6-pack and https://knifeaid.com/pages/gift-cards and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://knifeaid.com/pages/how-knife-sharpening-works, https://knifeaid.com/products/e-gift-card, https://knifeaid.com/blogs/knife-mastery, https://knifeaid.com/collections/all, https://knifeaid.com/products/choose-a-mail-in-knife-sharpening-package and https://knifeaid.com/pages/what-we-sharpen and 2 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25076527&Ver=2&mid=2decda7e-531e-4fcb-bf68-08140f28cecd&bo=1&sid=022743d0de7311f1b8fd11dbcc802127&vid=02275f40de7311f18ae0e54e15687c6b&vids=1&msclkid=N&pi=918639831&lg.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 764 words of visible text.

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