usnews.com website review

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

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

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

Tealium costs a phone 1.7 s of main-thread work and 73 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 1.0 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Tealium, Google/Doubleclick Ads and saambaa.com and others), adding 4.7 MB and 4.3 s of main-thread time.

7 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

saambaa.com costs a phone 544 ms of main-thread work and 343 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 119 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

clipcentric.com costs a phone 227 ms of main-thread work and 2.3 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.

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

Amazon Ads costs a phone 249 ms of main-thread work and 402 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 2,023 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

14 KiB could be saved by minifying JavaScript.

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

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.

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

Your largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “It’s not just partisan takeovers that are possible in midte…”.

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

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

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

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

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

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

Your homepage downloads 34.5 MB in 1,498 requests on a phone: images 24.4 MB (505), scripts 6.1 MB (201) and media 2.2 MB (1). Under 2 MB keeps phones on slow connections fast.

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

Form elements do not have associated labels (1 element).

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

Elements use prohibited ARIA attributes (1 element).

Links do not have a discernible name (1 element).

Heading elements are not in a sequentially-descending order (7 elements).

Elements with visible text labels do not have matching accessible names. (3 elements).

robots.txt has 1 error.

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

The page uses 3 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

28 errors were logged to the browser console during Google's test (“[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Large scripts ship without source maps.

We could not load https://usnews.com from our server, so the homepage checks are missing. If the site is up, it may block automated visitors.