csdnb.org website review

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

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

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

About 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

Your mobile performance score is 18. 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, Other Google APIs/SDKs and Cloudflare and others), adding 1.0 MB and 502 ms of main-thread time.

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

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

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

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

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

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. 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 100 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.

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

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

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

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

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

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

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

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

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

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

6 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-31, real Chrome visitors' tap response (inp) went from 113 ms to 115 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.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.9 MB in 62 requests on a phone: scripts 1.5 MB (11), images 824 KiB (29) and fonts 201 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

Some list items are not inside a list.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

No XML sitemap at https://www.csdnb.org/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 148 pages on csdnb.org and 62 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.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Large scripts ship without source maps.

1 link go through two or more redirects, for example https://sites.google.com/a/csdnbstaff.org/csdnb-staff-portal/Home.

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

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

csdnb.org'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.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.