ojrsd.com website review

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

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

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Cloudflare and others), adding 1.1 MB and 209 ms of main-thread time.

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

finalsite.net costs a phone 0 ms of main-thread work and 768 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.

6 long tasks block the main thread while loading, the longest for 205 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.

Your largest element takes 11.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 first text or image appears after 7.4 s on a phone. Good is under 1.8 s.

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

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

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

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

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

Your homepage downloads 2.1 MB in 56 requests on a phone: scripts 923 KiB (8), images 796 KiB (28) and fonts 197 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example FCHeartPic11.jpg at 512 px wide, shown at 1 px. Resized copies would save about 221 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.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 contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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.

Your title is only 24 characters: “Home - Owen J Roberts Sd”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 24 characters: “Home - Owen J Roberts Sd”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Home” and “Wildcat Fast Facts”). One clear main headline is easier for people and search engines.

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

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

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

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 327 pages on ojrsd.com and 50 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 https://www.ojrsd.com/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://www.ojrsd.com/about-us/facilities-planning, https://www.ojrsd.com/about-us/facilities-planning/long-term-facilities-plan and https://www.ojrsd.com/about-us/facilities-planning/secondary-campus-plan all use the title “Long-Term Facilities Plan”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ojrsd.com/about-us/facilities-planning/long-term-facilities-plan took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 200 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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Before a visitor clicks anything, the page loads 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 1 cookie (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.