rubynz.com website review

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

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

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

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

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

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

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

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

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

Google Tag Manager costs a phone 539 ms of main-thread work and 513 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 385 ms of main-thread work and 1.1 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.

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

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

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

18 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

20 KiB could be saved by minifying JavaScript.

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 33.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HEY RUBETTE ~ ENJOY 15% OFF YOUR FIRST ORDER WITH CODE NEWE…”.

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

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

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

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

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

31 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' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 619 requests on a phone: scripts 3.1 MB (294), images 1.2 MB (86) and other files 936 KiB (181). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

16 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 4 characters: “RUBY”. 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 7 <h1> headlines (“WIN YOUR WISHLIST”, “FEATURED” and “FEATURED”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 492 pages on rubynz.com and 9 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.

/pages/ruby-loyalty has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/toolbox, whose canonical is /blogs/toolbox/toolbox-for-change. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/toolbox has no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://rubynz.com/.

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

5 errors were 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: 4 customer or partner logos. 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 362 words of visible text.

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