Website review, no card needed

thrivescholars.org logo

thrivescholars.org website review

Visit site (opens in a new tab)Reviewed 2 November 202626 issues · 82 checks

This review found 26 issues worth fixing on thrivescholars.org, 4 of them high impact, across 82 checks. The most urgent: render-blocking 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
1.8 s1.0 sJul 4Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.7 s
Jul 11, 20261.5 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
114 ms96 msJul 11Oct 3198 ms
Show as table
DateReal-visitor tap response (INP)
Jul 11, 2026100 ms
Jul 18, 2026104 ms
Jul 25, 2026109 ms
Aug 1, 2026105 ms
Aug 8, 2026111 ms
Aug 15, 2026108 ms
Aug 22, 2026111 ms
Aug 29, 2026112 ms
Sep 5, 2026111 ms
Sep 12, 2026108 ms
Sep 19, 2026103 ms
Sep 26, 2026105 ms
Oct 3, 2026105 ms
Oct 10, 2026104 ms
Oct 17, 2026105 ms
Oct 24, 2026102 ms
Oct 31, 202698 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 thrivescholars.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thrivescholars.org at 0.4 s0.4 s
  2. thrivescholars.org at 0.8 s0.8 s
  3. thrivescholars.org at 1.2 s1.2 s
  4. thrivescholars.org at 1.5 s1.5 s
  5. thrivescholars.org at 1.9 s1.9 s
  6. thrivescholars.org at 2.3 s2.3 s
  7. thrivescholars.org at 2.7 s2.7 s
  8. thrivescholars.org at 3.1 s3.1 s

Speed

7 to fix88
  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    1.7 MB

    8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 88

    88/100

    Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and LinkedIn Ads and others), adding 799 KiB and 521 ms of main-thread time.

  • Reduce unused CSS

    440 ms · 106 KiB

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

  • Google Tag Manager adds 473 ms

    473 ms

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

    406 KiB

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

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 151 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).

  • Use efficient cache lifetimes

    10 KiB

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

  • Minify CSS

    10 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 512 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 10.2 s

    10.2 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 25 images without width and height

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    -2%

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

10 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.4 s

    1.4 s

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

  • Real-user INP: 106 ms

    106 ms

    Real visitors wait 106 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.3 s

    1.3 s

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

  • Real-user TTFB: 718 ms

    718 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Total Blocking Time: 165 ms

    165 ms

    Scripts block the page for only 165 ms while loading. Good is under 200 ms.

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Every year, thousands of talented students have the drive a…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.6 MB in 90 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 90 requests on a phone: images 2.2 MB (37), scripts 885 KiB (28) and fonts 375 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    364 KiB

    2 images are downloaded at several times the size a phone draws them, for example mentor-library-session.jpg at 1,920 px wide, shown at 276 px. Resized copies would save about 364 KiB.

  • 2 images in older formats

    2 images (463 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 1.0 g of CO₂ per visit

    1.03 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9296
  • 6 text elements with low contrast

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 57 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is short (26 characters)

    Your title is only 26 characters: “Homepage - Thrive Scholars”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Helping Extraordinary Scholars Succeed” and “25 years of unlocking opportunity”). One clear main headline is easier for people and search engines.

  • 61 internal links, 9 external

    The homepage links to 61 pages on thrivescholars.org and 9 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Thrive Scholars supports students from high school through college and into an early career. driving accessability to t…”.

  • Canonical URL set

    The canonical URL is https://thrivescholars.org/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://thrivescholars.org/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: 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 (726 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://thrivescholars.org/llms.txt (3 KiB, 26 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://thrivescholars.org/scholars/program/journey, https://thrivescholars.org/scholars/program/academies, https://thrivescholars.org/scholars/program/admissions, https://thrivescholars.org/scholars/program/college-success, https://thrivescholars.org/scholars/program/careers and https://thrivescholars.org/scholars/program/mentorship and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://thrivescholars.org/scholars, https://thrivescholars.org/scholars/program/academies, https://thrivescholars.org/scholars/program/admissions, https://thrivescholars.org/scholars/program/college-success, https://thrivescholars.org/scholars/program/careers and https://thrivescholars.org/scholars/program/mentorship and 6 others have 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 42 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://thrivescholars.org' has been b…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 41 testimonial or review blocks. 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 opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 628 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Apply”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “How to Apply”, “Apply” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager and 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 LinkedIn Insight (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.

  • 8 cookies set on arrival

    8

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 thrivescholars.org, 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 Analytics | Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
2 open roles
Teams
Career Pathways (1), College Success (1)
Job board
rippling

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on thrivescholars.org, including 11 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

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