riinternational.com website review

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

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

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

5 third-party services load with your homepage (Accessibe Accessibility Overlay, hu-manity.co and wp.com and others), adding 691 KiB and 253 ms of main-thread time.

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

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

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

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.

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Durable crisis infrastructure powered by access, peers, ali…”. Most of its time is element render delay (2.3 s).

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

ARIA progressbar elements do not have accessible names. (4 elements).

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 20 characters: “Recovery Innovations”. 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.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 50 pages on riinternational.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.

There is no https://recoveryinnovations.org/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://recoveryinnovations.org/our-model, https://recoveryinnovations.org/impact, https://recoveryinnovations.org/locations, https://recoveryinnovations.org/leadership, https://recoveryinnovations.org/our-careers and https://recoveryinnovations.org/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

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.

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.