rositascoffee.com website review

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

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

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

8 third-party services load with your homepage (Shopify, smile.io and Google CDN and others), adding 522 KiB and 269 ms of main-thread time.

About 166 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rositas Coffee Roasters”.

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

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.

reaching_5f3f4b24-a467-4f91-a007-8d345b543089.png 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).

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

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

There are 2 <h1> headlines (“” and “Go ahead, reach for it”). One clear main headline is easier for people and search engines.

Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 82 pages on rositascoffee.com and 5 external pages.

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

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

https://rositascoffee.com/customer_authentication/redirect, https://rositascoffee.com/policies/shipping-policy and https://rositascoffee.com/collections/best-for-espresso have no meta description, so Google writes the search snippet from whatever text it finds.

https://rositascoffee.com/customer_authentication/redirect, https://rositascoffee.com/pages/rositas-reserve, https://rositascoffee.com/pages/about-us, https://rositascoffee.com/pages/brew-guide, https://rositascoffee.com/pages/faqs and https://rositascoffee.com/pages/coffee-archive have no <h1> headline, so visitors and search engines get no clear main topic.

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

8 of 24 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: the server responded with a status of 404 ()”.

Social proof on the homepage: 3 trust badges. 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 272 words of visible text.

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