Website review, no card needed
rainbird.com website review
Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 90 checks
This review found 38 issues worth fixing on rainbird.com, 17 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.7 s |
| May 16, 2026 | 7.4 s |
| May 23, 2026 | 7.2 s |
| May 30, 2026 | 7.1 s |
| Jun 6, 2026 | 6.9 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 111 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 125 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 141 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 99 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 85 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 122 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
6.4 s · 2.7 MB39 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).
Improve image delivery
5.5 s · 2.7 MB11 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.5 s faster on a phone.
Render-blocking requests
3.4 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused JavaScript
1.5 s · 281 KiBAbout 281 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Optanon and AddToAny and others), adding 546 KiB and 249 ms of main-thread time.
Reduce unused CSS
150 ms · 93 KiBAbout 93 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.
Legacy JavaScript
150 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 401 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.7 s
21.7 sYour largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “design services”.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 111 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.7 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 93 ms
93 msScripts block the page for only 93 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 73 requests
5.1 MBYour homepage downloads 5.1 MB in 73 requests on a phone: images 4.2 MB (35), scripts 557 KiB (15) and fonts 148 KiB (4). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.
21 images in older formats
21 images (4.4 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.
5 images below the first screen load straight away
5 images further down the page (427 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.43 g of CO₂e: 171.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
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)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
10 H1 headlines
There are 10 <h1> headlines (“”, “Region Switcher” and “Quick Jump To”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
137 internal links, 26 external
The homepage links to 137 pages on rainbird.com and 26 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Rain Bird is a leading global manufacturer and provider of irrigation products and services. Learn about our company, c…”.
Title: 39 characters
Your title is a healthy 39 characters: “Rain Bird | A Global Irrigation Company”.
Canonical URL set
The canonical URL is http://www.rainbird.com/.
Structured data in place
Structured data found: Organization.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.rainbird.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.rainbird.com/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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (803 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
13 pages share 3 titles
/, https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/en and https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/es all use the title “Rain Bird | A Global Irrigation Company”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/fr, https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/lta/en, https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/lta/es, https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/eur/en, https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/eur/es and https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/eur/fr and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/en and https://www.rainbird.com/g/sAVxu4hVFWHLOMnAMpCnADfKtW75HDReuf4uQMGRv8TMHXtYGDxGbHtHe4jFsvN3/usa/es use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 466 words of copy
The homepage carries about 466 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
19 calls to action
The homepage has 19 calls to action, for example “Apply”, “SHOP RAIN BIRD” and “CONTACT”.
2 short forms
2 short forms (7 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at rainbird.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Company
- Employees
- 848
- Founded
- 1933
- Headquarters
- Azusa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on rainbird.com, including 14 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.