5.4 sec in total
363 ms
4.7 sec
316 ms
Visit codection.com now to see the best up-to-date Codection content for Spain and also check out these interesting facts you probably never knew about codection.com
Codection es una empresa especializada en el desarrollo de plugins premium, libres y a medida para WordPress y WooCommerce.
Visit codection.comWe analyzed Codection.com page load time and found that the first response time was 363 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
codection.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value11.2 s
0/100
25%
Value10.7 s
7/100
10%
Value2,070 ms
7/100
30%
Value0.004
100/100
15%
Value15.2 s
7/100
10%
363 ms
2838 ms
323 ms
35 ms
234 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 93% of them (70 requests) were addressed to the original Codection.com, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Codection.com.
Page size can be reduced by 331.5 kB (20%)
1.6 MB
1.3 MB
In fact, the total size of Codection.com main page is 1.6 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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 188.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. 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 188.0 kB or 74% of the original size.
Potential reduce by 0 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. Codection images are well optimized though.
Potential reduce by 103.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. This website has mostly compressed JavaScripts.
Potential reduce by 40.5 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. Codection.com needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 26% of the original size.
Number of requests can be reduced by 65 (92%)
71
6
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codection. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and as a result speed up the page load time.
codection.com
363 ms
codection.com
2838 ms
autoptimize_3fddc91498eb72e05be34e1cef3926b9.css
323 ms
css
35 ms
hooks.min.js
234 ms
i18n.min.js
235 ms
frontend-gtag.min.js
238 ms
jquery.min.js
362 ms
jquery-migrate.min.js
248 ms
autoptimize_single_c41a1268ea436c9910e87db9a052713e.js
310 ms
autoptimize_single_0f17ceb0e5032e1b3404749ea73234d7.js
312 ms
jquery.blockUI.min.js
316 ms
js.cookie.min.js
372 ms
woocommerce.min.js
388 ms
select2.full.min.js
490 ms
zxcvbn-async.min.js
395 ms
password-strength-meter.min.js
398 ms
password-strength-meter.min.js
480 ms
lazysizes.min.js
480 ms
autoptimize_single_43851cc7b7e0059bb28df0ba02ec1d0b.js
480 ms
autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js
489 ms
autoptimize_single_0b1719adf5fa7231cb1a1b54cf11a50e.js
488 ms
autoptimize_single_79ebb4e295a9a24dbcaa181a6bd9855b.js
491 ms
sourcebuster.min.js
494 ms
order-attribution.min.js
540 ms
autoptimize_single_830dae7fb9dfd5ac1879a83dd028083d.js
545 ms
foundation.min.js
551 ms
jquery.hoverIntent.min.js
573 ms
swiper-bundle.min.js
654 ms
salvattore.min.js
576 ms
autoptimize_single_5bc964d2dc9b0ee5d2041bb4e9d54943.js
617 ms
devbridge-jquery-autocomplete.min.js
622 ms
joinchat.min.js
630 ms
api.js
62 ms
wp-polyfill.min.js
637 ms
autoptimize_single_ec0187677793456f98473f49d9e9b95f.js
695 ms
enlighterjs.min.js
773 ms
complianz.min.js
702 ms
react.min.js
707 ms
react-dom.min.js
644 ms
react-jsx-runtime.min.js
537 ms
deprecated.min.js
537 ms
dom.min.js
547 ms
escape-html.min.js
544 ms
element.min.js
493 ms
is-shallow-equal.min.js
507 ms
keycodes.min.js
512 ms
priority-queue.min.js
495 ms
compose.min.js
489 ms
private-apis.min.js
498 ms
redux-routine.min.js
494 ms
data.min.js
508 ms
autoptimize_single_36878700722ad5c1f9c12d4c1c543977.js
434 ms
url.min.js
451 ms
api-fetch.min.js
458 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
15 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
27 ms
autoptimize_single_178f4d3163b38b06e6b4a00d28fbb566.js
466 ms
autoptimize_single_aa681f0ff1478919f02ae32c7a466bec.js
471 ms
data-controls.min.js
492 ms
html-entities.min.js
502 ms
notices.min.js
516 ms
autoptimize_single_bdc1e466fc436dc223abbd653674f2ad.js
520 ms
autoptimize_single_3748756fed1fd4b5dd135f2faf47a3fd.js
565 ms
dom-ready.min.js
493 ms
a11y.min.js
493 ms
primitives.min.js
499 ms
autoptimize_single_537006056dd96d88f5191204fb38e2db.js
587 ms
autoptimize_single_505fce8711cc47daf2d944f62d9b0e99.js
476 ms
autoptimize_single_09a2bc6aaea00e614964e5cd5e09400a.js
496 ms
RedSys-y-Bizum-Gateway-para-WooCommerce.png
651 ms
Logo.png
520 ms
rating_over.gif
586 ms
recaptcha__en.js
26 ms
zxcvbn.min.js
241 ms
codection.com 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.
codection.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
codection.com 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codection.com 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 Codection.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.
codection.com
Open Graph data is detected on the main page of Codection. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: