wedigcoffee.com website review

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

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

8 third-party services load with your homepage (zbcdn.net, zotabox.com and Shopify and others), adding 1.1 MB and 545 ms of main-thread time.

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

zotabox.com costs a phone 254 ms of main-thread work and 770 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.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

zbcdn.net costs a phone 276 ms of main-thread work and 283 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.

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

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

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

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

5 images could be 110 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

26 KiB could be saved by minifying JavaScript.

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

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 12.1 s. Good is under 3.8 s.

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

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

The layout shifts by 0.149 while loading, so content jumps under the reader's thumb. Good is under 0.1.

13 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.4 MB in 145 requests on a phone: scripts 961 KiB (26), other files 759 KiB (91) and images 392 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

1 dropdown has no label.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

1 button has no accessible name, so screen readers announce just “button”.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate 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.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Your title is only 13 characters: “We Dig Coffee”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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.

Your <h1> is empty.

The homepage links to 48 pages on wedigcoffee.com and 2 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://www.wedigcoffee.com/collections/best-sellers/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt and https://www.wedigcoffee.com/collections/new-in/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt all use the title “I Like Coffee and Maybe 3 People - TShort-Sleeve Unisex T-Shirt – We …”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wedigcoffee.com/collections/all-products, https://www.wedigcoffee.com/collections/best-sellers and https://www.wedigcoffee.com/collections/new-in have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wedigcoffee.com/collections/best-sellers/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt and https://www.wedigcoffee.com/collections/new-in/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt use the same meta description. A description written for each page earns more clicks.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.wedigcoffee.com/collections/best-sellers/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt, whose canonical is https://www.wedigcoffee.com/products/i-like-coffee-and-maybe-3-people-tshort-sleeve-unisex-t-shirt. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wedigcoffee.com/pages/contact-us has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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