Website review, no card needed
anc.edu website review
Visit site (opens in a new tab)Reviewed 30 October 202629 issues · 84 checks
This review found 29 issues worth fixing on anc.edu, 6 of them high impact, across 84 checks. The most urgent: wix adds 1.4 s. 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
83BClosest competitors among Wix websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 92 ms |
| May 16, 2026 | 83 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 76 ms |
| Jun 6, 2026 | 75 ms |
| Jun 13, 2026 | 77 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 75 ms |
| Jul 4, 2026 | 75 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 77 ms |
| Aug 15, 2026 | 75 ms |
| Aug 22, 2026 | 76 ms |
| Aug 29, 2026 | 76 ms |
| Sep 5, 2026 | 76 ms |
| Sep 12, 2026 | 76 ms |
| Sep 19, 2026 | 75 ms |
| Sep 26, 2026 | 71 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 72 ms |
| Oct 17, 2026 | 71 ms |
| Oct 24, 2026 | 72 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
Speed
Wix adds 1.4 s
1.4 sWix costs a phone 1.4 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (Wix, Sentry and Other Google APIs/SDKs and others), adding 2.3 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
600 ms · 513 KiBAbout 513 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
550 ms · 259 KiB6 images could be 259 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Render-blocking requests
750 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.
Duplicated JavaScript
150 ms · 36 KiB36 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.
Reduce unused CSS
136 KiBAbout 136 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
47 KiB47 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
17 KiB1 file is served with short cache lifetimes, so returning visitors download them again (17 KiB).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Clock tower stands on lush green lawn under a bright blue s…”.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 81 ms
81 msReal visitors wait 81 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 527 ms
527 msReal visitors wait 527 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 92 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 142 ms
142 msScripts block the page for only 142 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 257 requests
3.6 MBYour homepage downloads 3.6 MB in 257 requests on a phone: scripts 1.4 MB (118), other files 1.1 MB (103) and images 465 KiB (21). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
30d59a_2d831e6df52049d2aacb8bafbc5024c4~mv2.jpg 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).
About 1.0 g of CO₂ per visit
1.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
5 H1 headlines
There are 5 <h1> headlines (“READY TO TAKE A TOUR?”, “WE CARE ABOUT YOU!” and “MOST AFFORDABLE!”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
39 internal links, 21 external
The homepage links to 39 pages on anc.edu and 21 external pages.
4 checks passed
Title: 36 characters
Your title is a healthy 36 characters: “Home | Arkansas Northeastern College”.
Canonical URL set
The canonical URL is https://www.anc.edu/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.anc.edu/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (597 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.anc.edu/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://www.anc.edu/az, https://www.anc.edu/academics, https://www.anc.edu/admissions, https://www.anc.edu/advising, https://www.anc.edu/earlycollegeprogram and https://www.anc.edu/technicalcenter and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.anc.edu/academics, https://www.anc.edu/facstaff and https://www.anc.edu/donate have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.anc.edu/calendar has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
5 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.
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
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 227 words
The homepage has only about 227 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Transcript Request”.
4 calls to action
The homepage has 4 calls to action, for example “Transcript Request”, “Apply Now” and “Register”.
1 short form
A short form (1 field at most) is right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 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.
6 other companies contacted
Loading the homepage contacts 6 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 anc.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- Wix
- Framework
- React
- Hosting
- Wix
Hiring
- Hiring
- 48 open roles
- Teams
- Project Management (24), Superintendent (10), Business Development (6), Interns/Co-ops (4)
- Job board
- greenhouse
- Careers page
- www.anc.edu/jobs (opens in a new tab)
Company
- Founded
- 1975
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on anc.edu, including 12 speed issues, 3 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.