royalcupcoffee.com website review

56 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and ZenDesk and others), adding 899 KiB and 820 ms of main-thread time.

51 KiB could be saved by minifying CSS.

49 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 282 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.

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

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

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

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.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “No matter what you drink, drink Royal Cup. Your favorite co…”.

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

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

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

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

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

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

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

Your homepage downloads 13.4 MB in 72 requests on a phone: media 11.8 MB (1), scripts 949 KiB (20) and images 407 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example sca-logo.png at 1,104 px wide, shown at 246 px. Resized copies would save about 53 KiB.

1 image (96 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (96 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 3.80 g of CO₂e: 455.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 39 elements on the page fail 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 23 characters: “Home | Royal Cup 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.

There are 2 <h1> headlines (“No matter what you drink, drink Royal Cup.” and “Hear Our Story”). One clear main headline is easier for people and search engines.

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

The homepage links to 70 pages on royalcupcoffee.com and 16 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.royalcupcoffee.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.royalcupcoffee.com/careers, https://www.royalcupcoffee.com/locations and https://www.royalcupcoffee.com/brands/prideland have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.royalcupcoffee.com/brands/prideland took over 3 s to send its HTML from our server.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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