Website review, no card needed
bakeryhill.com website review
Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 76 checks
This review found 26 issues worth fixing on bakeryhill.com, 9 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
85B- #14,934 of 109,103 reviewed websitesbeats 82%
- #9,503 of 61,794 online storesbeats 79%
- #9,246 of 56,374 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.1 s · 444 KiBAbout 444 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and cloudfront.net and others), adding 15.0 MB and 150 ms of main-thread time.
Shopify adds 31 ms
31 msShopify costs a phone 31 ms of main-thread work and 14.8 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.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Use efficient cache lifetimes
250 ms · 83 KiB6 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).
Reduce unused CSS
150 ms · 42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 23 KiB3 images could be 23 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 96 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 547 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.079
0.079The layout barely moves while loading (CLS 0.079, good is under 0.1).
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.1 MB in 220 requests
17.1 MBYour homepage downloads 17.1 MB in 220 requests on a phone: media 14.5 MB (2), other files 997 KiB (160) and scripts 816 KiB (37). Under 2 MB keeps phones on slow connections fast.
About 4.8 g of CO₂ per visit
4.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.84 g of CO₂e: 581.1 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (2 elements)
Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
41 internal links, 3 external
The homepage links to 41 pages on bakeryhill.com and 3 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Bakery Hill Distillery, Melbourne, Australia. Premium Single Malt Whisky Distillery. Shop Online for Whisky, or visit u…”.
Title: 62 characters
Your title is a healthy 62 characters: “Australian Premium Single Malt Whisky | Bakery Hill Distillery”.
Canonical URL set
The canonical URL is https://bakeryhill.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://bakeryhill.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 (304 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bakeryhill.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://bakeryhill.com/collections/all, https://bakeryhill.com/pages/whisky and https://bakeryhill.com/pages/functions have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://bakeryhill.com/products/classic-malt-cask-strength-25th-edition and https://bakeryhill.com/products/classic-malt-25th-edition use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://bakeryhill.com/collections/all, https://bakeryhill.com/pages/sly-grog-shop-1, https://bakeryhill.com/pages/distillery, https://bakeryhill.com/pages/private-barrel-program, https://bakeryhill.com/pages/whisky and https://bakeryhill.com/products/classic-malt-cask-strength-25th-edition and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
5 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.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
24 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 332 words of copy
The homepage carries about 332 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” and “Contact”.
4 calls to action
The homepage has 4 calls to action, for example “Shop”, “Contact” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
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 bakeryhill.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Minmaxify Order Limits · Forms · cinaberis.com · cloudfront.net
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
- Analytics
- Google Analytics
- Hosting
- 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 bakeryhill.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.