Website review, no card needed
booksfy.in website review
Visit site (opens in a new tab)Reviewed 6 November 202664 issues · 101 checks
This review found 64 issues worth fixing on booksfy.in, 27 of them high impact, across 101 checks. The most urgent: render-blocking requests. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 174 ms |
| May 23, 2026 | 175 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 186 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 188 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 193 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 200 ms |
| Sep 26, 2026 | 194 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 139 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 130 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
Speed
Render-blocking requests
5.0 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused JavaScript
2.7 s · 413 KiBAbout 413 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Improve image delivery
1.8 s · 1.1 MB45 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused CSS
1.8 s · 367 KiBAbout 367 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Font display
1.9 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.9 s).
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,285 HTML elements
The page has 4,285 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
600 ms · 295 KiB80 files are served with short cache lifetimes, so returning visitors download them again (295 KiB).
8 third-party services on the page
8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Cloudflare CDN and others), adding 518 KiB and 636 ms of main-thread time.
Minify JavaScript
450 ms · 82 KiB82 KiB could be saved by minifying JavaScript.
Minify CSS
450 ms · 81 KiB81 KiB could be saved by minifying CSS.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 446 ms. During a long task the page ignores taps.
jQuery CDN adds 326 ms
326 msjQuery CDN costs a phone 326 ms of main-thread work and 31 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.
Google Tag Manager adds 293 ms
293 msGoogle Tag Manager costs a phone 293 ms of main-thread work and 343 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 710 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
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: 271 ms
271 msYour server sent the HTML in 271 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.
Largest Contentful Paint: 15.9 s
15.9 sYour largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.431
0.431The layout shifts by 0.431 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 321 ms
321 msScripts block taps and scrolling for 321 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 174 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
1 image over 500 KB
1789550746IIT-Banner.png weighs 845 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.4 MB in 109 requests
3.4 MBYour homepage downloads 3.4 MB in 109 requests on a phone: images 1.9 MB (55), scripts 790 KiB (16) and stylesheets 435 KiB (20). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (1.6 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.
An image on the first screen is lazy-loaded
1789550746IIT-Banner.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).
5 images far larger than shown
420 KiB5 images are downloaded at several times the size a phone draws them, for example 1789550746IIT-Banner.png at 1,400 px wide, shown at 396 px. Resized copies would save about 420 KiB.
About 1.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
92 images without alt text
92 images have no alt text, which hurts accessibility and image search.
128 links without text
128 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h4 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 20 failed. 3 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 (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “One Stop Shop For NCERT, CBSE and All Competitive Exam Books Booksfy - Booksfy”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (234 characters)
Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
496 internal links, 6 external
The homepage links to 496 pages on booksfy.in and 6 external pages.
3 checks passed
Structured data in place
Structured data found: Organization and WebSite.
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://booksfy.in/sitemap.xml.
AI search readiness
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://booksfy.in/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (7,370 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://booksfy.in/shoppingCart and https://booksfy.in/collections/ncert-books-combo-set use the same meta description. A description written for each page earns more clicks.
13 pages without an H1
https://booksfy.in/collections/ncert-books-class-1, https://booksfy.in/collections/ncert-books-class-2, https://booksfy.in/collections/ncert-books-class-3, https://booksfy.in/collections/ncert-books-class-4, https://booksfy.in/collections/ncert-books-class-5 and https://booksfy.in/collections/ncert-books-class-6 and 7 others 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 198 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
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
1 broken image
1 image failed to load on a phone, for example https://booksfy.in/.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
2 checks passed
Tap targets are thumb-sized
250 of 262 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 9,589 words of copy
The homepage carries about 9,589 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: “| Contact us”.
9 calls to action
The homepage has 9 calls to action, for example “Shop By Class”, “Shop By Subject” and “Shop By Exam”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
12 other companies contacted
Loading the homepage contacts 12 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 booksfy.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 64 issues on booksfy.in, including 26 speed issues, 5 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.