rubicotech.com website review

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

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

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

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

Google Tag Manager costs a phone 773 ms of main-thread work and 760 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.

Google CDN costs a phone 683 ms of main-thread work and 741 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.

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

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

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

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

Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You built it, now let's make it unbreakable Whether you are…”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 116 ms to 345 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 2.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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.

Your homepage downloads 2.7 MB in 106 requests on a phone: scripts 1.8 MB (36), other files 359 KiB (14) and images 221 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example variation-3-editorial.png at 2,560 px wide, shown at 390 px. Resized copies would save about 40 KiB.

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

6 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: 1 element on the page fails this check, rated moderate by axe-core.

28 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 homepage links to 47 pages on rubicotech.com and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://rubicotech.com/blog and https://rubicotech.com/get-started have no meta description, so Google writes the search snippet from whatever text it finds.

https://rubicotech.com/get-started and https://rubicotech.com/technical-expert-consultation have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

Chrome logged issues while loading the page (“Content security policy”).

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 1,333 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies (measured from a US location before any click).

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.