rinnai.us website review

8 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, fouanalytics.com and Facebook and others), adding 1.2 MB and 1.1 s of main-thread time.

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

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

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

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

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

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need.

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

3 KiB could be saved by minifying JavaScript.

Desktop scores 91 but mobile only 45. 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Parent and child in a kitchen”.

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

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

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

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

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

9 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-24, real Chrome visitors' tap response (inp) went from 92 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

home-hero_banner.png weighs 725 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.0 MB in 83 requests on a phone: images 1.6 MB (22), scripts 1.2 MB (29) and stylesheets 65 KiB (5). Under 2 MB keeps phones on slow connections fast.

8 images (1.6 MB) are 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.

6 images further down the page (777 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example home-hero_banner.png at 1,336 px wide, shown at 350 px. Resized copies would save about 277 KiB.

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

2 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 17 characters: “Homepage | Rinnai”. 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.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 96 pages on rinnai.us and 49 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://www.rinnai.us/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.

Your homepage links to https://www.rinnai.us/folds-of-honor, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.rinnai.us/find-pro, https://www.rinnai.us/universal/message-from-the-president, https://www.rinnai.us/universal/quality, https://www.rinnai.us/blog, https://www.rinnai.us/residential/locations and https://www.rinnai.us/residential/electric-rehp-models have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rinnai.us/residential, https://www.rinnai.us/commercial and https://www.rinnai.us/professional use the same meta description. A description written for each page earns more clicks.

https://www.rinnai.us/professional, https://www.rinnai.us/find-pro, https://www.rinnai.us/universal/message-from-the-president, https://www.rinnai.us/residential/corporate-history, https://www.rinnai.us/press-releases and https://www.rinnai.us/residential/locations took over 3 s to send their HTML from our server.

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

6 of 12 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://web-modules-de-na1.niceincontact.com/guide/channel-guide.css?29886791' from origin…”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight 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 8 cookies (measured from a US location before any click).

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