pbk.com website review

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

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

1 third-party service load with your homepage (Vimeo), adding 30.6 MB and 0 ms of main-thread time.

Vimeo costs a phone 0 ms of main-thread work and 30.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.

Your mobile performance score is 75 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

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

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

Polyfills for old browsers add 12 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.

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Your homepage downloads 35.2 MB in 44 requests on a phone: media 33.4 MB (8), images 1.3 MB (15) and scripts 455 KiB (9). Under 2 MB keeps phones on slow connections fast.

6 images (868 KiB) 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 6 <h1> headlines (“Creating experiences that unite communities”, “Designing for the Future” and “Taking Learning Outdoors”). One clear main headline is easier for people and search engines.

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

The homepage links to 43 pages on pbk.com and 12 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.

/prek-12-education, /civic and /health-wellness have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

Opening the homepage sets 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.