anthonysespresso.com website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Yotpo and Shopify and others), adding 2.1 MB and 1.2 s of main-thread time.

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

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

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

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

Yotpo costs a phone 324 ms of main-thread work and 574 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.

Shopify costs a phone 225 ms of main-thread work and 447 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.

18 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 19 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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 153 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-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 382 requests on a phone: scripts 3.1 MB (143), other files 894 KiB (141) and images 572 KiB (58). Under 2 MB keeps phones on slow connections fast.

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

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

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

2 elements hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (BreadcrumbList, CreativeWorkSeries, LocalBusiness and Organization) but with 1 problem, for example “ld+json block 4 is not valid JSON (Unexpected non-whitespace character after JSON at position 2)”.

The homepage links to 308 pages on anthonysespresso.com and 8 external pages.

https://anthonysespresso.com/apps/subscriptions, https://anthonysespresso.com/collections/delonghi/De'Longhi and https://anthonysespresso.com/collections/philips/Philips are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://anthonysespresso.com/collections/philips/Philips and https://anthonysespresso.com/collections/miele all use the title “Buy Online | Anthony’s Espresso”. Search engines can't tell which page to show for a search, so each competes with the others.

https://anthonysespresso.com/apps/subscriptions, https://anthonysespresso.com/collections/smeg and https://anthonysespresso.com/collections/quick-mill-rocket-and-ceado-save-the-tax-and-more have no meta description, so Google writes the search snippet from whatever text it finds.

https://anthonysespresso.com/collections/philips/Philips and https://anthonysespresso.com/collections/miele use the same meta description. A description written for each page earns more clicks.

https://anthonysespresso.com/collections/sale, https://anthonysespresso.com/apps/subscriptions, https://anthonysespresso.com/collections/delonghi/De'Longhi, https://anthonysespresso.com/collections/philips/Philips, https://anthonysespresso.com/collections/jura and https://anthonysespresso.com/collections/bezzera have no <h1> headline, so visitors and search engines get no clear main topic.

https://anthonysespresso.com/collections/philips/Philips, https://anthonysespresso.com/collections/smeg, https://anthonysespresso.com/pages/shop-breville and https://anthonysespresso.com/collections/gaggia took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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.

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.

The homepage carries about 1,648 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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