Website review, no card needed
nrao.edu website review
Visit site (opens in a new tab)Reviewed 26 October 202648 issues · 95 checks
This review found 48 issues worth fixing on nrao.edu, 20 of them high impact, across 95 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 84 ms |
| May 16, 2026 | 84 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 91 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 93 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 85 ms |
| Sep 26, 2026 | 84 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 86 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 88 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
23.9 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 23.9 s.
Use efficient cache lifetimes
7.2 s · 5.6 MB73 files are served with short cache lifetimes, so returning visitors download them again (5.6 MB).
Improve image delivery
2.4 s · 4.5 MB25 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.
Reduce unused JavaScript
5.9 s · 815 KiBAbout 815 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.
Reduce unused CSS
2.1 s · 358 KiBAbout 358 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Twitter and others), adding 5.3 MB and 863 ms of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 57). Pages that score under 90 lose visitors before the first paint.
Google CDN adds 421 ms
421 msGoogle CDN costs a phone 421 ms of main-thread work and 798 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.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 3.9 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.
Legacy JavaScript
300 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 237 ms
237 msGoogle Tag Manager costs a phone 237 ms of main-thread work and 320 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 33 KiB33 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Document request latency
66 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 32.8 s
32.8 sThe first text or image appears after 32.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 48.0 s
48.0 sYour largest element takes 48.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “This artist's impression of the Gomez’s Hamburger system sh…”.
Speed Index: 32.8 s
32.8 sVisually, the page fills in at 32.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.7 s
48.7 sThe page becomes fully interactive after 48.7 s. Good is under 3.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 249 ms
249 msScripts block taps and scrolling for 249 ms in total while the page loads. Good is under 200 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
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 84 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 82 ms
82 msReal visitors wait 82 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.2 MB in 128 requests
11.2 MBYour homepage downloads 11.2 MB in 128 requests on a phone: images 4.7 MB (38), fonts 3.9 MB (3) and scripts 1.6 MB (42). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (1.6 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.
An image on the first screen is lazy-loaded
C.-Law_GoHam-disk-angled2-585x300.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).
1 image far larger than shown
352 KiB1 image is downloaded at several times the size a phone draws it, for example NSF_Logo.png at 1,722 px wide, shown at 90 px. Resized copies would save about 352 KiB.
3 images below the first screen load straight away
3 images further down the page (207 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.19 g of CO₂e: 382.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
20 tap targets too small
20 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “National Radio Astronomy Observatory – Revealing the Hidden Universe”.
107 internal links, 26 external
The homepage links to 107 pages on nrao.edu and 26 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “The public page for the National Radio Astronomy Observatory (NRAO). Find info related to radio astronomy and the effor…”.
Canonical URL set
The canonical URL is https://public.nrao.edu/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://public.nrao.edu/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://public.nrao.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,185 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://public.nrao.edu/cdl, https://public.nrao.edu/spectrum-management, https://public.nrao.edu/next-generation-radar, https://public.nrao.edu/visit and https://public.nrao.edu/visit/very-large-array have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://public.nrao.edu/telescopes/vla, https://public.nrao.edu/telescopes/alma and https://public.nrao.edu/telescopes/vlba use the same meta description. A description written for each page earns more clicks.
10 pages slow to respond
https://public.nrao.edu/gallery, https://public.nrao.edu/telescopes, https://public.nrao.edu/telescopes/vla, https://public.nrao.edu/telescopes/alma, https://public.nrao.edu/ngvla and https://public.nrao.edu/cdl and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://public.nrao.edu' has been blocked …”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 1,103 words of copy
The homepage carries about 1,103 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Join & Give”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Xandr (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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
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.
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 nrao.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
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Virginia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on nrao.edu, including 22 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.