5.4 sec in total
320 ms
4.5 sec
500 ms
Visit ocedis.com now to see the best up-to-date Ocedis content and also check out these interesting facts you probably never knew about ocedis.com
Visit ocedis.comWe analyzed Ocedis.com page load time and found that the first response time was 320 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ocedis.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value18.3 s
0/100
25%
Value8.1 s
21/100
10%
Value590 ms
50/100
30%
Value0.261
47/100
15%
Value14.7 s
8/100
10%
320 ms
719 ms
186 ms
197 ms
201 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 70% of them (47 requests) were addressed to the original Ocedis.com, 12% (8 requests) were made to Cdnjs.cloudflare.com and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ocedis.com.
Page size can be reduced by 707.4 kB (15%)
4.7 MB
4.0 MB
In fact, the total size of Ocedis.com main page is 4.7 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. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 10.5 kB, which is 24% 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 36.0 kB or 83% of the original size.
Potential reduce by 118.4 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. Ocedis images are well optimized though.
Potential reduce by 405.8 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 405.8 kB or 70% of the original size.
Potential reduce by 147.1 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. Ocedis.com needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 83% of the original size.
Number of requests can be reduced by 26 (46%)
57
31
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ocedis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ocedis.com
320 ms
www.ocedis.com
719 ms
bootstrap.min.css
186 ms
font-awesome.min.css
197 ms
bootstrap-theme.min.css
201 ms
jquery.min.js
27 ms
bootstrap.min.js
199 ms
index.js
217 ms
jquery.fancybox.css
18 ms
jquery.fancybox-buttons.css
20 ms
style.css
281 ms
style-responsive.css
345 ms
index.css
1312 ms
style-site.css
1363 ms
debug.css
1367 ms
b70b1f3a8dffaafdd0a74670134ef354.js
318 ms
jquery-ui.min.js
24 ms
site-full.min.js
388 ms
tmstickup.js
423 ms
menu_mobile.js
437 ms
jquery.bxslider.css
560 ms
jquery.bxslider.js
635 ms
dropdown.js
531 ms
jquery.fancybox.pack.js
17 ms
jquery.fancybox-thumbs.js
20 ms
jquery.fancybox-buttons.js
21 ms
jquery.fancybox-media.js
22 ms
css
53 ms
ga.js
96 ms
analytics.js
95 ms
picto-groupe.png
128 ms
logo.jpg
246 ms
002.jpg
1659 ms
003.jpg
1759 ms
001.jpg
2103 ms
004.jpg
750 ms
fond-fleche-diaporama.png
227 ms
fond-section-1-accueil.jpg
497 ms
586x230.png
724 ms
picto-analyse.png
589 ms
picto-assistance.png
682 ms
picto-formations.png
773 ms
picto-sav.png
831 ms
picto-personnalisation.png
840 ms
picto-marketing.png
864 ms
fond-section-3-accueil.jpg
939 ms
carte.png
930 ms
110x82.png
1016 ms
110x82.jpeg
1082 ms
110x82.jpeg
1130 ms
fond-pied.png
1107 ms
vague.png
1846 ms
logo-pied.png
1198 ms
picto-melfrance.png
1237 ms
picto-melwater.png
1290 ms
picto-ocedis-maroc.png
1344 ms
picto-ocedis.png
1379 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
106 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
107 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
137 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
138 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
154 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
154 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
153 ms
fontawesome-webfont.woff
1474 ms
__utm.gif
119 ms
collect
99 ms
ocedis.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
ocedis.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ocedis.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ocedis.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Ocedis.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.
ocedis.com
Open Graph description is not detected on the main page of Ocedis. 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: