summitcoffee.com website review

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

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

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

6 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 2.8 MB and 818 ms of main-thread time.

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

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

Squarespace costs a phone 662 ms of main-thread work and 1.3 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.

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 907 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 167 ms. During a long task the page ignores taps.

Desktop scores 84 but mobile only 51. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 files are served with short cache lifetimes, so returning visitors download them again (3 KiB).

Your largest element takes 18.6 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 18.7 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 2.9 MB in 86 requests on a phone: scripts 1.5 MB (51), images 893 KiB (5) and fonts 196 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

1 element hidden from screen readers can still receive keyboard focus.

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 skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

2 visible links have no text or label, so screen readers cannot say where they go.

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

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/62ffa9a70eb3a417405…”.

The homepage links to 71 pages on summitcoffee.com and 4 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://www.summitcoffee.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://www.summitcoffee.com/cafes and https://www.summitcoffee.com/visitus all use the title “Cafes - Summit Coffee”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.summitcoffee.com/summitmugclub has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.summitcoffee.com/cafes and https://www.summitcoffee.com/visitus 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://www.summitcoffee.com/visitus, whose canonical is https://www.summitcoffee.com/cafes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.summitcoffee.com/cafes, https://www.summitcoffee.com/menu, https://www.summitcoffee.com/app, https://www.summitcoffee.com/summitcreamery, https://www.summitcoffee.com/summitmugclub and https://www.summitcoffee.com/shopcoffee and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.summitcoffee.com/summitmugclub, https://www.summitcoffee.com/shopcoffee, https://www.summitcoffee.com/subscribe, https://www.summitcoffee.com/about and https://www.summitcoffee.com/whileyousip have 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 22 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/62ffa9a70eb3a417405e3bba/150/5c5…”.

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.

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

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

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.

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