Website review, no card needed
pccr.edu.ph website review
Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 75 checks
This review found 32 issues worth fixing on pccr.edu.ph, 9 of them high impact, across 75 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 27, 2026 | 2.2 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Sep 19, 2026 | 3.8 s |
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
Speed
Render-blocking requests
1.5 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Use efficient cache lifetimes
900 ms · 590 KiB33 files are served with short cache lifetimes, so returning visitors download them again (590 KiB).
Mobile performance score: 75
75/100Your mobile performance score is 75 (desktop: 80). Pages that score under 90 lose visitors before the first paint.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Improve image delivery
300 ms · 120 KiB2 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
150 ms · 28 KiBAbout 28 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 110 ms. During a long task the page ignores taps.
Reduce unused JavaScript
93 KiBAbout 93 KiB of JavaScript is downloaded but never used on this page.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 163 KiB and 0 ms of main-thread time.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 257 ms of it running JavaScript. That is comfortably low.
Server response: 204 ms
204 msYour server sent the HTML in 204 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.2 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PCCR | For the Good of the Public and Country”. Most of its time is resource load delay (2.1 s).
Time to Interactive: 4.9 s
4.9 sThe page becomes fully interactive after 4.9 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
98 KiB1 image is downloaded at several times the size a phone draws it, for example pccr-logo-eagle.png at 2,218 px wide, shown at 58 px. Resized copies would save about 98 KiB.
1 image in older formats
1 image (99 KiB) is 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.2 g of CO₂ per visit
0.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.22 g of CO₂e: 26.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 789 KiB in 40 requests
789 KiBYour homepage downloads 789 KiB in 40 requests on a phone: scripts 262 KiB (16), fonts 249 KiB (5) and images 192 KiB (7). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (21 elements)
Headings should not be empty: 21 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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 XML sitemap
No XML sitemap at https://pccr.edu.ph/sitemap.xml, so Google discovers your pages only by following links.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
50 internal links, 1 external
The homepage links to 50 pages on pccr.edu.ph and 1 external page.
3 checks passed
Title: 40 characters
Your title is a healthy 40 characters: “PCCR | Philippine College of Criminology”.
Canonical URL set
The canonical URL is https://pccr.edu.ph/.
robots.txt in place
robots.txt is in place.
AI search readiness
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://pccr.edu.ph/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 (1,044 words), so crawlers that don't run JavaScript still read it.
Other pages
13 linked pages hidden from search
https://pccr.edu.ph/contact-us, https://pccr.edu.ph/about/community-extension-and-services, https://pccr.edu.ph/about/the-research-center, https://pccr.edu.ph/about/faqs, https://pccr.edu.ph/about/privacy-policy and https://pccr.edu.ph/academic-programs/college-of-criminal-justice and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
13 pages without a meta description
https://pccr.edu.ph/contact-us, https://pccr.edu.ph/about/community-extension-and-services, https://pccr.edu.ph/about/the-research-center, https://pccr.edu.ph/about/faqs, https://pccr.edu.ph/about/privacy-policy and https://pccr.edu.ph/academic-programs/college-of-criminal-justice and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://pccr.edu.ph/events has no <h1> headline, so visitors and search engines get no clear main topic.
11 pages slow to respond
https://pccr.edu.ph/contact-us, https://pccr.edu.ph/about/community-extension-and-services, https://pccr.edu.ph/about/the-research-center, https://pccr.edu.ph/about/faqs, https://pccr.edu.ph/about/privacy-policy and https://pccr.edu.ph/academic-programs/college-of-criminal-justice and 5 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
4 checks passed
Linked pages load
13 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
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
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 843 words of copy
The homepage carries about 843 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Download Forms”.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 1 trust badge.
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
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 pccr.edu.ph, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on pccr.edu.ph, including 10 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.