rubicon.tech website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and roseperl.com and others), adding 599 KiB and 122 ms of main-thread time.

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

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

1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

39 KiB could be saved by minifying JavaScript.

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

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.

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

Real visitors wait 250 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 154 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Visually, the page fills in at 4.1 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.

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

Your homepage downloads 2.1 MB in 241 requests on a phone: other files 882 KiB (117), scripts 810 KiB (73) and images 155 KiB (11). Under 2 MB keeps phones on slow connections fast.

Homepage-hero--apex-m-3a_2x_ede97827-5a24-4d0c-b08c-5f29a276 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.59 g of CO₂e: 70.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

3 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 181 pages on rubicon.tech and 34 external pages.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.roseperl.com/storelocator-prod/assets/css/findonline-1771903877.css' from orig…”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

rubicon.tech's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

DMARC is set to p=none, so mail pretending to be rubicon.tech is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 10 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.