Programmable

Website review, no card needed

sae.edu logo

sae.edu website review

Visit site (opens in a new tab)Reviewed 30 October 202620 issues · 66 checks

This review found 20 issues worth fixing on sae.edu, 7 of them high impact, across 66 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

84B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.5 s3.9 sMay 9Oct 244.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.3 s
May 23, 20264.3 s
May 30, 20264.3 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.3 s
Jun 27, 20264.3 s
Jul 4, 20264.4 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.2 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20264.1 s
Oct 24, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
229 ms212 msMay 9Oct 24225 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026214 ms
May 16, 2026220 ms
May 23, 2026221 ms
May 30, 2026222 ms
Jun 6, 2026220 ms
Jun 13, 2026214 ms
Jun 20, 2026217 ms
Jun 27, 2026218 ms
Jul 4, 2026221 ms
Jul 11, 2026223 ms
Jul 18, 2026222 ms
Jul 25, 2026222 ms
Aug 1, 2026223 ms
Aug 8, 2026224 ms
Aug 15, 2026225 ms
Aug 22, 2026224 ms
Aug 29, 2026224 ms
Sep 5, 2026223 ms
Sep 12, 2026221 ms
Sep 19, 2026221 ms
Sep 26, 2026221 ms
Oct 3, 2026222 ms
Oct 10, 2026225 ms
Oct 17, 2026227 ms
Oct 24, 2026225 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

www.sae.edu (opens in a new tab)
Full-page screenshot of sae.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sae.edu at 0.4 s0.4 s
  2. sae.edu at 0.8 s0.8 s
  3. sae.edu at 1.1 s1.1 s
  4. sae.edu at 1.5 s1.5 s
  5. sae.edu at 1.9 s1.9 s
  6. sae.edu at 2.3 s2.3 s
  7. sae.edu at 2.6 s2.6 s
  8. sae.edu at 3.0 s3.0 s

Speed

1 to fix99

  • Render-blocking requests

    1.1 s

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

  • Use efficient cache lifetimes

    22 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (22 KiB).

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (geojs.io), adding 1 KiB and 0 ms of main-thread time.

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 37 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100

  • Fails Core Web Vitals for real visitors

    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.

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 214 ms to 225 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

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

10 checks passed

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the element shown below.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

100

  • About 0.02 g of CO₂ per visit

    0.02 g

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

1 checks passed

  • Page weight: 75 KiB in 8 requests

    75 KiB

    Your homepage downloads 75 KiB in 8 requests on a phone: scripts 70 KiB (4), HTML 4 KiB (1) and other files 1 KiB (3). That is a lean page.

Accessibility

5 to fixGoogle 7181

  • lang attribute must have a valid value (2 elements)

    lang attribute must have a valid value: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (2 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed

  • 13 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 13 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10089

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    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

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

  • No X (Twitter) card tag

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

  • 10 internal links, 10 external

    The homepage links to 10 pages on sae.edu and 10 external pages.

5 checks passed

  • Meta description: 105 characters

    Your meta description is 105 characters: “Explore SAE's creative media courses worldwide. Select your region to find courses and campuses near you.”.

  • One H1 headline

    Your main headline reads: “Choose your region”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “SAE Institute - Choose your region”.

  • Structured data in place

    Structured data found: WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83

  • No Organization structured data

    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.

  • No llms.txt

    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.

1 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix85

  • 2 pages without a meta description

    /fra and /che have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example /aut, whose canonical is /aut/sae-home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    /fra and /esp have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

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

4 checks passed

  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    20 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33

  • No call to action on the first screen

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

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

  • Only about 47 words

    The homepage has only about 47 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

1 checks passed

  • Analytics in place

    Analytics detected: Matomo.

Privacy and tracking

  • No consent tool detected

    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.

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at sae.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Analytics
Matomo
Hosting
AWS

Company

Employees
130
Founded
1976
Headquarters
Emeryville

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on sae.edu, including 3 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25