saytechnologies.com website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.

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

Your mobile performance score is 33 (desktop: 57). 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, Facebook and singular.net and others), adding 1.2 MB and 947 ms of main-thread time.

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

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

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

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

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

About 16 KiB of CSS is downloaded but never applied on this page.

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

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.

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

Your largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Your shares. Your say.”.

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

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

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

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

2 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' tap response (inp) went from 137 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 98 requests on a phone: scripts 3.0 MB (32), images 1.6 MB (19) and fonts 173 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

8 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.

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

Your title is only 9 characters: “Say by RH”. 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 only 49 characters: “Say brings investors closer to their investments.”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“A direct line to every shareholder”, “What is Say by Robinhood?” and “How Say by Robinhood helps”). One clear main headline is easier for people and search engines.

2 links have no real href, so search engines can't follow them.

The homepage links to 56 pages on saytechnologies.com and 34 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 /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.

/sitemap.html, /sitemap-crypto.html and /sitemap-marketing.html have no <title>, so Google invents the link text in results.

/us/en/say-by-robinhood/for-companies, /us/en/say-by-robinhood/contact, /sitemap.html, /sitemap-crypto.html and /sitemap-marketing.html have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /us/en/invest, whose canonical is /invest. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/sitemap.html, /sitemap-crypto.html and /sitemap-marketing.html have no <h1> headline, so visitors and search engines get no clear main topic.

/sitemap.html has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.robinhood.com/assets/generated_assets/brand/_next/static/css/3e7328d479a66ab25…”.

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

Large scripts ship without source maps.

Opening https://saytechnologies.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://saytechnologies.com/terms.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

robinhood.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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.

The homepage carries about 479 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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