3.6 sec in total
350 ms
3 sec
311 ms
Click here to check amazing Codex content. Otherwise, check out these important facts you probably never knew about codex.si
Reliable partner for agricultural and industrial bearings and other driving elements. We provide the parts that drive your business forward.
Visit codex.siWe analyzed Codex.si page load time and found that the first response time was 350 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
codex.si performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value7.4 s
4/100
25%
Value5.3 s
57/100
10%
Value570 ms
52/100
30%
Value0.002
100/100
15%
Value9.8 s
28/100
10%
350 ms
1194 ms
102 ms
58 ms
235 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 95% of them (39 requests) were addressed to the original Codex.si, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Codex.si.
Page size can be reduced by 83.5 kB (7%)
1.2 MB
1.2 MB
In fact, the total size of Codex.si main page is 1.2 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. 25% of websites need less resources to load. Images take 992.8 kB which makes up the majority of the site volume.
Potential reduce by 82.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 82.9 kB or 80% 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. Codex images are well optimized though.
Potential reduce by 429 B
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 153 B
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. Codex.si has all CSS files already compressed.
Number of requests can be reduced by 24 (63%)
38
14
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
codex.si
350 ms
www.codex.si
1194 ms
main_78361efd.css
102 ms
gtm.js
58 ms
mediaelementplayer-legacy.min.css
235 ms
wp-mediaelement.min.css
330 ms
jquery.min.js
26 ms
main_78361efd.js
533 ms
captcha_78361efd.js
368 ms
dom-ready.min.js
369 ms
hooks.min.js
368 ms
i18n.min.js
368 ms
a11y.min.js
428 ms
jquery.json.min.js
431 ms
gravityforms.min.js
530 ms
utils.min.js
435 ms
vendor-theme.min.js
437 ms
scripts-theme.min.js
528 ms
mediaelement-and-player.min.js
631 ms
mediaelement-migrate.min.js
535 ms
wp-mediaelement.min.js
536 ms
vimeo.min.js
626 ms
sl_SI.png
477 ms
de_DE.png
520 ms
fr_FR.png
520 ms
it_IT.png
521 ms
pl_PL.png
575 ms
hr.png
576 ms
sr_RS.png
579 ms
es_ES.png
579 ms
el.png
585 ms
hu_HU.png
583 ms
ro_RO.png
676 ms
cs_CZ.png
678 ms
sk_SK.png
679 ms
bearing-closeup.jpg
882 ms
codex-bearing-4.jpg
1073 ms
DSC_7320-2048px.jpg
981 ms
codex-warehouse.jpg
1260 ms
helvetica_light_3638bbe2.woff
860 ms
mejs-controls.svg
238 ms
codex.si 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.
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
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.
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.
codex.si 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
codex.si 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codex.si 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 Codex.si 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.
codex.si
Open Graph data is detected on the main page of Codex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: