Website review, no card needed

cameron.edu logo

cameron.edu website review

Visit site (opens in a new tab)Reviewed 30 October 202637 issues · 80 checks

This review found 37 issues worth fixing on cameron.edu, 16 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
1.2 s973 msMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
90 ms70 msMay 9Oct 2488 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202679 ms
May 16, 202676 ms
May 23, 202676 ms
May 30, 202675 ms
Jun 6, 202672 ms
Jun 13, 202675 ms
Jun 20, 202673 ms
Jun 27, 202673 ms
Jul 4, 202674 ms
Jul 11, 202675 ms
Jul 18, 202675 ms
Jul 25, 202675 ms
Aug 1, 202674 ms
Aug 8, 202673 ms
Aug 15, 202676 ms
Aug 22, 202677 ms
Aug 29, 202679 ms
Sep 5, 202682 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202684 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202687 ms
Oct 24, 202688 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 cameron.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cameron.edu at 1.4 s1.4 s
  2. cameron.edu at 2.8 s2.8 s
  3. cameron.edu at 4.2 s4.2 s
  4. cameron.edu at 5.6 s5.6 s
  5. cameron.edu at 7.0 s7.0 s
  6. cameron.edu at 8.4 s8.4 s
  7. cameron.edu at 9.7 s9.7 s
  8. cameron.edu at 11.1 s11.1 s

Speed

12 to fix23
  • Use efficient cache lifetimes

    13.8 s · 8.5 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (8.5 MB).

  • Improve image delivery

    5.2 s · 1.4 MB

    9 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.2 s faster on a phone.

  • Reduce unused JavaScript

    3.1 s · 620 KiB

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

  • Font display

    3.0 s

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

  • YouTube adds 1.1 s

    1.1 s

    YouTube costs a phone 1.1 s of main-thread work and 986 KiB 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.

  • Mobile performance score: 23

    23/100

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

  • Main-thread work: 5.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and The Trade Desk and others), adding 2.4 MB and 1.5 s of main-thread time.

  • Reduce unused CSS

    900 ms · 193 KiB

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

  • 14 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Adobe TypeKit adds 39 ms

    39 ms

    Adobe TypeKit costs a phone 39 ms of main-thread work and 1.2 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.

  • Minify CSS

    150 ms · 14 KiB

    14 KiB could be saved by minifying CSS.

  • 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: 3 ms

    3 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 33.0 s

    33.0 s

    Your largest element takes 33.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bentley Gardens”.

  • Time to Interactive: 42.0 s

    42.0 s

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

  • Speed Index: 13.4 s

    13.4 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.154

    0.154

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

  • 11 images without width and height

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

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

    +13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 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

    -3%

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

6 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.5 s

    1.5 s

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

  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 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.2 s

    1.2 s

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

  • Real-user TTFB: 610 ms

    610 ms

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

Images and page weight

5 to fix18
  • Page weight: 10.8 MB in 95 requests

    10.8 MB

    Your homepage downloads 10.8 MB in 95 requests on a phone: images 7.1 MB (32), scripts 2.0 MB (11) and fonts 1.5 MB (30). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    491 KiB

    2 images are downloaded at several times the size a phone draws them, for example home_page_header_copy2.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 491 KiB.

  • 20 images in older formats

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

  • 3 images below the first screen load straight away

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

  • About 3.1 g of CO₂ per visit

    3.07 g

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

Accessibility

1 to fixGoogle 10099
  • 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.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8374
  • No meta description

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Life On Campus”). One clear main headline is easier for people and search engines.

  • 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 X (Twitter) card tag

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

  • 121 internal links, 11 external

    The homepage links to 121 pages on cameron.edu and 11 external pages.

3 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “Cameron University | Cameron University”.

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

AI search readiness

1 to fix88
  • 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 https://www.cameron.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 (647 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.cameron.edu/campus-map, https://www.cameron.edu/duncan, https://www.cameron.edu/email, https://www.cameron.edu/its, https://www.cameron.edu/university-calendar and https://www.cameron.edu/press-releases and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.cameron.edu/campus-map has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 to fixGoogle 7797
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 423 words of copy

    The homepage carries about 423 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START YOUR JOURNEY”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Course Schedule”, “Schedule a Tour” and “Start Your Journey”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and The Trade Desk (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

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 cameron.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on cameron.edu, including 19 speed issues, 5 SEO issues and 2 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