hasbropulse.com website review

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

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

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

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

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

6 third-party services load with your homepage (ZenDesk, Google Tag Manager and Cloudflare and others), adding 1.7 MB and 435 ms of main-thread time.

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

ZenDesk costs a phone 278 ms of main-thread work and 454 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.

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

Amplience costs a phone 1 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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.

2 KiB could be saved by minifying CSS.

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.43 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 118 requests on a phone: scripts 1.5 MB (32), images 1.0 MB (46) and HTML 248 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “The Official Site for Hasbro Collectibles & Exclusives | Hasbro Pulse”.

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

The homepage links to 5 pages on hasbropulse.com and 2 external pages.

A phone browser shows 781 words, but the HTML your server sends has only 115. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no /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 GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/order-status and /pages/hasbro-pulse-premium-terms all use the title “Hasbro Pulse”. Search engines can't tell which page to show for a search, so each competes with the others.

/order-status has no meta description, so Google writes the search snippet from whatever text it finds.

/order-status and /product/hasbro-pulse-premium/PULSEPREMIUM have no <h1> headline, so visitors and search engines get no clear main topic.

/order-status, /collections/shop-all-products and /product/hasbro-pulse-premium/PULSEPREMIUM 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 4 pages linked from your homepage and read each the way a search engine does.

51 of 118 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 (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “pwa-kit-react-sdk.registerServiceWorker ERROR ServiceWorker registration failed {"error":{"name":"TypeError","message":…”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

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

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

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

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.

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.

The homepage carries about 781 words of visible text.

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 Google Tag Manager (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

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

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