sigels.com website review

About 573 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

8 third-party services load with your homepage (cityhive.net, Facebook and Google Tag Manager and others), adding 1.9 MB and 1.4 s of main-thread time.

Your mobile performance score is 55 (desktop: 51). Pages that score under 90 lose visitors before the first paint.

cityhive.net costs a phone 438 ms of main-thread work and 1.1 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.

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

Facebook costs a phone 365 ms of main-thread work and 238 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.

Google Tag Manager costs a phone 331 ms of main-thread work and 372 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.

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

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

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

2 images could be 26 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.

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

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

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.

Real visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Image placeholder”.

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

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

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

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

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

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

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

Your homepage downloads 2.3 MB in 78 requests on a phone: scripts 1.4 MB (26), images 573 KiB (17) and HTML 152 KiB (2). Under 2 MB keeps phones on slow connections fast.

6ad1084f5170fe0f93fdfdca.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 0.65 g of CO₂e: 78.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 image has no alt text, which hurts accessibility and image search.

4 tap targets are too small or too close together to hit reliably with a finger.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 12 characters: “Twin Liquors”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“This Week's Deals” and “Twin Sourced Wine & Spirits”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://twinliquors.com/googlesitemapxml.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 247 pages on sigels.com and 16 external pages.

https://twinliquors.com/pages/shop-wine, https://twinliquors.com/shop/product-groups/non-alcoholic-1, https://twinliquors.com/product-groups/90-points-wine-advocate, https://twinliquors.com/product-groups/90-points-wine-spectator, https://twinliquors.com/product-groups/90-points-wine-enthusiast and https://twinliquors.com/product-groups/90-points-vinous and 8 others use the same meta description. A description written for each page earns more clicks.

https://twinliquors.com/pages/shop-wine, https://twinliquors.com/shop/product-groups/non-alcoholic-1, https://twinliquors.com/product-groups/90-points-wine-advocate, https://twinliquors.com/product-groups/90-points-wine-spectator, https://twinliquors.com/product-groups/90-points-wine-enthusiast and https://twinliquors.com/product-groups/90-points-vinous and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 212 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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