twistedlemon.ca website review

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

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

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

About 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 830 ms faster on a phone.

8 third-party services load with your homepage (Facebook, Shopify and Google Tag Manager and others), adding 913 KiB and 516 ms of main-thread time.

5 images could be 402 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.

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

Shopify costs a phone 130 ms of main-thread work and 429 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.

7 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.

About 24 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.

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

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

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.

3 KiB could be saved by minifying JavaScript.

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.

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

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

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 80 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Your homepage downloads 3.0 MB in 357 requests on a phone: scripts 1.0 MB (184), images 970 KiB (26) and other files 751 KiB (107). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 108 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 83 characters, so Google will cut it off around 60: “Twisted Lemon Restaurant & Boutique Inn – Twisted Lemon - Restaurant & Boutique Inn”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

3 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 145 pages on twistedlemon.ca and 16 external pages.

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.

https://twistedlemon.ca/pages/contact, https://twistedlemon.ca/collections/dine-stay, https://twistedlemon.ca/collections/cocktail-trees-drinkable-ornaments, https://twistedlemon.ca/collections/games and https://twistedlemon.ca/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://twistedlemon.ca/collections/clarity-cocktails and https://twistedlemon.ca/collections/clarity-cocktails/Single-Bottle use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://twistedlemon.ca/collections/clarity-cocktails/Single-Bottle, whose canonical is https://twistedlemon.ca/collections/clarity-cocktails/single-bottle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://twistedlemon.ca/pages/contact, https://twistedlemon.ca/collections/dine-stay, https://twistedlemon.ca/collections/clarity-cocktails, https://twistedlemon.ca/collections/clarity-cocktails/Single-Bottle, https://twistedlemon.ca/collections/cocktail-trees-drinkable-ornaments and https://twistedlemon.ca/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot assign to read only property 'isDropdown' of object '#<PredictiveSearch>'”.

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.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,047 words of visible text.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 12 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.