11.4 sec in total
593 ms
10.7 sec
159 ms
Visit tonik.ca now to see the best up-to-date Tonik content for Canada and also check out these interesting facts you probably never knew about tonik.ca
Agence Tonik est une agence de relations publiques et un diffuseur de communiqué de presse
Visit tonik.caWe analyzed Tonik.ca page load time and found that the first response time was 593 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tonik.ca performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.8 s
55/100
25%
Value2.3 s
99/100
10%
Value180 ms
91/100
30%
Value0.003
100/100
15%
Value6.9 s
54/100
10%
593 ms
43 ms
6 ms
10 ms
12 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 25% of them (23 requests) were addressed to the original Tonik.ca, 22% (20 requests) were made to Static.xx.fbcdn.net and 13% (12 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (8.9 sec) relates to the external source Facebook.com.
Page size can be reduced by 86.6 kB (27%)
317.8 kB
231.2 kB
In fact, the total size of Tonik.ca main page is 317.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 177.8 kB which makes up the majority of the site volume.
Potential reduce by 13.7 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 13.7 kB or 73% of the original size.
Potential reduce by 25.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. Obviously, Tonik needs image optimization as it can save up to 25.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.3 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 41.2 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. Tonik.ca needs all CSS files to be minified and compressed as it can save up to 41.2 kB or 81% of the original size.
Number of requests can be reduced by 38 (44%)
87
49
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tonik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
tonik.ca
593 ms
css
43 ms
screen.css
6 ms
form.css
10 ms
site_base.css
12 ms
jquery.min.js
28 ms
public.js
9 ms
widget.js
60 ms
plusone.js
90 ms
gtm.js
93 ms
cb=gapi.loaded_0
47 ms
mixpanel-2.1.min.js
46 ms
bg-tonik.jpg
44 ms
ga.js
33 ms
cb=gapi.loaded_1
15 ms
cb=gapi.loaded_2
66 ms
badge
153 ms
logo-tonikbg.png
11 ms
logo-tonik3.png
10 ms
loupe.jpg
59 ms
bt-plus-com.jpg
59 ms
shadow.png
61 ms
border-bottom-extraits.jpg
62 ms
border-bottom.png
61 ms
icon-tel.png
61 ms
icon-mail.png
60 ms
icon-facebook.png
61 ms
icon-twitter.png
62 ms
icon-linkedin.png
61 ms
icon-google.png
62 ms
icon-flikr.png
63 ms
icon-foursquare.png
64 ms
icon-youtube.png
64 ms
bg-footer.jpg
63 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
58 ms
oct.js
66 ms
25 ms
__utm.gif
27 ms
postmessageRelay
42 ms
collect
59 ms
adsct
170 ms
adsct
48 ms
2710
144 ms
3193398744-postmessagerelay.js
28 ms
rpc:shindig_random.js
40 ms
rs=AGLTcCPxxcsaEHPLIxgGb9au86GYFsrXHA
15 ms
likebox.php
8893 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
20 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
19 ms
cb=gapi.loaded_0
81 ms
photo.jpg
99 ms
badges-eaefc7099b8352c2d91a1a3d728dcac7.png
73 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
22 ms
2679
89 ms
2683
78 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
54 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
58 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
63 ms
2701
65 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
6 ms
2670
130 ms
2688
53 ms
2651
30 ms
2722
35 ms
2703
31 ms
410ucuAGgaJ.css
178 ms
tSbl8xBI27R.css
222 ms
VyhHmC9SnBT.css
263 ms
q68gy-v_YMF.js
374 ms
8w-1WQE8wsO.js
396 ms
0wM5s1Khldu.js
300 ms
1bNoFZUdlYZ.js
303 ms
OloiM1PZafe.js
303 ms
LTv6ZK-5zxz.js
428 ms
1FCa-btixu2.js
394 ms
Oagsvfb4VWi.js
405 ms
pObvZSrFc_4.js
404 ms
Kt4tkgSRvHH.js
413 ms
H3EKDTObx05.js
422 ms
eR-qA8bp1RM.js
420 ms
11188358_10153238401134788_4065757540086133427_n.png
256 ms
430236_10150635586669788_2023969016_n.jpg
295 ms
10312588_1577592652559760_8936948717345145334_n.jpg
335 ms
23816_383518331261_4866473_n.jpg
423 ms
12540578_160019344366225_3835179601112101912_n.jpg
373 ms
12733963_10154021089005407_6019501466681198357_n.jpg
378 ms
10847826_10153356966927656_8947931572064650805_n.jpg
378 ms
10553338_1112388595448555_8632506784363633441_n.jpg
375 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
70 ms
gxbPuQdXIZP.png
46 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
90 ms
tonik.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
tonik.ca 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
tonik.ca SEO score
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tonik.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Tonik.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.
tonik.ca
Open Graph description is not detected on the main page of Tonik. 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: