njedge.net website review

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

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

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

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

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

6 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 202 KiB and 97 ms of main-thread time.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Nation’s Nonprofit Technology Consortium The premier so…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.6 MB in 141 requests on a phone: images 5.8 MB (34), scripts 508 KiB (63) and fonts 176 KiB (4). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.

24 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

22 images (3.9 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.

NJEdge-Logo-WHITE-tight-300x190.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

9 elements hidden from screen readers can still receive keyboard focus.

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

3 links inside paragraphs rely on colour alone to stand out.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

The homepage links to 84 pages on njedge.net and 9 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://njedge.net/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://njedge.net/members-support, https://njedge.net/about, https://njedge.net/about/board-of-trustees, https://njedge.net/about/edge-team, https://njedge.net/affiliated-organizations and https://njedge.net/membership and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://njedge.net/membership has no <h1> headline, so visitors and search engines get no clear main topic.

https://njedge.net/affiliated-organizations took over 3 s to send its HTML from our server.

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

12 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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