rosslyn.direct website review

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

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

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

About 587 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

110 KiB could be saved by minifying CSS.

8 third-party services load with your homepage (Shopify, loox.io and octaneai.com and others), adding 1.1 MB and 363 ms of main-thread time.

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

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

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

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

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

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Real visitors wait 480 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 2.8 MB in 231 requests on a phone: scripts 1.2 MB (79), other files 881 KiB (126) and images 360 KiB (12). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Rosslyn_Product_Photo_Coming_Soon.png at 1,200 px wide, shown at 257 px. Resized copies would save about 129 KiB.

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

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

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 95 pages on rosslyn.direct and 12 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.

https://rosslyn.direct/collections/shop-all, https://rosslyn.direct/collections/thca-live-resin, https://rosslyn.direct/collections/distillate-510-carts, https://rosslyn.direct/collections/pre-rolls-hash-holes, https://rosslyn.direct/blogs/know-your-flow and https://rosslyn.direct/pages/contact and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://rosslyn.direct/collections/shop-all, https://rosslyn.direct/collections/thca-live-rosin-2, https://rosslyn.direct/collections/thca-live-resin, https://rosslyn.direct/collections/thca-flower, https://rosslyn.direct/collections/distillate-510-carts and https://rosslyn.direct/collections/pre-rolls-hash-holes and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 33 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.

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

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