fantasypros.com website review

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

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

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, pub.network and Rubicon Project and others), adding 2.4 MB and 2.1 s of main-thread time.

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

pub.network costs a phone 389 ms of main-thread work and 450 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.

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

Pubmatic costs a phone 348 ms of main-thread work and 102 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.

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

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

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

3 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

142 KiB could be saved by minifying CSS.

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

Desktop scores 58 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 174 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.4 MB in 1,133 requests on a phone: scripts 3.7 MB (95), media 1.1 MB (1) and other files 540 KiB (544). Under 2 MB keeps phones on slow connections fast.

1 image (80 KiB) is 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.

1 image further down the page (80 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 88 characters, so Google will cut it off around 60: “Fantasy Football Rankings, 2026 Projections, Fantasy Baseball Cheat Sheets | FantasyPros”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 17 pages on fantasypros.com and 13 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.

The HTML your server sends has 117 of the 211 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/about/privacy/ccpa-data-subject-request-opt-out has no meta description, so Google writes the search snippet from whatever text it finds.

/nfl, /mlb, /nba and /nhl have no <h1> headline, so visitors and search engines get no clear main topic.

/nfl, /mlb, /nba, /nhl and /about/privacy/ccpa-data-subject-request-opt-out have 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 and read each the way a search engine does.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://support.fantasypros.com/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fantasypros.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 22 cookies, 1 of them by other companies (measured from a US location before any click).

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