investors.com website review

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

154 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.

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

Your mobile performance score is 6. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 5,288 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, LiveRamp Privacy Manager and Rubicon Project and others), adding 3.4 MB and 3.4 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

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

LiveRamp Privacy Manager costs a phone 644 ms of main-thread work and 123 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.

Google/Doubleclick Ads costs a phone 468 ms of main-thread work and 798 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.

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

Rubicon Project costs a phone 517 ms of main-thread work and 98 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.

11 images could be 309 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

Other Google APIs/SDKs costs a phone 320 ms of main-thread work and 606 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.

362 KiB could be saved by minifying JavaScript.

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

9 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

For real visitors the layout shifts by 0.52 (75th percentile). Good is under 0.1.

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

Your largest element takes 23.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Wall Street "WALL ST" sign and broadway street over America…”.

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

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

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

The layout shifts by 0.43 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.5 MB in 1,106 requests on a phone: scripts 8.4 MB (245), images 1.8 MB (289) and HTML 789 KiB (118). Under 2 MB keeps phones on slow connections fast.

7 images (290 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.

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

1 button has no accessible name, so screen readers announce just “button”.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

4 tap targets are too small or too close together to hit reliably with a finger.

2 elements hidden from screen readers can still receive keyboard focus.

1 link inside paragraphs relies on colour alone to stand out.

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

3 visible links have no text or label, so screen readers cannot say where they go.

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

Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (2 elements).

Elements with visible text labels do not have matching accessible names. (1 element).

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Your title is 70 characters, so Google will cut it off around 60: “Investor’s Business Daily | Stock News and Stock Market Analysis - IBD”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 210 pages on investors.com and 164 external pages.

Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.investors.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.

robots.txt blocks ClaudeBot, Google-Extended, Applebot-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.

https://www.investors.com/market-trend/ibds-etf-market-strategy/ibds-etf-market-strategy and https://www.investors.com/ibd-indexes/ibd-etf-indexes-ibd-50-etf-leaders-breakout-stocks-etf-ffty-ldrs-bout all use the title “IBD's ETF Market Strategy | Investor's Business Daily”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.investors.com/tag/all-news-and-stock-ideas has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.investors.com/market-trend/ibds-etf-market-strategy/ibds-etf-market-strategy and https://www.investors.com/ibd-indexes/ibd-etf-indexes-ibd-50-etf-leaders-breakout-stocks-etf-ffty-ldrs-bout use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.investors.com/stock-lists/best-growth-stocks-buy-watch-ibd-stock-lists, whose canonical is https://www.investors.com/research/best-growth-stocks-buy-watch-ibd-stock-lists. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.investors.com/tag/all-news-and-stock-ideas, https://www.investors.com/category/market-trend/the-big-picture, https://www.investors.com/category/stock-lists/stocks-near-a-buy-zone and https://www.investors.com/ibd-data-tables have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4017980&Ver=2&mid=737229a8-0faf-41b5-a2bb-16883180f378&bo=1&sid=93a633e0d13811f194f3057cd1405c18&vid=93a665e0d13811f1930de91c5dbad330&vids=1&msclkid=N&pi=918639831&lg=.

25 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

The homepage carries about 1,389 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 9 mores (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.

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

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.

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