Website review, no card needed
redis.io website review
Visit site (opens in a new tab)Reviewed 27 October 202629 issues · 78 checks
This review found 29 issues worth fixing on redis.io, 11 of them high impact, across 78 checks. The most urgent: mobile performance score: 31. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Redis
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 407 ms |
| May 16, 2026 | 383 ms |
| May 23, 2026 | 358 ms |
| May 30, 2026 | 331 ms |
| Jun 6, 2026 | 291 ms |
| Jun 13, 2026 | 296 ms |
| Jun 20, 2026 | 330 ms |
| Jun 27, 2026 | 364 ms |
| Jul 4, 2026 | 387 ms |
| Jul 11, 2026 | 340 ms |
| Jul 18, 2026 | 279 ms |
| Jul 25, 2026 | 224 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 215 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 243 ms |
| Aug 29, 2026 | 240 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 198 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 233 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
Speed
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
700 ms · 717 KiB23 files are served with short cache lifetimes, so returning visitors download them again (717 KiB).
Render-blocking requests
850 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 642 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 101 KiBAbout 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
350 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
1,637 HTML elements
The page has 1,637 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Amplitude Mobile Analytics adds 14 ms
14 msAmplitude Mobile Analytics costs a phone 14 ms of main-thread work and 373 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, TrustArc and 6sc.co and others), adding 771 KiB and 190 ms of main-thread time.
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.
1 checks passed
Server response: 68 ms
68 msYour server sent the HTML in 68 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.
Time to Interactive: 28.2 s
28.2 sThe page becomes fully interactive after 28.2 s. Good is under 3.8 s.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INQUIRING AGENTS WANT TO KNOW:”.
Total Blocking Time: 2.1 s
2.1 sScripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user INP: 331 ms
331 msReal visitors wait 331 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 933 ms
933 msReal visitors wait 933 ms for your server to start answering (75th percentile). Good is under 800 ms.
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 407 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 170 requests
5.8 MBYour homepage downloads 5.8 MB in 170 requests on a phone: scripts 3.1 MB (77), other files 2.0 MB (49) and HTML 427 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.65 g of CO₂e: 198.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
190 internal links, 16 external
The homepage links to 190 pages on redis.io and 16 external pages.
8 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Developers love Redis. Unlock the full potential of the Redis database with Redis Enterprise and start building blazing…”.
One H1 headline
Your main headline reads: “Inquiring agents want to know:”.
Title: 40 characters
Your title is a healthy 40 characters: “Redis - Real-time data for agents & apps”.
Canonical URL set
The canonical URL is https://redis.io/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://redis.io/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,324 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://redis.io/llms.txt (46 KiB, 199 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://redis.io/context-retriever is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages share a meta description
https://redis.io/resources/agent-memory-benchmark-report, https://redis.io/iris, https://redis.io/context-retriever, https://redis.io/agent-memory and https://redis.io/solutions/flex 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 78 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15332846&Ver=2&mid=ae733eb3-7e4f-4026-9961-74333c2e0b85&bo=2&sid=1d2408f0d24a11f18cbfd7ddf80766ee&vid=1d241ad0d24a11f1b6a20bb3e0a308b1&vids=1&msclkid=N&pi=918639831&lg.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
82 of 97 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 805 words of copy
The homepage carries about 805 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: “Pricing Let’s talk numbers” and “Redis on AWS Buy with cloud commits”.
14 calls to action
The homepage has 14 calls to action, for example “Join the Redis Partner Network”, “Book a meeting” and “Try Redis”.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
36 other companies contacted
Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) 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 redis.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Redis
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Hiring
- Hiring
- 27 open roles
- Teams
- Sales (17), Customer Org (3), Engineering (3), Marketing (2)
- Job board
- ashby
- Careers page
- redis.io/company/careers (opens in a new tab)
Company
- Employees
- 434
- Founded
- 2009
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on redis.io, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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.