nrf.com website review

About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Insider and Google Tag Manager and others), adding 2.3 MB and 860 ms of main-thread time.

Your mobile performance score is 62 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

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

YouTube costs a phone 305 ms of main-thread work and 971 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.

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

Insider costs a phone 231 ms of main-thread work and 470 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.

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

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

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Desktop scores 90 but mobile only 62. 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.

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 page becomes fully interactive after 28.9 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.8 MB in 176 requests on a phone: scripts 2.8 MB (66), images 2.6 MB (38) and fonts 181 KiB (11). Under 2 MB keeps phones on slow connections fast.

6 images (758 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.

8 images further down the page (516 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example nrff_honors27_1600x900_the_list.webp at 1,600 px wide, shown at 310 px. Resized copies would save about 113 KiB.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

There are 3 <h1> headlines (“2026 Annual Holiday Forecast”, “2026 Winter Holiday Webinar” and “CNBC/NRF Retail Monitor Upgrade”). One clear main headline is easier for people and search engines.

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

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 107 pages on nrf.com and 47 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.

https://nrf.com/membership and https://nrf.com/membership/committees-and-councils have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://nrf.com/advocacy/policy-issues/digital-pricing-and-retail, whose canonical is https://nrf.com/advocacy/policy-issues/data-driven-pricing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nrf.com/membership took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://nrf.com/.

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

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

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

1 error was logged to the browser console while the page loaded, for example “Service Worker registration failed: TypeError: Cannot read properties of undefined (reading 'register')”.

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 671 words of visible text.

Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics and Google Tag Manager (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 6 cookies, 1 of them by other companies (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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.