Website review, no card needed

queens.edu logo

queens.edu website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 81 checks

This review found 34 issues worth fixing on queens.edu, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
2.1 s915 msMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.3 s
Jun 6, 20261.6 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.4 s
Aug 15, 20261.1 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Oct 24, 20261.6 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
132 ms98 msMay 16Oct 31127 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026104 ms
May 30, 2026105 ms
Jun 6, 2026104 ms
Jun 13, 2026106 ms
Jun 20, 2026112 ms
Jun 27, 2026111 ms
Jul 4, 2026112 ms
Jul 11, 2026111 ms
Jul 18, 2026102 ms
Jul 25, 2026105 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026107 ms
Aug 22, 2026108 ms
Aug 29, 2026117 ms
Sep 5, 2026119 ms
Sep 12, 2026128 ms
Sep 19, 2026123 ms
Sep 26, 2026117 ms
Oct 3, 2026116 ms
Oct 10, 2026112 ms
Oct 17, 2026118 ms
Oct 24, 2026121 ms
Oct 31, 2026127 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 queens.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix48
  • Reduce unused JavaScript

    1.9 s · 487 KiB

    About 487 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Improve image delivery

    1.3 s · 320 KiB

    6 images could be 320 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1,007 KiB and 1.0 s of main-thread time.

  • Minify JavaScript

    900 ms · 157 KiB

    157 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    300 ms · 260 KiB

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

  • Google Tag Manager adds 448 ms

    448 ms

    Google Tag Manager costs a phone 448 ms of main-thread work and 534 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 CSS

    450 ms · 21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 2.5 s

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

  • 11 long tasks on the main thread

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

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • Render-blocking requests

    50 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 17 ms

    17 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO”.

  • Time to Interactive: 15.0 s

    15.0 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Largest content (LCP) got 50% slower for real visitors

    +50%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Total Blocking Time: 582 ms

    582 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 19% slower for real visitors

    +19%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 130 ms

    130 ms

    Real visitors wait 130 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix68
  • Page weight: 2.5 MB in 100 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 100 requests on a phone: scripts 1.4 MB (31), images 951 KiB (22) and fonts 127 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 2 images far larger than shown

    84 KiB

    2 images are downloaded at several times the size a phone draws them, for example Strategic-townhall-main-sm.jpg at 385 px wide, shown at 72 px. Resized copies would save about 84 KiB.

  • 6 images in older formats

    6 images (472 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.

  • About 0.7 g of CO₂ per visit

    0.72 g

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

Accessibility

2 to fix93
  • 1 button without a name

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8578
  • No meta description

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Welcome to Charlotte's University - Queens University of Charlotte”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • 80 internal links, 14 external

    The homepage links to 80 pages on queens.edu and 14 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Charlotte’s University”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.queens.edu/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.queens.edu/llms.txt (8 KiB, 19 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.queens.edu/admissions, https://www.queens.edu/visit, https://www.queens.edu/request-information, https://www.queens.edu/this-is-queens, https://www.queens.edu/president/mission-vision-values and https://www.queens.edu/president/history and 9 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 47 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

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is 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 “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix72
  • 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 opening hours

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

  • About 615 words of copy

    The homepage carries about 615 words of visible text.

6 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Apply”, “Request Info” and “Learn More”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 mores (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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 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.

  • 35 other companies contacted

    Loading the homepage contacts 35 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 queens.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
Google Tag Manager | Hotjar
Hosting
Fastly

Hiring

Hiring
1 open role
Job board
careers page

Company

Employees
543
Founded
1857
Headquarters
Charlotte

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on queens.edu, including 18 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