3.2 sec in total
347 ms
2.2 sec
729 ms
Click here to check amazing Kollectif content for Canada. Otherwise, check out these important facts you probably never knew about kollectif.net
Kollectif existe depuis 2006 et s’est donné comme mission d’informer, de valoriser et de soutenir l’incroyable talent de la communauté architecturale d’ici.
Visit kollectif.netWe analyzed Kollectif.net page load time and found that the first response time was 347 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
kollectif.net performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value18.9 s
0/100
25%
Value13.7 s
2/100
10%
Value14,330 ms
0/100
30%
Value1.607
0/100
15%
Value27.7 s
0/100
10%
347 ms
44 ms
13 ms
94 ms
94 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 56% of them (72 requests) were addressed to the original Kollectif.net, 5% (7 requests) were made to Px.owneriq.net and 5% (6 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (923 ms) belongs to the original domain Kollectif.net.
Page size can be reduced by 1.4 MB (26%)
5.5 MB
4.1 MB
In fact, the total size of Kollectif.net main page is 5.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. 80% 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 530.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 304.2 kB, which is 55% 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 530.0 kB or 95% of the original size.
Potential reduce by 40.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. Kollectif images are well optimized though.
Potential reduce by 736.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 736.8 kB or 74% of the original size.
Potential reduce by 112.8 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. Kollectif.net needs all CSS files to be minified and compressed as it can save up to 112.8 kB or 67% of the original size.
Number of requests can be reduced by 65 (57%)
114
49
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kollectif. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
kollectif.net
347 ms
47588.css
44 ms
shareaholic.js
13 ms
widget.css
94 ms
styles.css
94 ms
cff-style.css
95 ms
font-awesome.min.css
22 ms
eventpost.min.css
95 ms
dashicons.min.css
173 ms
style.css
167 ms
style.css
293 ms
ie.css
170 ms
owl.carousel.css
174 ms
jquery.js
388 ms
jquery-migrate.min.js
256 ms
searchwp-live-search.min.js
257 ms
modernizr.custom.min.js
257 ms
owl.carousel.min.js
422 ms
scripts.js
343 ms
47588.css
23 ms
wp-emoji-release.min.js
341 ms
jquery.form.min.js
260 ms
scripts.js
288 ms
cff-scripts.js
356 ms
eventpost.min.js
357 ms
zerospam.js
401 ms
masonry.min.js
436 ms
jquery.masonry.min.js
403 ms
foundation.min.js
479 ms
wp-embed.min.js
439 ms
2e689bb3bfd2e75382a74779d3885c47.json
33 ms
PDM1-1.jpg
562 ms
PDM2.jpg
558 ms
PDM3.jpg
561 ms
PDM4.jpg
559 ms
PDM5.jpg
639 ms
project_bg.png
553 ms
logo_kollectif_big.png
553 ms
ico_facebook.png
555 ms
ico_twitter.png
561 ms
ico_linkedin.png
637 ms
ico_courriel.png
639 ms
ico_search.png
640 ms
logo_kollectif_small.png
640 ms
image_rollover.png
641 ms
ico_view.png
713 ms
logo_esquisse.png
713 ms
logo_indexdesign.png
714 ms
logo_mission_design.png
714 ms
logo_RAIC-IRAC.png
715 ms
logo_contech.png
714 ms
logo_edp.png
755 ms
logo_v2com.png
756 ms
logo_interdisciplinaire_design.png
757 ms
icon_bulletin.gif
757 ms
ico_facebook_medium.png
765 ms
ico_twitter_medium.png
797 ms
ico_linkedin_medium.png
820 ms
logo_montreal_unesco-mention.png
821 ms
analytics.js
11 ms
logo_montreal_unesco.png
828 ms
20160319-boma-556x292.jpg
914 ms
20160319-durabilys-556x292.jpg
877 ms
collect
13 ms
20160319-oma-556x292.jpg
843 ms
shrMain.min.js
9 ms
M.woff
424 ms
20160319-cca-556x292.jpg
923 ms
20160319-best-556x292.jpg
898 ms
jquery.min.js
387 ms
20160319-mcgill-556x292.jpg
886 ms
20160319-ccc-263x138.jpg
536 ms
20150508-mv-556x292.jpg
566 ms
20160318-c2-556x292.jpg
584 ms
20160318-aapc_-263x138.jpg
521 ms
20160318-utile-263x138.jpg
568 ms
20160318-sdgq-556x292.jpg
593 ms
Olivier_Blouin_Stade-Olympique_Montreal-163x92.jpg
558 ms
BKGD_Kollectif-163x92.jpg
599 ms
Phare_de_Qu%C3%A9bec_Labeaume_Dallaire_2-163x91.jpg
563 ms
Complexe_Bourbon_Montreal_Village_42-163x92.jpg
564 ms
ico_facebook_small.png
577 ms
pageview.gif
45 ms
vglnk.js
16 ms
partners.js
214 ms
pixel.gif
7 ms
pixel.gif
10 ms
sholic.js
6 ms
usermatch
214 ms
beacon.js
7 ms
cms-sh2c.html
82 ms
eexelate.js
5 ms
7 ms
ep
8 ms
ep
7 ms
pixel
16 ms
42 ms
cm
8 ms
ping_match.gif
9 ms
net.php
13 ms
2964
39 ms
pixel
28 ms
generic
7 ms
ermcm
11 ms
pixel
70 ms
generic
22 ms
rs
8 ms
xrefid.xgi
6 ms
pixel.gif
45 ms
pixel.gif
4 ms
match-result
37 ms
xrefid.xgi
5 ms
usermatch
133 ms
ping
45 ms
Vu1.nsAoJWgAAeq9HQAAAAA-%26925
116 ms
pixel
24 ms
casaleopenrtb
68 ms
usersync.aspx
84 ms
casale
74 ms
i.gif
112 ms
pixelssl.htm
114 ms
crum
192 ms
domains
57 ms
crum
221 ms
rum
214 ms
crum
157 ms
rum
204 ms
ddcssl.htm
48 ms
crum
157 ms
kollectif.net accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
kollectif.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
kollectif.net 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 doesn't use 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 Kollectif.net 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 Kollectif.net 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.
kollectif.net
Open Graph data is detected on the main page of Kollectif. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: