Website review, no card needed
forgottosaveforretirement.com website review
Visit site (opens in a new tab)Reviewed 20 November 202625 issues · 58 checks
This review found 25 issues worth fixing on forgottosaveforretirement.com, 11 of them high impact, across 58 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 6.4 s |
| Jun 6, 2026 | 6.4 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.4 s |
| Jul 4, 2026 | 6.4 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.4 s |
| Jul 25, 2026 | 6.3 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.2 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.2 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.2 s |
| Sep 19, 2026 | 6.2 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.2 s |
| Oct 10, 2026 | 6.2 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 6.1 s |
| Oct 31, 2026 | 6.1 s |
| Nov 7, 2026 | 6.0 s |
| Nov 14, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 706 ms |
| Jun 6, 2026 | 714 ms |
| Jun 13, 2026 | 721 ms |
| Jun 20, 2026 | 728 ms |
| Jun 27, 2026 | 750 ms |
| Jul 4, 2026 | 765 ms |
| Jul 11, 2026 | 777 ms |
| Jul 18, 2026 | 786 ms |
| Jul 25, 2026 | 781 ms |
| Aug 1, 2026 | 772 ms |
| Aug 8, 2026 | 761 ms |
| Aug 15, 2026 | 744 ms |
| Aug 22, 2026 | 735 ms |
| Aug 29, 2026 | 732 ms |
| Sep 5, 2026 | 730 ms |
| Sep 12, 2026 | 733 ms |
| Sep 19, 2026 | 736 ms |
| Sep 26, 2026 | 734 ms |
| Oct 3, 2026 | 737 ms |
| Oct 10, 2026 | 736 ms |
| Oct 17, 2026 | 729 ms |
| Oct 24, 2026 | 728 ms |
| Oct 31, 2026 | 723 ms |
| Nov 7, 2026 | 720 ms |
| Nov 14, 2026 | 711 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.9 s
5.9 sReal visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 703 ms
703 msReal visitors wait 703 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 706 ms to 711 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.4 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 783 ms
783 msReal visitors wait 783 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
2 images in older formats
2 images (296 KiB) 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.
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.6 MB
1.6 MBYour homepage downloads 1.6 MB on a phone, 315 KiB of it images (19%). That is a lean page.
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
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
20 tap targets too small
20 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (41 elements)
All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
13 internal links, 2 external
The homepage links to 13 pages on forgottosaveforretirement.com and 2 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “The Budget Retirement Options channel is changing how retirees think about their golden years by offering realistic, en…”.
Title: 35 characters
Your title is a healthy 35 characters: “Budget Retirement Options - YouTube”.
Canonical URL set
The canonical URL is https://www.youtube.com/channel/UCYlar7rn3XtGScuZ80rAPMg.
Structured data in place
Structured data found: ProfilePage.
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://www.youtube.com/sitemaps/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
10%A phone browser shows 276 words, but the HTML your server sends has only 28. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No Organization structured data
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.
No llms.txt
There is no https://www.youtube.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.
1 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.
Other pages
1 page without a title
https://www.youtube.com/ads has no <title>, so Google invents the link text in results.
4 pages without a meta description
https://www.youtube.com/t/contact_us, https://www.youtube.com/ads, https://www.youtube.com/t/terms and https://www.youtube.com/t/privacy have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.youtube.com/about/copyright, whose canonical is https://www.youtube.com/howyoutubeworks/copyright. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
/, https://www.youtube.com/ads and https://www.youtube.com/new have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.youtube.com/about 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
18 small tap targets
18 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 276 words of copy
The homepage carries about 276 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe”.
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
No consent tool detected
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.
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.
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 forgottosaveforretirement.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
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on forgottosaveforretirement.com, including 5 speed issues, 1 SEO issue and 3 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.