Website review, no card needed
castleandkey.com website review
Visit site (opens in a new tab)Reviewed 23 October 202626 issues · 81 checks
This review found 26 issues worth fixing on castleandkey.com, 8 of them high impact, across 81 checks. The most urgent: page weight: 6.0 MB in 266 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
86B- #11,726 of 119,939 reviewed websitesbeats 86%
- #7,168 of 67,986 online storesbeats 85%
- #6,948 of 61,962 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 915 ms |
| May 9, 2026 | 928 ms |
| May 16, 2026 | 979 ms |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 983 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 998 ms |
| Oct 3, 2026 | 993 ms |
| Oct 10, 2026 | 995 ms |
| Oct 17, 2026 | 997 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 79 ms |
| May 9, 2026 | 80 ms |
| May 16, 2026 | 84 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 91 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 90 ms |
| Sep 12, 2026 | 90 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 90 ms |
| Oct 3, 2026 | 91 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 88 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
750 ms · 716 KiB12 images could be 716 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 77). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Use efficient cache lifetimes
600 ms · 51 KiB10 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Google Tag Manager and others), adding 793 KiB and 240 ms of main-thread time.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Reduce unused JavaScript
73 KiBAbout 73 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.
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.
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 528 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.9 s
22.9 sThe page becomes fully interactive after 22.9 s. Good is under 3.8 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 79 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 767 ms
767 msReal visitors wait 767 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 7 ms
7 msScripts block the page for only 7 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.0 MB in 266 requests
6.0 MBYour homepage downloads 6.0 MB in 266 requests on a phone: images 4.3 MB (42), other files 812 KiB (110) and scripts 644 KiB (80). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 4.9 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (6.0 MB) 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.
An image on the first screen is lazy-loaded
c_k_hero04_m.webp 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).
1 image far larger than shown
262 KiB1 image is downloaded at several times the size a phone draws it, for example ck-texture-overlay.png at 1,920 px wide, shown at 390 px. Resized copies would save about 262 KiB.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
<svg> elements with an img or image role must have alternative text (2 elements)
<svg> elements with an img or image role must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 127 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
137 internal links, 14 external
The homepage links to 137 pages on castleandkey.com and 14 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Award-winning Kentucky bourbon, gin & vodka from a historic Frankfort distillery. Shop spirits, book tours & plan your …”.
One H1 headline
Your main headline reads: “Our Story in Every Bottle”.
Title: 53 characters
Your title is a healthy 53 characters: “Classic Spirits Reimagined in Kentucky – Castle & Key”.
Canonical URL set
The canonical URL is https://castleandkey.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://castleandkey.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,271 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://castleandkey.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://castleandkey.com/pages/terms and https://castleandkey.com/pages/cookie-policy, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages without a meta description
https://castleandkey.com/collections/all, https://castleandkey.com/collections/featured, https://castleandkey.com/pages/experimental-series and https://castleandkey.com/pages/sparkling-gin-cocktails have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://castleandkey.com/products/traditional-bourbon, whose canonical is https://castleandkey.com/products/small-batch-bourbon. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.
4 checks passed
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 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
68 of 80 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,066 words of copy
The homepage carries about 1,066 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BOOK AN EXPERIENCE” and “Shop”.
21 calls to action
The homepage has 21 calls to action, for example “Start Shopping”, “Apply” and “Shop”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 1 trust badge.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
19 other companies contacted
Loading the homepage contacts 19 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 castleandkey.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on castleandkey.com, including 9 speed issues, 1 SEO issue 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.