nalearning.org website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.7 s.

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

9 images could be 1.8 MB 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.

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

6 third-party services load with your homepage (Google CDN, avochato.com and Other Google APIs/SDKs and others), adding 2.4 MB and 1.1 s of main-thread time.

About 558 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.

avochato.com costs a phone 417 ms of main-thread work and 1.5 MB 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.

Google CDN costs a phone 499 ms of main-thread work and 730 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 95 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.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Desktop scores 96 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “North American Learning Institute (NALI) is an eLearning or…”.

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

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

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

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

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

Your homepage downloads 4.6 MB in 48 requests on a phone: images 2.1 MB (12), scripts 1.2 MB (20) and fonts 759 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images (216 KiB) 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.

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

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

Headings skip levels (h3 → h6), 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.

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

There are 2 <h1> headlines (“Affordable, easily accessible online education” and “Affordable, easily accessible online education”). One clear main headline is easier for people and search engines.

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

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

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

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

The homepage links to 36 pages on nalearning.org and 44 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://nalearning.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://nalearning.org/es, https://nalearning.org/court-required-classes, https://nalearning.org/workplace-compliance-training, https://nalearning.org/secondary-school-and-higher-education-programs and https://nalearning.org/personal-growth-and-development-classes and 5 others all use the title “North American Learning Institute”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nalearning.org/es, https://nalearning.org/about-us, https://nalearning.org/court-required-classes, https://nalearning.org/workplace-compliance-training, https://nalearning.org/secondary-school-and-higher-education-programs and https://nalearning.org/personal-growth-and-development-classes and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 639 words of visible text.

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