pluto.tv website review

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

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

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

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

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

6 files are served with short cache lifetimes, so returning visitors download them again (663 KiB).

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

3 third-party services load with your homepage (paramount.com, plutostatic.tv and ketchcdn.com), adding 1.2 MB and 327 ms of main-thread time.

About 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

paramount.com costs a phone 327 ms of main-thread work and 12 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.

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

plutostatic.tv costs a phone 0 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.

14 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need.

Desktop scores 54 but mobile only 28. 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.

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.

Real visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors wait 3.5 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Real visitors wait 345 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Your homepage downloads 3.9 MB in 176 requests on a phone: scripts 2.0 MB (66), images 1.2 MB (69) and other files 330 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

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.

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

No XML sitemap at https://pluto.tv/sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 103 pages on pluto.tv and 26 external pages.

There is no https://pluto.tv/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.

https://pluto.tv/us/home has no <h1> headline, so visitors and search engines get no clear main topic.

https://pluto.tv/us/category/fff75417-3a50-4042-9ec2-bec991e9ca02 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.

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

2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'register')”.

Large scripts ship without source maps.

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

The homepage has only about 14 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.

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

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