pinotspalette.com website review

51 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

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

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

4 images could be 377 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.

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

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

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

10 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 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.

Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PAINT. DRINK. HAVE FUN.® Gather your favorite people for se…”.

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

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

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.6 MB in 93 requests on a phone: scripts 1.5 MB (38), images 922 KiB (17) and fonts 113 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

The robots meta tag says “noindex”: Google is told not to list this page at all.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Google's crawler is blocked from indexing this page.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 48 pages on pinotspalette.com and 11 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.

There is no https://pinotspalette.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://pinotspalette.com/locations, https://pinotspalette.com/set-culture-info/en-us, https://pinotspalette.com/set-culture-info/en-ca, https://pinotspalette.com/pinot-perks/faqs, https://pinotspalette.com/pinot-perks/terms-of-use and https://pinotspalette.com/pinot-perks/privacy-policy and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/, https://pinotspalette.com/set-culture-info/en-us and https://pinotspalette.com/set-culture-info/en-ca all use the title “Paint & Sip, Wine & Painting Parties - Pinot's Palette”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pinotspalette.com/set-culture-info/en-us and https://pinotspalette.com/set-culture-info/en-ca use the same meta description. A description written for each page earns more clicks.

https://pinotspalette.com/set-culture-info/en-us, https://pinotspalette.com/set-culture-info/en-ca, https://pinotspalette.com/pinot-perks/terms-of-use and https://pinotspalette.com/pinot-perks/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5710182&tm=gtm002&Ver=2&mid=156a27bc-751e-493a-87d5-52aa420d723a&bo=1&sid=c8562440d3bb11f19ff989eb00fbfc49&vid=c8563200d3bb11f1a0baedab21979a3a&vids=1&msclkid=N&pi=918.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://content.pinotspalette.com/css/pinot/pinot.min.css?v=20210624' from origin 'https:/…”.

Requests the geolocation permission on page load.

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

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 form on the homepage, so every lead has to click through to another page first.

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 625 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies (measured from a US location before any click).

Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.