Website review, no card needed

acg.edu logo

acg.edu website review

Visit site (opens in a new tab)Reviewed 25 October 202643 issues · 91 checks

This review found 43 issues worth fixing on acg.edu, 21 of them high impact, across 91 checks. The most urgent: page weight: 49.9 MB in 303 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

Real-visitor load time (LCP)75th percentile, phones
4.6 s3.2 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.6 s
May 16, 20264.0 s
May 23, 20264.3 s
May 30, 20264.4 s
Jun 6, 20264.5 s
Jun 13, 20264.5 s
Jun 20, 20264.4 s
Jun 27, 20264.4 s
Jul 4, 20264.3 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.2 s
Sep 5, 20264.2 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20263.8 s
Oct 10, 20263.6 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
370 ms265 msMay 2Oct 17298 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026277 ms
May 9, 2026299 ms
May 16, 2026322 ms
May 23, 2026335 ms
May 30, 2026339 ms
Jun 6, 2026342 ms
Jun 13, 2026342 ms
Jun 20, 2026343 ms
Jun 27, 2026342 ms
Jul 4, 2026339 ms
Jul 11, 2026336 ms
Jul 18, 2026333 ms
Jul 25, 2026335 ms
Aug 1, 2026336 ms
Aug 8, 2026344 ms
Aug 15, 2026353 ms
Aug 22, 2026355 ms
Aug 29, 2026358 ms
Sep 5, 2026356 ms
Sep 12, 2026353 ms
Sep 19, 2026345 ms
Sep 26, 2026335 ms
Oct 3, 2026321 ms
Oct 10, 2026298 ms
Oct 17, 2026298 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

Full-page screenshot of acg.edu (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. acg.edu at 0.9 s0.9 s
  2. acg.edu at 1.8 s1.8 s
  3. acg.edu at 2.7 s2.7 s
  4. acg.edu at 3.5 s3.5 s
  5. acg.edu at 4.4 s4.4 s
  6. acg.edu at 5.3 s5.3 s
  7. acg.edu at 6.2 s6.2 s
  8. acg.edu at 7.1 s7.1 s

Speed

11 to fix20
  • Render-blocking requests

    4.3 s

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

  • Mobile performance score: 20

    20/100

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

  • Main-thread work: 7.2 s

    A phone's processor spends 7.2 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6,041 HTML elements

    The page has 6,041 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    450 ms · 32.8 MB

    70 images could be 32.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cookiebot and workers.dev and others), adding 1.7 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 711 ms

    711 ms

    Google Tag Manager costs a phone 711 ms of main-thread work and 880 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.

  • Use efficient cache lifetimes

    450 ms · 254 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (254 KiB).

  • Cookiebot adds 478 ms

    478 ms

    Cookiebot costs a phone 478 ms of main-thread work and 165 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.

  • Reduce unused JavaScript

    482 KiB

    About 482 KiB of JavaScript is downloaded but never used on this page.

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

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

  • 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 218 ms

    218 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Speed Index: 66.4 s

    66.4 s

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

  • Time to Interactive: 155.8 s

    155.8 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Founded in 1875, The American College of Greece is the olde…”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Cumulative Layout Shift: 0.404

    0.404

    The layout shifts by 0.404 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 717 ms

    717 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 326 ms

    326 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

2 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 736 ms

    736 ms

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

Images and page weight

3 to fix45
  • Page weight: 49.9 MB in 303 requests

    49.9 MB

    Your homepage downloads 49.9 MB in 303 requests on a phone: images 46.6 MB (104), scripts 2.5 MB (129) and fonts 413 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Bioinnovation-forum-2026-768x576.png weighs 624 KiB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (1,009 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.

  • 2 images below the first screen load straight away

    2 images further down the page (59 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 14.1 g of CO₂ per visit

    14.14 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 6987
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 17 text elements with low contrast

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

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 49 links without text

    49 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.

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 6982
  • No meta description

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“The American College of Greece” and “Welcome”). One clear main headline is easier for people and search engines.

  • 13 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 970 internal links, 53 external

    The homepage links to 970 pages on acg.edu and 53 external pages.

6 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “The American College of Greece”.

  • Canonical URL set

    The canonical URL is https://www.acg.edu/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://www.acg.edu/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.acg.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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,317 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 pages without a meta description

    https://www.acg.edu/virtual-tour, https://www.acg.edu/current-students/myacg-apply-now-register-online, https://www.acg.edu/current-students/student-services/student-life/student-code-of-conduct, https://www.acg.edu/current-students/financial-assistance/undergraduate-financial-assistance, https://www.acg.edu/current-students/financial-assistance/financial-assistance-faqs and https://www.acg.edu/careers-acg and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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

1 to fix97
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • 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.

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

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

  • 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 3,186 words of copy

    The homepage carries about 3,186 words of visible text.

4 checks passed
  • 35 calls to action

    The homepage has 35 calls to action, for example “Apply Now”, “Request Information” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 acg.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 © 2016.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on acg.edu, including 21 speed issues, 4 SEO issues and 3 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