pbclibrary.org website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

18 images could be 783 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

8 third-party services load with your homepage (bibliocommons.com, Google Tag Manager and bibliocms.com and others), adding 4.6 MB and 899 ms of main-thread time.

10 files are served with short cache lifetimes, so returning visitors download them again (580 KiB).

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

bibliocommons.com costs a phone 366 ms of main-thread work and 1.7 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.

bibliocms.com costs a phone 172 ms of main-thread work and 2.3 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.

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

36 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

5 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

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

Your largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Featured View previous item Access to County Library & Park…”.

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

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

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

13 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-24, real Chrome visitors' tap response (inp) went from 127 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.5 MB in 88 requests on a phone: images 2.7 MB (31), scripts 1.7 MB (27) and HTML 857 KiB (1). Under 2 MB keeps phones on slow connections fast.

21 images (2.3 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.

2 images are downloaded at several times the size a phone draws them, for example Untitled-1-12.png at 1,500 px wide, shown at 330 px. Resized copies would save about 145 KiB.

3 images further down the page (221 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

15 visible links have no text or label, so screen readers cannot say where they go.

Your meta description is only 39 characters: “Link to Library card application page …”. 70 to 160 characters is enough to sell the click.

The homepage links to 125 pages on pbclibrary.org and 111 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.

Your homepage links to /using-the-library, which answers with an error. Visitors hit a dead end and search engines drop it.

/faqs has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cor-liv-cdn-static.bibliocommons.com/dynamic_stylesheet/FL-PALMBEACH/external_libr…”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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 1,051 words of visible text.

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

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

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.

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