Analyze Événement de musique électronique extérieur | Piknic Électronik Montréal

Piknic Électronik l'événement de musique électronique à savourer tous les dimanches l'été, du 22 mai au 2 octobre 2016 au Parc Jean-Drapeau.

Page load speed analysis

  • 58/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    987 ms

  • Resources loaded

    2.9 sec

  • Page rendered

    545 ms

  • Total page load time

    4.4 sec

Click here to check amazing Piknic Electronik content for Portugal. Otherwise, check out these important facts you probably never knew about

We analyzed page load time and found that the first response time was 987 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Page optimization

  • HTML 83.8 kB
    Images 4.7 MB
    Javascripts 534.5 kB
    CSS 66.5 kB

    In fact, the total size of main page is 5.4 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 4.7 MB which makes up the majority of the site volume.

    • Original 83.8 kB
    • After minification 81.3 kB
    • After compression 21.1 kB

    HTML optimization

    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 62.7 kB or 75% of the original size.

    • Original 4.7 MB
    • After optimization 4.6 MB

    Image optimization

    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. Piknic Electronik images are well optimized though.

    • Original 534.5 kB
    • After minification 507.1 kB
    • After compression 175.9 kB

    JavaScript optimization

    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 358.6 kB or 67% of the original size.

    • Original 66.5 kB
    • After minification 54.3 kB
    • After compression 10.8 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 55.7 kB or 84% of the original size.

Network requests diagram

  • csf4klm.js
  • reset.css
  • styles.css
  • prettyPhoto.css
  • jquery-1.8.3.min.js
  • jquery.cycle2.min.js
  • bootstrap-tooltip.js
  • application.js
  • swfobject.js
  • player.js
  • jquery.prettyPhoto.js
  • jquery.smartbanner.css
  • jquery.smartbanner.js
  • addthis_widget.js
  • 6
  • bg_body3.jpg
  • logo.png
  • logo.svg
  • WEBSITE3.png
  • novos_artistas_2.2.png
  • 11800593_1460601384240856_6609653488844531823_n.jpg
  • CASH.png
  • all.js
  • arrow_bottom.svg
  • btn_openmenu.svg
  • btn_openbadges.svg
  • btn_opensearch.svg
  • dates_pt.png
  • twitter_bird_black.png
  • G9PGoYAusXv8HTHppTtFJJxTgPOCIDGvsib9UwQYoy6ff5V8ggM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtg3.eot
  • h3EZD1NJNG2nAJsx3HTos5Z25q7jLtwUD-PZyfe4z83ffFx8ggM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtgM.eot
  • fontello.woff
  • widgets.js
  • bg_left2.png
  • bg_right2.png
  • ga.js
  • bigbox_1
  • leaderboard_bottom
  • footer
  • footer_mobile
  • 300lo.json
  • pt.js
  • ie67-css.d5089428ac7f05efd372.js
  • Nkw-K8-CAojMeJeJZSPepW-WaWUkxx7wrcIdG_g0BSbff5W8ggM-eMI6MK6fw6NuSh90iY83ZAlTifoRdhXtfb.eot
  • sh.8e5f85691f9aaa082472a194.html
  • xd_arbiter.php
  • xd_arbiter.php
  • ping
  • like_box.php
  • UThj8VI7Xhd.css
  • FL1kvZ1wVUz.css
  • 7HwxA8gVs6-.css
  • XDFRGGOuyy0.css
  • cuTBFFsHWNo.css
  • GXvsRy35KkY.css
  • ljoX-PyMzJF.css
  • q68gy-v_YMF.js
  • FJmpeSpHpjS.js
  • 0wM5s1Khldu.js
  • 1bNoFZUdlYZ.js
  • njO1TPvGzoR.js
  • OloiM1PZafe.js
  • LTv6ZK-5zxz.js
  • 1FCa-btixu2.js
  • Oagsvfb4VWi.js
  • pObvZSrFc_4.js
  • Kt4tkgSRvHH.js
  • H3EKDTObx05.js
  • eR-qA8bp1RM.js
  • 1QuX41zDRrx.js
  • 11986408_1477361522564842_9220909556514625619_n.jpg
  • safe_image.php
  • safe_image.php
  • 11218624_1477361649231496_4110098443725447471_n.png
  • 10354686_10150004552801856_220367501106153455_n.jpg
  • 10414880_831589553575444_5777076281418390744_n.jpg
  • 11873516_117964985217965_2476546505907043668_n.jpg
  • 12063556_10208043893878936_3392538030735268815_n.jpg
  • 10985187_1573679042958323_688083077315353377_n.jpg
  • 11430264_1608607789424391_5595270192367685796_n.jpg
  • 12208553_1007988845887881_3540591077323343738_n.jpg
  • 12715242_600183030133249_4829546342116927299_n.png
  • 12814347_1526900600944267_7808654962803937251_n.png
  • 12743611_600181506800068_6982678855597757725_n.png
  • 11218624_1477361649231496_4110098443725447471_n.png
  • wL6VQj7Ab77.png
  • s7jcwEQH7Sx.png
  • QDwYpIaRyfG.png
  • pimRBh7B6ER.png
  • K00K-UgnsKu.png
  • gxbPuQdXIZP.png
  • I6-MnjEovm5.js
  • pQrUxxo5oQp.js

Our browser made a total of 102 requests to load all elements on the main page. We found that 33% of them (34 requests) were addressed to the original, 28% (29 requests) were made to and 13% (13 requests) were made to The less responsive or slowest element that took the longest time to load (987 ms) belongs to the original domain

Additional info on


The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Piknic Electronik. 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 12 to 1 for CSS and as a result speed up the page load time.











Possible request optimization













Normal result

IP address uses IP address which is currently shared with 1 other domain. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 299
NS 299
NS 299

299 Mname:
Serial: 1461783732
Refresh: 21600
Retry: 3600
Expire: 1814400
Minimum-ttl: 300
MX 299 Pri: 20

Language and encoding

Normal result


FR fr language flag


PT pt language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 Portuguese language. Our system also found out that 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.

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Portugal. It lies approximately 3410 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to Portugal or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Piknic Electronik. 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:

Share this report in social media

Analyze another website