ocls.org website review

22 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.7 MB and 1.1 s of main-thread time.

About 924 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

57 KiB could be saved by minifying JavaScript.

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

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

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

Google Maps costs a phone 138 ms of main-thread work and 329 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.

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

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

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

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.

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

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman dances with a group of people, a smile on her face.”.

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

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

The layout shifts by 0.411 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 6.7 MB in 111 requests on a phone: images 4.1 MB (49), scripts 1.8 MB (36) and fonts 732 KiB (6). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.7 MB together. On a phone connection a single image that size takes seconds.

14 images (3.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.

12 images further down the page (2.4 MB) 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.90 g of CO₂e: 228.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 dropdown has no label.

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

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

20 images have no alt text, which hurts accessibility and image search.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 123 pages on ocls.org and 86 external pages.

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.

There is no https://ocls.org/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.

https://ocls.org/booksandmore is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://ocls.org/about/system-holiday-closings-calendar, https://ocls.org/using-library, https://ocls.org/using-library/getting-started-library, https://ocls.org/using-library/types-cards/what-are-types-cards, https://ocls.org/using-library/library-policies and https://ocls.org/using-library/getting-started-library-locations-melrose-center-rooms-studios-types-of-cards/what-are-the-librarys-rules-of-conduct and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://ocls.org/using-library/getting-started-library, whose canonical is https://ocls.org/using-library/getting-started-library/getting-started-library. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ocls.org/using-library, https://ocls.org/using-library/types-cards/what-are-types-cards, https://ocls.org/using-library/library-policies, https://ocls.org/using-library/getting-started-library-locations-melrose-center-rooms-studios-types-of-cards/what-are-the-librarys-rules-of-conduct, https://ocls.org/using-library/fees/library-fees and https://ocls.org/frequently-asked-questions and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://ocls.org/wp-content/themes/ocls-theme/images/default-image.jpg.

51 of 120 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://stats.g.doubleclick.net/g/collect?v=2&ngs=1&ibt=1&tid=G-GXEJ84YGCN&cid=98694051.1793935475&gtm=4…”.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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 6 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.