7.4 sec in total
1.3 sec
5 sec
1.1 sec
Welcome to codecom.co homepage info - get ready to check Codecom best content right away, or after learning these important things about codecom.co
Codecom Provide fibre connectivity, termination & structured cable solutions for telecommunications & data centre Visit our page for more information!
Visit codecom.coWe analyzed Codecom.co page load time and found that the first response time was 1.3 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
codecom.co performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.7 s
0/100
25%
Value10.8 s
7/100
10%
Value2,190 ms
6/100
30%
Value0
100/100
15%
Value15.5 s
7/100
10%
1347 ms
72 ms
61 ms
197 ms
134 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 78% of them (93 requests) were addressed to the original Codecom.co, 8% (10 requests) were made to Fonts.gstatic.com and 5% (6 requests) were made to Fast.wistia.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Codecom.co.
Page size can be reduced by 231.1 kB (9%)
2.5 MB
2.3 MB
In fact, the total size of Codecom.co main page is 2.5 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. 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 208.9 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 208.9 kB or 86% of the original size.
Potential reduce by 15.2 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. Codecom images are well optimized though.
Potential reduce by 7.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.
Number of requests can be reduced by 84 (82%)
102
18
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codecom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
codecom.co
1347 ms
codecom.co
72 ms
premium-addons.min.css
61 ms
front-css.css
197 ms
new-flags.css
134 ms
style.css
167 ms
custom-frontend.min.css
147 ms
custom.css
127 ms
css
97 ms
slick.css
88 ms
jquery.flipster.min.css
183 ms
all.min.css
167 ms
style.css
176 ms
woocommerce.css
213 ms
all.min.css
215 ms
v4-shims.min.css
195 ms
public.css
207 ms
elementor-icons.min.css
241 ms
swiper.min.css
230 ms
post-9.css
218 ms
custom-pro-frontend.min.css
259 ms
post-7.css
241 ms
post-3044.css
282 ms
post-31.css
247 ms
post-169.css
288 ms
css
104 ms
jquery.min.js
282 ms
jquery-migrate.min.js
284 ms
jquery.blockUI.min.js
280 ms
add-to-cart.min.js
284 ms
js.cookie.min.js
330 ms
woocommerce.min.js
331 ms
front-js.js
311 ms
8207776.js
134 ms
js
129 ms
uperm5c2dm.jsonp
108 ms
E-v1.js
122 ms
s6o8a32lu8.jsonp
149 ms
post-3355.css
435 ms
post-3357.css
324 ms
post-2825.css
326 ms
post-2851.css
537 ms
post-3360.css
435 ms
animations.min.css
436 ms
1c67a45d84.js
165 ms
sourcebuster.min.js
435 ms
order-attribution.min.js
377 ms
wp-polyfill-inert.min.js
463 ms
regenerator-runtime.min.js
325 ms
wp-polyfill.min.js
412 ms
react.min.js
397 ms
hooks.min.js
384 ms
deprecated.min.js
380 ms
dom.min.js
529 ms
react-dom.min.js
522 ms
escape-html.min.js
510 ms
element.min.js
507 ms
is-shallow-equal.min.js
495 ms
i18n.min.js
493 ms
keycodes.min.js
526 ms
priority-queue.min.js
522 ms
compose.min.js
512 ms
private-apis.min.js
501 ms
redux-routine.min.js
498 ms
data.min.js
492 ms
jquery.flipster.min.js
546 ms
slick.min.js
473 ms
custom.js
620 ms
slide-menu.min.js
542 ms
navigation.js
469 ms
vue.min.js
540 ms
jet-menu-public-scripts.js
600 ms
jquery.smartmenus.min.js
591 ms
webpack-pro.runtime.min.js
638 ms
webpack.runtime.min.js
632 ms
frontend-modules.min.js
632 ms
8207776.js
405 ms
collectedforms.js
364 ms
banner.js
402 ms
frontend.min.js
523 ms
waypoints.min.js
525 ms
core.min.js
521 ms
frontend.min.js
523 ms
elements-handlers.min.js
520 ms
widgets-scripts.js
610 ms
bg-home-new.jpg
511 ms
logo-codecom.svg
511 ms
landing-QSFP.png
2668 ms
landing-CHDS-2.png
516 ms
landing-CMD-1.png
512 ms
Screen-Shot-6.jpg
510 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjg.woff
206 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjg.woff
352 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjg.woff
364 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjg.woff
417 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjg.woff
413 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjg.woff
414 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjg.woff
413 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjg.woff
415 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjg.woff
414 ms
fa-solid-900.woff
2661 ms
fa-solid-900.ttf
2510 ms
fa-regular-400.woff
1854 ms
fa-regular-400.ttf
1916 ms
fa-brands-400.woff
1968 ms
fa-brands-400.ttf
2768 ms
tsstApxBaigK_hnnc1k.woff
254 ms
Screen-Shot-8.jpg
1959 ms
popover.js
103 ms
Screen-Shot-3.jpg
2448 ms
Screen-Shot-2.jpg
2448 ms
Screen-Shot-5.jpg
2449 ms
Screen-Shot-1.jpg
2448 ms
dots-separator.svg
2449 ms
dots-separator-hover.svg
2446 ms
externalPlayer.js
31 ms
share-v2.js
44 ms
eb006e869a9bae3a0f79ec1401b4b829.jpg
276 ms
638a922ef11b52fb983210dabe00f502.jpg
277 ms
eb006e869a9bae3a0f79ec1401b4b829.jpg
197 ms
codecom.co 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
codecom.co 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
Page has valid source maps
codecom.co 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codecom.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Codecom.co 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.
codecom.co
Open Graph description is not detected on the main page of Codecom. 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: