Website review, no card needed
harpercollins.co.in website review
Visit site (opens in a new tab)Reviewed 31 October 202639 issues · 87 checks
This review found 39 issues worth fixing on harpercollins.co.in, 19 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
71C- #101,814 of 126,508 reviewed websitesbeats 17%
- #61,735 of 70,497 online storesbeats 10%
- #2,142 of 2,974 WooCommerce storesbeats 23%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 113 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 108 ms |
| Oct 24, 2026 | 108 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
2.3 s
4.5 s
6.8 s
9.1 s
11.3 s
13.6 s
15.8 s
18.1 s
Speed
Reduce unused JavaScript
4.1 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Improve image delivery
1.9 s · 3.0 MB28 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
3.3 s43 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, userway.org and Cloudflare CDN and others), adding 1.2 MB and 664 ms of main-thread time.
Google Tag Manager adds 585 ms
585 msGoogle Tag Manager costs a phone 585 ms of main-thread work and 978 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
450 ms · 66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,733 HTML elements
The page has 1,733 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 33 KiB33 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
2 KiB3 files are served with short cache lifetimes, so returning visitors download them again (2 KiB).
Duplicated JavaScript
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 425 ms
425 msYour server sent the HTML in 425 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 LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.7 s
21.7 sYour largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Reading helps us feel more present, more connected, and qui…”. Most of its time is element render delay (11.0 s).
Speed Index: 24.0 s
24.0 sVisually, the page fills in at 24.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.9 s
40.9 sThe page becomes fully interactive after 40.9 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.13
0.13For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.
43 images without width and height
43 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 300 ms
300 msScripts block taps and scrolling for 300 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 113 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 114 ms
114 msReal visitors wait 114 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.8 MB in 362 requests
8.8 MBYour homepage downloads 8.8 MB in 362 requests on a phone: images 4.4 MB (51), scripts 2.7 MB (181) and fonts 1.1 MB (18). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
THE-REAL-HORRORS-ARE-HAPPENING-IN-REAL-TIME.-newsletter.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.9 MB3 images are downloaded at several times the size a phone draws them, for example THE-REAL-HORRORS-ARE-HAPPENING-IN-REAL-TIME.-newsletter.png at 1,371 px wide, shown at 150 px. Resized copies would save about 1.9 MB.
13 images in older formats
13 images (2.8 MB) 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.
17 images below the first screen load straight away
17 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.48 g of CO₂e: 297.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 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 (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 16 external
The homepage links to 100 pages on harpercollins.co.in and 16 external pages.
8 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “We are among the leading publishing houses in India, bringing bestselling books and authors to readers worldwide. Conne…”.
One H1 headline
Your main headline reads: “Join Us in the Year of Reading for Pleasure”.
Title: 44 characters
Your title is a healthy 44 characters: “Leading Book Publisher | HarperCollins India”.
Canonical URL set
The canonical URL is https://harpercollins.co.in/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://harpercollins.co.in/wp-sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,743 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://harpercollins.co.in/llms.txt (6 KiB, 36 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://harpercollins.co.in/2026-the-year-of-reading-for-pleasure, which answers with an error. Visitors hit a dead end and search engines drop it.
7 pages slow to respond
https://harpercollins.co.in/our-books, https://harpercollins.co.in/blogs, https://harpercollins.co.in/publish-with-us, https://harpercollins.co.in/product/arguments-with-gandhi, https://harpercollins.co.in/product/sea-salt-and-spice-a-history-of-mumbai-through-food and https://harpercollins.co.in/product/the-first-house-from-the-booker-prize-shortlisted-author-of-burnt-sugar and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “wp is not defined”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
29 of 29 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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 2,455 words of copy
The homepage carries about 2,455 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Learn more”, “Start reading” and “War Of Lanka (Ram Chandra Series Book 4)”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
9 other companies contacted
Loading the homepage contacts 9 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.co.in, 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
- React
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- GoDaddy
Company
- Founded
- 1992
- Headquarters
- Noida
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on harpercollins.co.in, including 21 speed issues, 1 SEO issue and 3 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.