Website review, no card needed
pepcleve.org website review
Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 82 checks
This review found 27 issues worth fixing on pepcleve.org, 6 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 92 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 87 ms |
| Nov 14, 2026 | 86 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.7 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Improve image delivery
150 ms · 3.8 MB9 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
710 ms · 92 KiBAbout 92 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 710 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Adobe TypeKit and others), adding 4.9 MB and 124 ms of main-thread time.
b-cdn.net adds 0 ms
0 msb-cdn.net costs a phone 0 ms of main-thread work and 4.5 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.
Reduce unused CSS
150 ms · 22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
32 KiB5 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).
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 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 110 ms of it running JavaScript. That is comfortably low.
Server response: 55 ms
55 msYour server sent the HTML in 55 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
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) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 92 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 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 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 14 ms
14 msScripts block the page for only 14 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.3 MB in 35 requests
5.3 MBYour homepage downloads 5.3 MB in 35 requests on a phone: images 4.8 MB (23), scripts 196 KiB (3) and fonts 178 KiB (4). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
10 images far larger than shown
3.3 MB10 images are downloaded at several times the size a phone draws them, for example plushieswebsiteimage2.png at 1,600 px wide, shown at 92 px. Resized copies would save about 3.3 MB.
16 images in older formats
16 images (4.3 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.
10 images below the first screen load straight away
10 images further down the page (3.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 179.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (9 elements).
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
148 internal links, 12 external
The homepage links to 148 pages on pepcleve.org and 12 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Positive Education Program serves children with developmental trauma, mental health challenges, and autism throughout G…”.
One H1 headline
Your main headline reads: “Supporting young people to overcome and thrive.”.
Title: 39 characters
Your title is a healthy 39 characters: “Home | Positive Education Program (PEP)”.
Structured data in place
Structured data found: Organization 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://www.pepcleve.org/sitemap.xml.
AI search readiness
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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,007 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.pepcleve.org/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.pepcleve.org/what-we-do/services/community-support and https://www.pepcleve.org/what-we-do/services/autism all use the title “Services | Positive Education Program (PEP)”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages share a meta description
https://www.pepcleve.org/ask-us, https://www.pepcleve.org/support-us, https://www.pepcleve.org/who-we-are/staff-leadership, https://www.pepcleve.org/who-we-are/board-leadership, https://www.pepcleve.org/who-we-are/news and https://www.pepcleve.org/what-we-do/services/community-support and 1 other use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.pepcleve.org/work-with-us, whose canonical is https://www.pepcleve.org/work-with-us/overview. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
21 small tap targets
21 of 90 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 1 customer or partner logo. 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.
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 871 words of copy
The homepage carries about 871 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Learn More” and “2025-2026 Training Schedule”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
6 other companies contacted
Loading the homepage contacts 6 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 pepcleve.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Liquid Web
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on pepcleve.org, including 11 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.