johnstoncc.edu website review

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

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

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

651 KiB could be saved by minifying JavaScript.

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

Your mobile performance score is 39. 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, 451.io and Facebook and others), adding 1.8 MB and 827 ms of main-thread time.

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

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

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

451.io costs a phone 160 ms of main-thread work and 624 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.

Cloudflare CDN costs a phone 128 ms of main-thread work and 303 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.

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

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

11 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 46.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “placeholder”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 114 ms to 128 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.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.1 MB in 82 requests on a phone: images 7.3 MB (16), scripts 2.5 MB (29) and fonts 103 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

9 images are downloaded at several times the size a phone draws them, for example gdavis.png at 1,060 px wide, shown at 45 px. Resized copies would save about 4.2 MB.

11 images (7.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.

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

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 26 characters: “Johnston Community College”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 88 pages on johnstoncc.edu and 22 external pages.

There is no https://www.johnstoncc.edu/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.johnstoncc.edu/index.php and / all use the title “Johnston Community College”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.johnstoncc.edu/community/index.html, https://www.johnstoncc.edu/foundation/index.html, https://www.johnstoncc.edu/student-support/index.html and https://www.johnstoncc.edu/news/index.php have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.johnstoncc.edu/index.php. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, 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 7 cookies, 1 of them by other companies (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.