rifoundation.org website review

33 files are served with short cache lifetimes, so returning visitors download them again (12.1 MB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.5 s.

About 504 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

408 KiB could be saved by minifying CSS.

5 images could be 10.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 third-party service load with your homepage (Azure Web Services), adding 11.3 MB and 0 ms of main-thread time.

Azure Web Services costs a phone 0 ms of main-thread work and 11.3 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.

Your mobile performance score is 61 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

About 35 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Desktop scores 87 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Only together can we build the future we all hope for.”.

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

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

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

11 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-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.1 MB in 36 requests on a phone: images 11.3 MB (23), stylesheets 521 KiB (1) and fonts 115 KiB (2). Under 2 MB keeps phones on slow connections fast.

2026-07-31_Website_Homepage_CLF-1.png weighs 9.8 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 2026-07-31_Website_Homepage_CLF-1.png at 1,600 px wide, shown at 351 px. Resized copies would save about 5.5 MB.

1 image (9.8 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

4 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.

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

There are 3 <h1> headlines (“Site Navigation”, “Site Search” and “Only together can we build the future we all hope…”). One clear main headline is easier for people and search engines.

The homepage links to 64 pages on rifoundation.org and 9 external pages.

There is no https://rifoundation.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.

/ and https://rifoundation.org/es all use the title “RI Foundation | Rhode Island Foundation”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rifoundation.org/about/who-we-are, https://rifoundation.org/about/what-we-do and https://rifoundation.org/about/our-history use the same meta description. A description written for each page earns more clicks.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

Opening the homepage sets 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.