4.9 sec in total
221 ms
4.3 sec
408 ms
Visit cpeig.org now to see the best up-to-date Cpeig content and also check out these interesting facts you probably never knew about cpeig.org
Visit cpeig.orgWe analyzed Cpeig.org page load time and found that the first response time was 221 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cpeig.org performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value6.0 s
13/100
25%
Value6.8 s
35/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value8.3 s
39/100
10%
221 ms
409 ms
480 ms
33 ms
110 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Cpeig.org, 94% (133 requests) were made to Cpeig.gal and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cpeig.gal.
Page size can be reduced by 107.5 kB (6%)
1.9 MB
1.8 MB
In fact, the total size of Cpeig.org main page is 1.9 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 37.8 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 6.6 kB, which is 14% 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 37.8 kB or 81% of the original size.
Potential reduce by 39.6 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. Cpeig images are well optimized though.
Potential reduce by 9.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 20.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. Cpeig.org needs all CSS files to be minified and compressed as it can save up to 20.6 kB or 13% of the original size.
Number of requests can be reduced by 114 (87%)
131
17
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cpeig. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 77 to 1 for CSS and as a result speed up the page load time.
cpeig.org
221 ms
cpeig.org
409 ms
cpeig.gal
480 ms
css
33 ms
normalize.css
110 ms
normalize-fixes.css
208 ms
ajax-progress.module.css
251 ms
align.module.css
251 ms
autocomplete-loading.module.css
293 ms
fieldgroup.module.css
291 ms
container-inline.module.css
294 ms
clearfix.module.css
304 ms
details.module.css
333 ms
hidden.module.css
334 ms
item-list.module.css
389 ms
js.module.css
389 ms
nowrap.module.css
389 ms
position-container.module.css
401 ms
progress.module.css
417 ms
reset-appearance.module.css
415 ms
resize.module.css
485 ms
sticky-header.module.css
486 ms
system-status-counter.css
486 ms
system-status-report-counters.css
497 ms
system-status-report-general-info.css
499 ms
tabledrag.module.css
500 ms
tablesort.module.css
582 ms
tree-child.module.css
585 ms
views.module.css
585 ms
animate.css
610 ms
md-slider.css
582 ms
md-slider-style.css
586 ms
md-slider-principal_md-layers.css
679 ms
onecol.css
664 ms
bootstrap.min.css
798 ms
font-awesome.min.css
684 ms
animate.min.css
668 ms
simple-line-icons.min.css
711 ms
owl.carousel.min.css
747 ms
owl.theme.default.min.css
746 ms
magnific-popup.min.css
674 ms
theme.css
611 ms
theme-elements.css
678 ms
theme-blog.css
588 ms
theme-shop.css
552 ms
settings.css
607 ms
layers.css
626 ms
navigation.css
639 ms
component.css
594 ms
nivo-slider.css
607 ms
default.css
608 ms
default.css
649 ms
h.css
617 ms
custom.css
626 ms
action-links.css
595 ms
breadcrumb.css
612 ms
button.css
608 ms
collapse-processed.css
604 ms
container-inline.css
608 ms
details.css
624 ms
exposed-filters.css
623 ms
field.css
634 ms
form.css
587 ms
icons.css
605 ms
inline-form.css
591 ms
item-list.css
634 ms
link.css
635 ms
links.css
619 ms
menu.css
589 ms
more-link.css
588 ms
pager.css
607 ms
tabledrag.css
629 ms
tableselect.css
605 ms
tablesort.css
579 ms
tabs.css
586 ms
textarea.css
563 ms
ui-dialog.css
576 ms
messages.css
595 ms
progress.css
582 ms
skin-corporate-6.css
606 ms
jquery.min.js
648 ms
jquery.once.min.js
503 ms
drupalSettingsLoader.js
604 ms
es_eZs--OcadvfUGo8D3dYOAEfc-b5lulb3BhytLhq3LbU.js
606 ms
drupal.js
604 ms
drupal.init.js
598 ms
progress.js
568 ms
ajax.js
597 ms
ajax.js
626 ms
modernizr.min.js
635 ms
jquery.appear.min.js
634 ms
jquery.easing.min.js
643 ms
jquery-cookie.min.js
597 ms
bootstrap.min.js
618 ms
common.min.js
641 ms
jquery.validation.min.js
627 ms
jquery.easy-pie-chart.min.js
625 ms
jquery.gmap.min.js
587 ms
jquery.lazyload.min.js
577 ms
jquery.isotope.min.js
649 ms
owl.carousel.min.js
627 ms
jquery.magnific-popup.min.js
613 ms
vide.min.js
615 ms
jquery.themepunch.tools.min.js
719 ms
jquery.themepunch.revolution.min.js
730 ms
jquery.flipshow.min.js
642 ms
jquery.nivo.slider.min.js
639 ms
jquery.validate.min.js
611 ms
view.home.js
613 ms
theme.js
670 ms
custom.js
687 ms
theme.init.js
670 ms
examples.portfolio.js
690 ms
jquery.touchwipe.js
660 ms
modernizr.js
660 ms
jquery.easing.js
656 ms
jquery-migrate-1.2.1.min.js
562 ms
md-slider.js
610 ms
init-md-slider.js
589 ms
logo_cpeig_color.png
710 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
57 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
58 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
90 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
138 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
139 ms
fontawesome-webfont.woff
731 ms
Simple-Line-Icons.ttf
693 ms
01_colexiate_1929x540_modif2.jpg
1274 ms
Imaxe%20do%20video%20corporativo%20do%20centro%20%E2%80%98CiTIUS%20%E2%80%93%20Tecnoloxias%20Intelixentes%20en%20cada%20paso%E2%80%99.jpg
1038 ms
proteccion_datos.jpg
877 ms
Angel%20Vi%C3%B1a.jpg
1485 ms
00_ccii.png
655 ms
01b_sabadell.png
692 ms
02_psn.png
718 ms
03_lacaixa.png
767 ms
04_hotel_puerta_camino.png
789 ms
05_barcelo.png
838 ms
06_cntg.png
846 ms
07_voldix.png
885 ms
08_OSI.png
937 ms
icon-search.png
862 ms
cpeig.org accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cpeig.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cpeig.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cpeig.org 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 Cpeig.org 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.
cpeig.org
Open Graph description is not detected on the main page of Cpeig. 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: