Tools & Wizards About Us
cpi.pe screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

cpi.pe

CPI - compañia peruana de estudios de mercado y opinión pública sac

Page Load Speed

938 ms in total

First Response

181 ms

Resources Loaded

624 ms

Page Rendered

133 ms

cpi.pe screenshot

About Website

Visit cpi.pe now to see the best up-to-date CPI content for Peru and also check out these interesting facts you probably never knew about cpi.pe

Compañía peruana dedicada a la investigación, estudios de mercados y opinión pública

Visit cpi.pe

Key Findings

We analyzed Cpi.pe page load time and found that the first response time was 181 ms and then it took 757 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

cpi.pe performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.9 s

89/100

10%

Network Requests Diagram

cpi.pe

181 ms

reset.css

39 ms

estilos.css

83 ms

jquery.js

141 ms

jquery.bxSlider.js

114 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 90% of them (38 requests) were addressed to the original Cpi.pe, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Cpi.pe.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.2 kB (20%)

Content Size

1.1 MB

After Optimization

837.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cpi.pe main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 773.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.6 kB

  • Original 19.6 kB
  • After minification 17.4 kB
  • After compression 5.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 2.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.6 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 20.8 kB

  • Original 773.3 kB
  • After minification 752.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. CPI images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 151.4 kB

  • Original 224.4 kB
  • After minification 186.8 kB
  • After compression 73.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 151.4 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 28.3 kB

  • Original 34.9 kB
  • After minification 28.6 kB
  • After compression 6.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Cpi.pe needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

40

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CPI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cpi.pe

cpi.pe

181 ms

reset.css

reset.css

39 ms

estilos.css

estilos.css

83 ms

jquery.js

jquery.js

141 ms

jquery.bxSlider.js

jquery.bxSlider.js

114 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

90 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

63 ms

jquery.corner.js

jquery.corner.js

67 ms

scripts.js

scripts.js

92 ms

jquery.uniform.min.js

jquery.uniform.min.js

98 ms

uniform.default.css

uniform.default.css

108 ms

jquery.fancybox.js

jquery.fancybox.js

155 ms

jquery.fancybox.css

jquery.fancybox.css

117 ms

ga.js

ga.js

45 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

45 ms

back_home.gif

back_home.gif

36 ms

logo.gif

logo.gif

36 ms

classImgLink.gif

classImgLink.gif

33 ms

twitter.png

twitter.png

34 ms

logofacebook.png

logofacebook.png

34 ms

google_plus.png

google_plus.png

32 ms

ic-chico.gif

ic-chico.gif

60 ms

ic-imprimir.gif

ic-imprimir.gif

61 ms

ic-contacto.gif

ic-contacto.gif

62 ms

back_menu.gif

back_menu.gif

61 ms

banner_opi_nac_201603_02.png

banner_opi_nac_201603_02.png

173 ms

banner_opi_nac_201603_01.png

banner_opi_nac_201603_01.png

191 ms

banner_mreport201601_02.png

banner_mreport201601_02.png

148 ms

banner_mreport201601_01.png

banner_mreport201601_01.png

234 ms

back_tab.png

back_tab.png

93 ms

bullet.gif

bullet.gif

97 ms

back_tab_v2.png

back_tab_v2.png

126 ms

back_tab_v3.png

back_tab_v3.png

130 ms

txt_market2.png

txt_market2.png

163 ms

bt_vermas.png

bt_vermas.png

171 ms

logo_apeim.jpg

logo_apeim.jpg

178 ms

fl_izq.gif

fl_izq.gif

192 ms

fl_der.gif

fl_der.gif

200 ms

bg_Scroll.png

bg_Scroll.png

202 ms

drag_Scroll.png

drag_Scroll.png

207 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

35 ms

__utm.gif

__utm.gif

23 ms

Accessibility Review

cpi.pe accessibility score

97

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

cpi.pe best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cpi.pe SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cpi.pe can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Cpi.pe main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

cpi.pe

Open Graph description is not detected on the main page of CPI. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: