Website review, no card needed
harpercollins.com website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 77 checks
This review found 46 issues worth fixing on harpercollins.com, 17 of them high impact, across 77 checks. The most urgent: google Tag Manager adds 1.1 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for HarperCollins
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DNot ranked: the homepage didn't load normally in this review.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 167 ms |
| May 23, 2026 | 167 ms |
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 184 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 191 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 202 ms |
| Aug 29, 2026 | 204 ms |
| Sep 5, 2026 | 203 ms |
| Sep 12, 2026 | 199 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 200 ms |
| Oct 17, 2026 | 200 ms |
| Oct 24, 2026 | 197 ms |
| Oct 31, 2026 | 194 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
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 967 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: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.2 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
550 ms · 932 KiB17 images could be 932 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Use efficient cache lifetimes
400 ms · 677 KiB47 files are served with short cache lifetimes, so returning visitors download them again (677 KiB).
Render-blocking requests
650 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Google CDN adds 430 ms
430 msGoogle CDN costs a phone 430 ms of main-thread work and 742 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.
Facebook adds 302 ms
302 msFacebook costs a phone 302 ms of main-thread work and 283 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 327 ms. During a long task the page ignores taps.
usablenet.com adds 263 ms
263 msusablenet.com costs a phone 263 ms of main-thread work and 23 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,271 HTML elements
The page has 2,271 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
100 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused CSS
83 KiBAbout 83 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).
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 11.4 s
11.4 sYour largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 36.8 s
36.8 sThe page becomes fully interactive after 36.8 s. Good is under 3.8 s.
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
Real-user TTFB: 810 ms
810 msReal visitors wait 810 ms for your server to start answering (75th percentile). Good is under 800 ms.
74 images without width and height
74 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.127
0.127The layout shifts by 0.127 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 167 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 183 ms
183 msReal visitors wait 183 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 7.9 MB in 416 requests
7.9 MBYour homepage downloads 7.9 MB in 416 requests on a phone: scripts 3.5 MB (124), other files 1.7 MB (196) and images 1.7 MB (38). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Billboard-Mobile_BestAmerica_67.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
64 form fields without a label
64 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “Just a moment...”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.harpercollins.com/sitemap.xml.
AI search readiness
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
32 small tap targets
32 of 147 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “ReferenceError: $ is not defined”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Homepage answers HTTP 403
Your homepage answered with HTTP 403, so visitors and search engines may see an error page.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 639 words of copy
The homepage carries about 639 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “Shop now”.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 5 mores (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.
40 cookies set on arrival
40Opening the homepage sets 40 cookies (measured from a US location before any click).
No consent tool detected
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.
50 other companies contacted
Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 harpercollins.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Founded
- 1817
- Headquarters
- 195 Broadway
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on harpercollins.com, including 22 speed issues, 9 SEO issues and 5 conversion gaps. 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.