anfora.com website review

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

About 281 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

7 images could be 303 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (autoketing.org, Shopify and Clarity and others), adding 1.0 MB and 508 ms of main-thread time.

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

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

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

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

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

12 KiB could be saved by minifying CSS.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slideshow Image 1”.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 65 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.5 MB in 290 requests on a phone: scripts 1.1 MB (61), images 1,002 KiB (22) and other files 785 KiB (104). Under 2 MB keeps phones on slow connections fast.

Motiva_Plana.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 further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

Your meta description is only 38 characters: “Mexico's best professional dinnerware.”. 70 to 160 characters is enough to sell the click.

Structured data found (Organization and WebSite) but with 6 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 76 pages on anfora.com and 4 external pages.

https://anforausa.com/es/pages/about-anfora, https://anforausa.com/pages/collections, https://anforausa.com/pages/plana-caribe-1, https://anforausa.com/pages/plana-bruma-titanio, https://anforausa.com/pages/motiva-2-0 and https://anforausa.com/pages/tulum-eco-ceramics and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://anforausa.com/es/pages/about-anfora, https://anforausa.com/pages/collections, https://anforausa.com/pages/plana-caribe-1, https://anforausa.com/pages/plana-bruma-titanio, https://anforausa.com/pages/motiva-2-0 and https://anforausa.com/pages/tulum-eco-ceramics and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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