2.3 sec in total
362 ms
1.7 sec
282 ms
Welcome to olymel.com homepage info - get ready to check Olymel best content for Canada right away, or after learning these important things about olymel.com
Découvrez nos produits (charcuterie, porc, jambon) ainsi que nos recettes, rapides et faciles à préparer.
Visit olymel.comWe analyzed Olymel.com page load time and found that the first response time was 362 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
olymel.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value11.7 s
0/100
25%
Value5.3 s
57/100
10%
Value780 ms
37/100
30%
Value0.001
100/100
15%
Value10.7 s
22/100
10%
362 ms
328 ms
55 ms
74 ms
99 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 91% of them (68 requests) were addressed to the original Olymel.com, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (715 ms) belongs to the original domain Olymel.com.
Page size can be reduced by 445.1 kB (14%)
3.2 MB
2.8 MB
In fact, the total size of Olymel.com main page is 3.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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 22.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 22.9 kB or 77% of the original size.
Potential reduce by 112.8 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. Olymel images are well optimized though.
Potential reduce by 97.1 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.1 kB or 63% of the original size.
Potential reduce by 212.4 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. Olymel.com needs all CSS files to be minified and compressed as it can save up to 212.4 kB or 77% of the original size.
Number of requests can be reduced by 17 (23%)
73
56
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olymel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
362 ms
accueil.css
328 ms
en.css
55 ms
css.php
74 ms
responsive.css
99 ms
jquery-1.7.1.min.js
136 ms
compact_js.php
173 ms
en.js
65 ms
js.php
87 ms
bg.jpg
339 ms
header_img.jpg
148 ms
header_img.jpg
143 ms
header_img.jpg
130 ms
header_img.jpg
95 ms
logo_default.png
95 ms
25_en.png
97 ms
bt-search-en.png
112 ms
analytics.js
95 ms
white_side.png
100 ms
corners.png
103 ms
sides_ew.png
114 ms
sides_ns.png
125 ms
circle_arrow.png
159 ms
home.png
483 ms
home.png
216 ms
home.png
179 ms
home.png
699 ms
home.png
575 ms
home.png
228 ms
home.png
300 ms
home.png
298 ms
home.png
512 ms
home.png
365 ms
home.png
531 ms
home.png
430 ms
home.png
512 ms
home.png
628 ms
home.png
582 ms
home.png
578 ms
home.png
694 ms
home.png
667 ms
home.png
644 ms
home.png
633 ms
between.png
647 ms
normal.png
678 ms
between.png
666 ms
wACK7EDRnYrRLATIEWyEmoCK7EDRnYrRLAUIEWyE0ECK7EDRnYrRLAVIEWyFDMCK7EDRnYrRLAWIEWyFSUCK7EDRnYrRLAXIEWyFqsCK7EDRnYrRFmwFCsAAAA=
51 ms
fbds.js
146 ms
normal.png
658 ms
normal.png
674 ms
linkid.js
26 ms
bg_content_bottom.png
602 ms
bg_content.png
610 ms
dhl-arrow-bg.png
626 ms
bg-top.png
715 ms
fb24.png
610 ms
instagram.png
618 ms
collect
36 ms
collect
74 ms
bg-main-menu.png
620 ms
bt_menu.png
620 ms
sn_main_menu_logo_2014.png
624 ms
bt_newsletters.png
602 ms
province_choice_1.png
586 ms
93 ms
province_choice_2.png
556 ms
arrow_select_language.png
549 ms
province_choice_3.png
482 ms
province_choice_4.png
482 ms
province_choice_5.png
466 ms
bg-search-input.png
430 ms
bt-clear_input.png
367 ms
bt_corpo.png
325 ms
bg_footer.png
313 ms
bt_foot.png
295 ms
olymel.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
Image elements do not have [alt] attributes
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.
olymel.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
olymel.com SEO score
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
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olymel.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Olymel.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
olymel.com
Open Graph data is detected on the main page of Olymel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: