Website review, no card needed

cip.org.pe logo

cip.org.pe website review

Visit site (opens in a new tab)Reviewed 18 November 202656 issues · 95 checks

This review found 56 issues worth fixing on cip.org.pe, 28 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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
4.2 s3.6 sMay 30Nov 144.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.9 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.1 s
Oct 31, 20264.1 s
Nov 7, 20264.1 s
Nov 14, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
138 ms120 msMay 30Nov 14131 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026128 ms
Jun 6, 2026134 ms
Jun 13, 2026136 ms
Jun 20, 2026133 ms
Jun 27, 2026132 ms
Jul 4, 2026131 ms
Jul 11, 2026130 ms
Jul 18, 2026135 ms
Jul 25, 2026133 ms
Aug 1, 2026134 ms
Aug 8, 2026133 ms
Aug 15, 2026127 ms
Aug 22, 2026122 ms
Aug 29, 2026122 ms
Sep 5, 2026122 ms
Sep 12, 2026124 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026127 ms
Oct 10, 2026128 ms
Oct 17, 2026127 ms
Oct 24, 2026130 ms
Oct 31, 2026131 ms
Nov 7, 2026130 ms
Nov 14, 2026131 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 cip.org.pe (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cip.org.pe at 1.4 s1.4 s
  2. cip.org.pe at 2.9 s2.9 s
  3. cip.org.pe at 4.3 s4.3 s
  4. cip.org.pe at 5.8 s5.8 s
  5. cip.org.pe at 7.2 s7.2 s
  6. cip.org.pe at 8.6 s8.6 s
  7. cip.org.pe at 10.1 s10.1 s
  8. cip.org.pe at 11.5 s11.5 s

Speed

14 to fix40
  • Use efficient cache lifetimes

    10.3 s · 13.7 MB

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

  • Render-blocking requests

    14.7 s

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

  • Avoid multiple page redirects

    4.4 s

    The page goes through 1 redirect before it starts loading, costing about 4.4 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    3.6 s · 327 KiB

    About 327 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Font display

    3.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

  • Reduce unused CSS

    2.2 s · 226 KiB

    About 226 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.2 s faster on a phone.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.5 s

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

  • Improve image delivery

    800 ms · 3.0 MB

    20 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Analytics and others), adding 1.1 MB and 583 ms of main-thread time.

  • 14 long tasks on the main thread

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

  • Google Tag Manager adds 318 ms

    318 ms

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

  • Google Maps adds 162 ms

    162 ms

    Google Maps costs a phone 162 ms of main-thread work and 788 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.

  • 2,238 HTML elements

    The page has 2,238 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

  • Minify CSS

    10 ms · 6 KiB

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

1 checks passed
  • Server response: 277 ms

    277 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.5 s

    5.5 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • First Contentful Paint: 13.5 s

    13.5 s

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

  • Largest Contentful Paint: 48.3 s

    48.3 s

    Your largest element takes 48.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Comunicado oficial CIP del 02 de noviembre de 2026”.

  • Speed Index: 17.2 s

    17.2 s

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

  • Time to Interactive: 50.3 s

    50.3 s

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

  • Total Blocking Time: 602 ms

    602 ms

    Scripts block taps and scrolling for 602 ms in total while the page loads. Good is under 200 ms.

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user INP: 144 ms

    144 ms

    Real visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix18
  • Page weight: 14.2 MB in 399 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 399 requests on a phone: images 11.6 MB (208), scripts 1.6 MB (102) and stylesheets 647 KiB (74). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    boton-cenei-inicio.jpg weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.8 MB

    6 images are downloaded at several times the size a phone draws them, for example boton-cenei-inicio.jpg at 5,121 px wide, shown at 348 px. Resized copies would save about 1.8 MB.

  • 40 images in older formats

    40 images (6.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.

  • 26 images below the first screen load straight away

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

  • About 4.0 g of CO₂ per visit

    4.04 g

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

Accessibility

14 to fixGoogle 7384
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 10 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 57 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 7779
  • 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.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 198 internal links, 48 external

    The homepage links to 198 pages on cip.org.pe and 48 external pages.

5 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “Inicio - Colegio de Ingenieros del Perú”.

  • Canonical URL set

    The canonical URL is https://www.cip.org.pe/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.cip.org.pe/comites-tecnicos declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.cip.org.pe/comites-tecnicos all use the title “Inicio - Colegio de Ingenieros del Perú”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.cip.org.pe/servicios-cip, https://www.cip.org.pe/tne, https://www.cip.org.pe/antisoborno, https://www.cip.org.pe/ibi, https://www.cip.org.pe/sistema-integrado-de-gestion-del-cipcn and https://www.cip.org.pe/iepi and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.cip.org.pe/antisoborno, https://www.cip.org.pe/ibi, https://www.cip.org.pe/iepi, https://www.cip.org.pe/comites-tecnicos, https://www.cip.org.pe/mujer-ingeniero and https://www.cip.org.pe/joven-ingeniero 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 105 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6987
  • 16 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 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 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 317 words of copy

    The homepage carries about 317 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 cip.org.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
Analytics
Google Analytics
Hosting
Oracle Cloud

Company

Founded
1962

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on cip.org.pe, including 24 speed issues, 3 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

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