worldofbooks.com website review

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

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

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

57 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

53 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

Shopify costs a phone 100 ms of main-thread work and 369 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.

8 third-party services load with your homepage (Optanon, Shopify and visually.io and others), adding 755 KiB and 349 ms of main-thread time.

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

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

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

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

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

Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide 1”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.0 MB in 408 requests on a phone: images 4.0 MB (63), other files 1.3 MB (206) and scripts 1.2 MB (99). Under 2 MB keeps phones on slow connections fast.

SYB_US_Mobile_29.10.26.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).

1 image (35 KiB) is 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.

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

10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 tap targets are too small or too close together to hit reliably with a finger.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.worldofbooks.com/tools/sitemap-builder/sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 258 pages on worldofbooks.com and 17 external pages.

Your homepage links to https://www.worldofbooks.com/pages/autumn and https://www.worldofbooks.com/pages/pride-month, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.worldofbooks.com/pages/sell-your-books, https://www.worldofbooks.com/collections/summer-reads-under-4 and https://www.worldofbooks.com/pages/sustainability-report-2025 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.worldofbooks.com/pages/sell-your-books, https://www.worldofbooks.com/pages/celebrating-black-authors and https://www.worldofbooks.com/pages/books-of-the-month have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.worldofbooks.com/pages/sell-your-books, https://www.worldofbooks.com/pages/christmas, https://www.worldofbooks.com/pages/books-authors-of-the-month, https://www.worldofbooks.com/pages/celebrating-black-authors, https://www.worldofbooks.com/pages/books-of-the-month and https://www.worldofbooks.com/collections/tiktok-us took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 112 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=16004578&tm=gtm002&Ver=2&mid=bb1bf9c1-589c-46c5-8d2e-fff7d66fe433&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=World%20of%20Books%20%7C%20Buy%20used%20books.

3 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 306 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Ads (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.

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

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