Website review, no card needed

pibetaphi.org logo

pibetaphi.org website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 79 checks

This review found 31 issues worth fixing on pibetaphi.org, 8 of them high impact, across 79 checks. The most urgent: page weight: 20.4 MB in 93 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
3.5 s2.3 sJul 18Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.8 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
103 ms90 msJul 18Oct 2494 ms
Show as table
DateReal-visitor tap response (INP)
Jul 18, 202695 ms
Jul 25, 202691 ms
Aug 1, 202692 ms
Aug 8, 202692 ms
Aug 15, 202691 ms
Aug 22, 202694 ms
Aug 29, 202693 ms
Sep 5, 202696 ms
Sep 12, 202697 ms
Sep 19, 202696 ms
Sep 26, 2026101 ms
Oct 3, 202695 ms
Oct 10, 202694 ms
Oct 17, 202694 ms
Oct 24, 202694 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 pibetaphi.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix81
  • Render-blocking requests

    1.1 s

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

  • Use efficient cache lifetimes

    900 ms · 17.6 MB

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

  • Improve image delivery

    15.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, curator.io and JSDelivr CDN and others), adding 19.7 MB and 570 ms of main-thread time.

  • Azure Web Services adds 0 ms

    0 ms

    Azure Web Services costs a phone 0 ms of main-thread work and 19.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.

  • Mobile performance score: 81

    81/100

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

  • Reduce unused CSS

    580 ms · 117 KiB

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

  • Google Tag Manager adds 351 ms

    351 ms

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

    263 KiB

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

  • Main-thread work: 2.2 s

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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: 6 ms

    6 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Time to Interactive: 43.9 s

    43.9 s

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

  • Speed Index: 14.4 s

    14.4 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

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

    +33%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Connect. Serve. Shine.”. Most of its time is element render delay (2.3 s).

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

6 checks passed
  • Real-user INP: 95 ms

    95 ms

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

  • Real-user TTFB: 764 ms

    764 ms

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

  • Total Blocking Time: 139 ms

    139 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 20.4 MB in 93 requests

    20.4 MB

    Your homepage downloads 20.4 MB in 93 requests on a phone: images 19.3 MB (35), scripts 697 KiB (31) and fonts 205 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 16.8 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    11.2 MB

    18 images are downloaded at several times the size a phone draws them, for example Homepage-CB3-tab1-image2.jpg at 4,912 px wide, shown at 200 px. Resized copies would save about 11.2 MB.

  • 24 images in older formats

    24 images (19.1 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.

  • 21 images below the first screen load straight away

    21 images further down the page (15.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.8 g of CO₂ per visit

    5.77 g

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

Accessibility

2 to fixGoogle 9697
  • 4 text elements with low contrast

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

  • 1 form field without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

2 to fixGoogle 7795
  • 7 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 67 internal links, 13 external

    The homepage links to 67 pages on pibetaphi.org and 13 external pages.

8 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Discover Pi Beta Phi, where women connect through sincere friendships, serve with purpose and shine as confident, value…”.

  • One H1 headline

    Your main headline reads: “Connect. Serve. Shine.”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Pi Beta Phi | Connect. Serve. Shine.”.

  • Canonical URL set

    The canonical URL is https://pibetaphi.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://pibetaphi.org/sitemap_index.xml.

AI search readiness

100
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 (740 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without an H1

    https://pibetaphi.org/history and https://pibetaphi.org/our-sisterhood have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://pibetaphi.org/notable-pi-phis, https://pibetaphi.org/our-sisterhood and https://pibetaphi.org/our-sisterhood/friendship-traditions took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Looks like your website URL has changed. To ensure the proper functioning of your banner, update the re…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • Thin social proof

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

  • 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 form on the homepage

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

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

    The homepage carries about 483 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: “Join Pi Beta Phi”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop”, “Contact” and “Join Pi Beta Phi”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

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 (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 10 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 pibetaphi.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on pibetaphi.org, including 18 speed issues, 2 SEO issues and 1 conversion gap. 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