Website review, no card needed
districtcutlery.com website review
Visit site (opens in a new tab)Reviewed 8 November 202617 issues · 74 checks
This review found 17 issues worth fixing on districtcutlery.com, 6 of them high impact, across 74 checks. The most urgent: page weight: 8.3 MB in 237 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #28,367 of 124,954 reviewed websitesbeats 72%
- #18,506 of 70,076 online storesbeats 67%
- #17,914 of 63,686 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 964 ms |
| Jun 13, 2026 | 980 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 993 ms |
| Aug 8, 2026 | 978 ms |
| Aug 15, 2026 | 961 ms |
| Aug 22, 2026 | 968 ms |
| Aug 29, 2026 | 978 ms |
| Sep 5, 2026 | 986 ms |
| Sep 12, 2026 | 980 ms |
| Sep 19, 2026 | 983 ms |
| Sep 26, 2026 | 965 ms |
| Oct 3, 2026 | 968 ms |
| Oct 10, 2026 | 951 ms |
| Oct 17, 2026 | 968 ms |
| Oct 24, 2026 | 957 ms |
| Oct 31, 2026 | 880 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 87 ms |
| May 23, 2026 | 82 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 76 ms |
| Aug 22, 2026 | 75 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 75 ms |
| Oct 24, 2026 | 76 ms |
| Oct 31, 2026 | 70 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
3,437 HTML elements
The page has 3,437 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Shopify adds 97 ms
97 msShopify costs a phone 97 ms of main-thread work and 555 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.
Improve image delivery
150 ms · 144 KiB11 images could be 144 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.
Render-blocking requests
200 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, shop.app and Judge.me and others), adding 584 KiB and 97 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 567 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 38.3 s
38.3 sYour largest element takes 38.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 38.3 s
38.3 sThe page becomes fully interactive after 38.3 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 667 ms
667 msReal visitors wait 667 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 87 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 23 ms
23 msScripts block the page for only 23 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.3 MB in 237 requests
8.3 MBYour homepage downloads 8.3 MB in 237 requests on a phone: fonts 6.1 MB (5), other files 866 KiB (81) and images 783 KiB (36). Under 2 MB keeps phones on slow connections fast.
About 2.3 g of CO₂ per visit
2.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 281.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
35 text elements with low contrast
35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “District Cutlery”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
264 internal links, 10 external
The homepage links to 264 pages on districtcutlery.com and 10 external pages.
5 checks passed
Meta description: 75 characters
Your meta description is 75 characters: “Purveyors of hand-crafted knives and experts at knife sharpening and repair”.
Canonical URL set
The canonical URL is https://districtcutlery.com/.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://districtcutlery.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,426 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://districtcutlery.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://districtcutlery.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://districtcutlery.com/collections/kitchen-shears and https://districtcutlery.com/collections/edc-knives took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 123 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
43 of 48 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,049 words of copy
The homepage carries about 1,049 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All Knives”.
5 calls to action
The homepage has 5 calls to action, for example “Shop By Maker”, “Contact” and “Shop All Knives”.
24 short forms
24 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 123 testimonial or review blocks, a star rating and 5 trust badges.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
No consent tool detected
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.
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at districtcutlery.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sami Wholesale · Judge Me Reviews
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on districtcutlery.com, including 8 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.