Website review, no card needed
yahoo.com website review
Visit site (opens in a new tab)Reviewed 12 October 202626 issues · 64 checks
This review found 26 issues worth fixing on yahoo.com, 9 of them high impact, across 64 checks. The most urgent: page weight: 4.3 MB. 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) |
|---|---|
| Apr 18, 2026 | 2.0 s |
| Apr 25, 2026 | 2.0 s |
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 196 ms |
| Apr 25, 2026 | 200 ms |
| May 2, 2026 | 204 ms |
| May 9, 2026 | 204 ms |
| May 16, 2026 | 201 ms |
| May 23, 2026 | 198 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 200 ms |
| Jun 20, 2026 | 204 ms |
| Jun 27, 2026 | 206 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 184 ms |
| Aug 8, 2026 | 183 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 190 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 208 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 215 ms |
| Oct 3, 2026 | 210 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
Real-user TTFB: 825 ms
825 msReal visitors wait 825 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 196 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).
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 INP: 198 ms
198 msReal visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 4.3 MB
4.3 MBYour homepage downloads 4.3 MB on a phone, 710 KiB of it images (16%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
https://d29szjachogqwa.cloudfront.net/images/user-uploaded/f is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
The skip-link target should exist and be focusable (3 elements)
The skip-link target should exist and be focusable: 3 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
47 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: 47 passed and 5 failed. 4 mores 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.
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos”.
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 XML sitemap
No XML sitemap at https://www.yahoo.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
20 internal links, 13 external
The homepage links to 20 pages on yahoo.com and 13 external pages.
4 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Latest news coverage, email, free stock quotes, live scores and video are just the beginning. Discover more every day a…”.
Canonical URL set
The canonical URL is https://www.yahoo.com/.
Structured data in place
Structured data found: NewsMediaOrganization and WebSite.
robots.txt in place
robots.txt is in place.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
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.
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
2 checks passed
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 (384 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to /finance/markets/article/wall-street-banks-had-a-blockbuster-first-half-higher-rates-will-test-the-boom-180220191.html, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without an H1
/news has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
/all 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 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 570 words of copy
The homepage carries about 570 words of visible text.
1 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics, Google Tag Manager and Taboola and 1 more (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 2 of them by other companies (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.
55 other companies contacted
Loading the homepage contacts 55 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 yahoo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on yahoo.com, including 1 speed issue, 4 SEO issues and 7 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.