3.5 sec in total
951 ms
2 sec
592 ms
Welcome to codigoverde.com homepage info - get ready to check Codigo Verde best content for Mexico right away, or after learning these important things about codigoverde.com
Consultoría especializada en Seguridad de la Información desde el 2009. Certificaciones en Ciberseguridad de CompTIA, EC-Council e ISC2.
Visit codigoverde.comWe analyzed Codigoverde.com page load time and found that the first response time was 951 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
codigoverde.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value13.7 s
0/100
25%
Value18.1 s
0/100
10%
Value25,250 ms
0/100
30%
Value0.305
38/100
15%
Value36.2 s
0/100
10%
951 ms
81 ms
70 ms
52 ms
101 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Codigoverde.com, 42% (36 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (951 ms) belongs to the original domain Codigoverde.com.
Page size can be reduced by 298.9 kB (37%)
802.7 kB
503.8 kB
In fact, the total size of Codigoverde.com main page is 802.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 337.3 kB which makes up the majority of the site volume.
Potential reduce by 200.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 200.3 kB or 85% of the original size.
Potential reduce by 41 B
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. Codigo Verde images are well optimized though.
Potential reduce by 97.3 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 97.3 kB or 47% of the original size.
Potential reduce by 1.3 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. Codigoverde.com has all CSS files already compressed.
Number of requests can be reduced by 18 (38%)
47
29
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codigo Verde. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
codigoverde.com
951 ms
js
81 ms
style.css
70 ms
css
52 ms
frontend-gtag.min.js
101 ms
jquery.min.js
63 ms
jquery-migrate.min.js
54 ms
js
154 ms
js
153 ms
mc-validate.js
153 ms
snippet.js
151 ms
idle-timer.min.js
46 ms
custom.js
141 ms
scripts.min.js
149 ms
smoothscroll.js
140 ms
jquery.fitvids.js
88 ms
common.js
87 ms
analytics.js
340 ms
js
415 ms
js
414 ms
c%C3%B3digoverde-imagotipo-transparente-fondos-oscuros.svg
718 ms
home-sider-1-2.jpg
389 ms
home-banner-1.jpg
382 ms
home-banner-2.jpg
383 ms
logo-comptia.svg
383 ms
ecouncil-logo.png
382 ms
certificadora-ics-2.svg
548 ms
co%CC%81digo-verde-logotipo-ceh_gray.svg
550 ms
ecsa_gray_logo.svg
552 ms
co%CC%81digo-verde-logotipo-lpt.svg
557 ms
co%CC%81digo-verde-logotipo-CCISO_gray.svg
552 ms
co%CC%81digo-verde-logotipo-ccisp.svg
696 ms
co%CC%81digo-verde-logotipo-ecih.svg
590 ms
PCME-big-1-gray.png
589 ms
cissp_gray_logo.png
592 ms
cisa_gray_logo.png
588 ms
cism_gray_logo.png
705 ms
CRISC-Vertical-gray-1.jpg
724 ms
comptia_casp_gray_logo.png
705 ms
comptia_security_gray_logo.png
708 ms
comptia_network_gray_logo.png
710 ms
home-mock-2.jpg
719 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
381 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
550 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
579 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
587 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
582 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
587 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
582 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
578 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
682 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
688 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
684 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
687 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
684 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
686 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
690 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
695 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
692 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
693 ms
9de2e92c-0f57-4357-a913-7dd9a8d8d6c9
434 ms
js
278 ms
modules.ttf
276 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
253 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
255 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
257 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
258 ms
pxiByp8kv8JHgFVrLDD4V1g.woff
262 ms
pxiByp8kv8JHgFVrLDD4V1s.ttf
265 ms
pxiByp8kv8JHgFVrLBT5V1g.woff
262 ms
pxiByp8kv8JHgFVrLBT5V1s.ttf
259 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
259 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
261 ms
pxiEyp8kv8JHgFVrFJM.woff
267 ms
pxiEyp8kv8JHgFVrFJA.ttf
267 ms
pxiByp8kv8JHgFVrLDz8V1g.woff
266 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
268 ms
pxiByp8kv8JHgFVrLFj_V1g.woff
268 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
271 ms
pxiGyp8kv8JHgFVrLPTedA.woff
272 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
272 ms
linkid.js
113 ms
collect
127 ms
collect
117 ms
collect
115 ms
style.min.css
78 ms
codigoverde.com accessibility score
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
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
Links do not have a discernible name
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.
codigoverde.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
codigoverde.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codigoverde.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Codigoverde.com 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.
codigoverde.com
Open Graph data is detected on the main page of Codigo Verde. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: