Website review, no card needed
hollywoodreporter.com website review
Visit site (opens in a new tab)Reviewed 12 October 202641 issues · 91 checks
This review found 41 issues worth fixing on hollywoodreporter.com, 18 of them high impact, across 91 checks. The most urgent: main-thread work: 13.7 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.7 s |
| Apr 25, 2026 | 1.7 s |
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 164 ms |
| Apr 25, 2026 | 162 ms |
| May 2, 2026 | 150 ms |
| May 9, 2026 | 143 ms |
| May 16, 2026 | 134 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 135 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.9 s
3.7 s
5.6 s
7.5 s
9.3 s
11.2 s
13.1 s
14.9 s
Speed
Main-thread work: 13.7 s
A phone's processor spends 13.7 s on main-thread work while loading, 8.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
JSDelivr CDN adds 1.3 s
1.3 sJSDelivr CDN costs a phone 1.3 s of main-thread work and 904 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.
Mobile performance score: 13
13/100Your mobile performance score is 13 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, Google/Doubleclick Ads and Ad Lightning and others), adding 2.8 MB and 3.3 s of main-thread time.
Use efficient cache lifetimes
150 ms · 1.6 MB175 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.
Reduce unused JavaScript
1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page.
Render-blocking requests
600 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Google/Doubleclick Ads adds 459 ms
459 msGoogle/Doubleclick Ads costs a phone 459 ms of main-thread work and 592 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.
Ad Lightning adds 439 ms
439 msAd Lightning costs a phone 439 ms of main-thread work and 181 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.
Optanon adds 365 ms
365 msOptanon costs a phone 365 ms of main-thread work and 303 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.
2,506 HTML elements
The page has 2,506 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
blogherads.com adds 156 ms
156 msblogherads.com costs a phone 156 ms of main-thread work and 590 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.
Legacy JavaScript
142 KiBPolyfills for old browsers add 142 KiB JavaScript that modern phones do not need.
Improve image delivery
85 KiB4 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 38 but mobile only 13. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user CLS: 0.41
0.41For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.
Time to Interactive: 60.0 s
60.0 sThe page becomes fully interactive after 60.0 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.485
0.485The layout shifts by 0.485 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mark Zuckerberg (Jeremy Strong) in 'The Social Reckoning.'”.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 678 ms
678 msReal visitors wait 678 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 164 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.2 MB in 1,084 requests
6.2 MBYour homepage downloads 6.2 MB in 1,084 requests on a phone: scripts 4.3 MB (179), other files 761 KiB (529) and fonts 431 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.75 g of CO₂e: 209.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
30 tap targets too small
30 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (10 elements)
Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 79 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (126 characters)
Your title is 126 characters, so Google will cut it off around 60: “The Hollywood Reporter – Movie news, TV news, awards news, lifestyle news, business news …”.
330 internal links, 101 external
The homepage links to 330 pages on hollywoodreporter.com and 101 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “Movie news, TV news, awards news, lifestyle news, business news and more from The Hollywood Reporter.”.
Canonical URL set
The canonical URL is https://www.hollywoodreporter.com/.
Structured data in place
Structured data found: Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.hollywoodreporter.com/sitemap.xml.
AI search readiness
robots.txt blocks 3 AI answer engine crawlers
3 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.hollywoodreporter.com/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (2,487 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.hollywoodreporter.com/t/awards, https://www.hollywoodreporter.com/t/international, https://www.hollywoodreporter.com/h/charts and https://www.hollywoodreporter.com/lists have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.hollywoodreporter.com/t/awards, https://www.hollywoodreporter.com/t/international, https://www.hollywoodreporter.com/t/thr-cover-story, https://www.hollywoodreporter.com/h/charts and https://www.hollywoodreporter.com/lists have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 160 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.hollywoodreporter.com/.
34 third-party cookies
34 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
13 small tap targets
13 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) NotSupportedError: Failed to execute 'browsingTopics' on 'Document': document.browsingTopics() is…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,728 words of copy
The homepage carries about 1,728 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SUBSCRIBE”.
11 calls to action
The homepage has 11 calls to action, for example “Subscribe”, “See My Options Sign Up” and “Subscribe Sign Up”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 4 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
88 other companies contacted
Loading the homepage contacts 88 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hollywoodreporter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on hollywoodreporter.com, including 21 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.