juniorlibraryguild.com website review

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and zoom.us and others), adding 2.2 MB and 677 ms of main-thread time.

5 images could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

About 270 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

410 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 314 ms of main-thread work and 363 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.

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

zoom.us costs a phone 116 ms of main-thread work and 1.6 MB 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 files are served with short cache lifetimes, so returning visitors download them again (193 KiB).

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Desktop scores 71 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A curated selection of the best new books delivered monthly…”.

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

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

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

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

7 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.4 MB in 231 requests on a phone: scripts 2.8 MB (161), images 982 KiB (30) and fonts 334 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image (77 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.

1 image further down the page (77 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

Some list items are not inside a list.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Some lists contain elements other than list items, which screen readers announce wrongly.

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is only 52 characters: “Junior Library Guild, Library Vendor, Best New Books”. 70 to 160 characters is enough to sell the click.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 97 pages on juniorlibraryguild.com and 21 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

/membership-benefits is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/categories, /categories/elementary, /categories/middle-school, /categories/high-school, /shop-books/all and /shop-books/all/in-stock and 4 others use the same meta description. A description written for each page earns more clicks.

/categories, /categories/elementary, /categories/middle-school, /categories/high-school, /shop-books/all and /shop-books/all/in-stock and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134598678&tm=gtm002&Ver=2&mid=bc832a7d-86f5-4b60-963f-2a6fdc62a217&bo=1&sid=8d053b30cc4d11f1abd1e5e69a49a0f3&vid=8d052f40cc4d11f1ba0ccb7928818d5e&vids=1&msclkid=N&pi=9.

13 of 44 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://302-laa-976.mktoutil.com/mktoutil/lpDomain?_mchId=302-LAA-976&_mchTd=juniorlibraryguild.com' vio…”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://www.juniorlibraryguild.com/fun-activities/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

juniorlibraryguild.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be juniorlibraryguild.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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