Website review, no card needed
capeco.edu.pe website review
Visit site (opens in a new tab)Reviewed 18 October 202644 issues · 84 checks
This review found 44 issues worth fixing on capeco.edu.pe, 18 of them high impact, across 84 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
70C- #103,425 of 124,214 reviewed websitesbeats 14%
- #62,690 of 69,818 online storesbeats 8%
- #2,224 of 2,907 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.5 s |
| May 2, 2026 | 4.6 s |
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 178 ms |
| May 2, 2026 | 182 ms |
| May 9, 2026 | 180 ms |
| May 16, 2026 | 169 ms |
| May 23, 2026 | 161 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 160 ms |
| Jun 20, 2026 | 160 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 190 ms |
| Aug 29, 2026 | 199 ms |
| Sep 5, 2026 | 200 ms |
| Sep 12, 2026 | 202 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 196 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
Speed
Render-blocking requests
5.0 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Use efficient cache lifetimes
1.9 s · 2.5 MB122 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Reduce unused CSS
1.9 s · 398 KiBAbout 398 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 24). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
750 ms · 2.1 MB4 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and Facebook and others), adding 1.4 MB and 1.7 s of main-thread time.
Google Tag Manager adds 914 ms
914 msGoogle Tag Manager costs a phone 914 ms of main-thread work and 629 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
678 KiBAbout 678 KiB of JavaScript is downloaded but never used on this page.
Google Maps adds 386 ms
386 msGoogle Maps costs a phone 386 ms of main-thread work and 481 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.
Facebook adds 368 ms
368 msFacebook costs a phone 368 ms of main-thread work and 223 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 346 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
64 KiB64 KiB could be saved by minifying JavaScript.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 29.8 s
29.8 sThe page becomes fully interactive after 29.8 s. Good is under 3.8 s.
Speed Index: 14.2 s
14.2 sVisually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 178 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 7.2 MB in 156 requests
7.2 MBYour homepage downloads 7.2 MB in 156 requests on a phone: images 4.4 MB (14), scripts 1.9 MB (74) and stylesheets 505 KiB (48). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1,017 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 2.0 g of CO₂ per visit
2.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.03 g of CO₂e: 244.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (6 elements)
[role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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
Meta description is long (296 characters)
Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.
18 internal links, 11 external
The homepage links to 18 pages on capeco.edu.pe and 11 external pages.
7 checks passed
One H1 headline
Your main headline reads: “PROGRAMAS ACADÉMICOS”.
Title: 49 characters
Your title is a healthy 49 characters: “Inicio - Instituto CAPECO Líderes en Construcción”.
Canonical URL set
The canonical URL is https://capeco.edu.pe/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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://capeco.edu.pe/sitemap_index.xml.
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://capeco.edu.pe/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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://capeco.edu.pe/cursos-inhouse, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
https://capeco.edu.pe/carrera-profesional-tecnico-construccion-civil-capeco and https://capeco.edu.pe/carrera all use the title “Carrera Técnica Profesional en Construcción Civil - Instituto CAPECO”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://capeco.edu.pe/carrera-profesional-tecnico-construccion-civil-capeco and https://capeco.edu.pe/carrera use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://capeco.edu.pe/carrera, whose canonical is https://capeco.edu.pe/carrera-profesional-tecnico-construccion-civil-capeco. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://capeco.edu.pe/nosotros-2, https://capeco.edu.pe/capecoemplea, https://capeco.edu.pe/transparencia-educativa, https://capeco.edu.pe/matriculas-secuenciales-ii-vi, https://capeco.edu.pe/servicio-atencion-estudiante and https://capeco.edu.pe/experiencia-estudiante and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://capeco.edu.pe/regalementos has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 11 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map 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.
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.
Only about 43 words
The homepage has only about 43 words of visible text; thin pages give Google and first-time buyers little to go on.
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
25 cookies set on arrival
25Opening the homepage sets 25 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 capeco.edu.pe, 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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on capeco.edu.pe, including 22 speed issues, 1 SEO issue and 7 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.