zwickspretzels.com website review

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

hcaptcha.com costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 5.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

4 third-party services load with your homepage (hcaptcha.com, Shopify and jQuery CDN and others), adding 2.4 MB and 1.4 s of main-thread time.

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

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

Shopify costs a phone 258 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.

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

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

About 12 KiB of CSS is downloaded but never applied on this page.

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.

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

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zwicksticks & Zwickbricks”. Most of its time is resource load delay (5.0 s).

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

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 4.5 MB in 359 requests on a phone: scripts 2.0 MB (172), images 1.0 MB (28) and other files 841 KiB (127). Under 2 MB keeps phones on slow connections fast.

pretzel-1497578_1280.jpg 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 is downloaded at several times the size a phone draws it, for example 2024_Zwick_Logo.png at 6,344 px wide, shown at 135 px. Resized copies would save about 127 KiB.

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 16 characters: “Zwick's Pretzels”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 314 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.

Your <h1> is empty.

The homepage links to 81 pages on zwickspretzels.com and 6 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://zwickspretzels.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://zwickspretzels.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://zwickspretzels.com/customer_authentication/redirect, https://zwickspretzels.com/collections/zwicksticks, https://zwickspretzels.com/collections/soft-pretzels, https://zwickspretzels.com/pages/pretzel-carts, https://zwickspretzels.com/pages/wholesale and https://zwickspretzels.com/pages/fundraising and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://zwickspretzels.com/customer_authentication/redirect, https://zwickspretzels.com/collections/zwicksticks, https://zwickspretzels.com/collections/soft-pretzels, https://zwickspretzels.com/pages/pretzel-carts, https://zwickspretzels.com/pages/wholesale and https://zwickspretzels.com/pages/fundraising and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

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 or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads 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 10 cookies, 1 of them by other companies (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.