3.3 sec in total
108 ms
2.3 sec
839 ms
Visit flavorcan.ca now to see the best up-to-date Flavorcan content for India and also check out these interesting facts you probably never knew about flavorcan.ca
Flavorcan International Inc. is a global supplier for distinctively designed flavors and specialty ingredients.
Visit flavorcan.caWe analyzed Flavorcan.ca page load time and found that the first response time was 108 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
flavorcan.ca performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.7 s
17/100
25%
Value14.4 s
1/100
10%
Value2,700 ms
3/100
30%
Value0.18
67/100
15%
Value25.5 s
0/100
10%
108 ms
1371 ms
67 ms
59 ms
57 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 71% of them (70 requests) were addressed to the original Flavorcan.ca, 16% (16 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Flavorcan.ca.
Page size can be reduced by 470.2 kB (19%)
2.5 MB
2.0 MB
In fact, the total size of Flavorcan.ca 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. 75% 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 157.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 157.0 kB or 82% of the original size.
Potential reduce by 302.3 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. Obviously, Flavorcan needs image optimization as it can save up to 302.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.7 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 6.3 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. Flavorcan.ca has all CSS files already compressed.
Number of requests can be reduced by 64 (80%)
80
16
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flavorcan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
flavorcan.ca
108 ms
flavorcan.ca
1371 ms
js
67 ms
prettyPhoto.css
59 ms
wp-video-lightbox.css
57 ms
style.min.css
130 ms
styles.css
63 ms
be.css
139 ms
animations.min.css
159 ms
fontawesome.css
133 ms
jplayer.blue.monday.min.css
136 ms
responsive.css
204 ms
css
33 ms
elementor-icons.min.css
165 ms
frontend-lite.min.css
166 ms
swiper.min.css
170 ms
post-3372.css
162 ms
frontend-lite.min.css
169 ms
global.css
211 ms
post-3651.css
218 ms
css
38 ms
fontawesome.min.css
203 ms
solid.min.css
208 ms
jquery.min.js
211 ms
jquery-migrate.min.js
231 ms
jquery.prettyPhoto.js
251 ms
video-lightbox.js
257 ms
frontend-gtag.min.js
250 ms
js
79 ms
js
80 ms
widget-nav-menu.min.css
409 ms
elementor.css
327 ms
index.js
326 ms
index.js
406 ms
core.min.js
406 ms
tabs.min.js
406 ms
debouncedresize.min.js
406 ms
magnificpopup.min.js
406 ms
menu.js
512 ms
visible.min.js
513 ms
animations.min.js
512 ms
jplayer.min.js
514 ms
api.js
78 ms
api.js
120 ms
enllax.min.js
421 ms
translate3d.js
379 ms
scripts.js
472 ms
wp-polyfill-inert.min.js
461 ms
regenerator-runtime.min.js
405 ms
wp-polyfill.min.js
401 ms
index.js
385 ms
jquery.smartmenus.min.js
378 ms
webpack-pro.runtime.min.js
377 ms
webpack.runtime.min.js
374 ms
frontend-modules.min.js
436 ms
hooks.min.js
434 ms
i18n.min.js
440 ms
frontend.min.js
435 ms
waypoints.min.js
403 ms
frontend.min.js
395 ms
elements-handlers.min.js
486 ms
underscore.min.js
435 ms
wp-util.min.js
437 ms
frontend.min.js
418 ms
js
163 ms
js
164 ms
flavorcan-international-logo-retina.jpg
366 ms
Logos.png
375 ms
Splash-Overlap.png
414 ms
Icon-2.png
382 ms
Icon.png
383 ms
156 ms
Vector.png
273 ms
Icon-3.png
302 ms
FSSC2023-2026.png
319 ms
flavorcan-international-flavour-design-b1.jpg
308 ms
Background-Image.png
375 ms
flavorcan-international-flavour-design-b2.jpg
348 ms
flavorcan-international-flavour-design-b3.jpg
331 ms
embed
322 ms
pxiEyp8kv8JHgFVrJJfedA.woff
108 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
123 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
123 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
122 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
122 ms
KFOmCnqEu92Fr1Mu4mxM.woff
123 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
122 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
135 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
136 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
135 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
135 ms
1Ptgg87LROyAm3Kz-Ck.woff
45 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtU.woff
47 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff
45 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtU.woff
46 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff
46 ms
eicons.woff
295 ms
42 ms
js
54 ms
flavorcan.ca 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
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.
flavorcan.ca 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
flavorcan.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Flavorcan.ca 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 Flavorcan.ca 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.
flavorcan.ca
Open Graph data is detected on the main page of Flavorcan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: