1.6 sec in total
53 ms
1.4 sec
180 ms
Visit discomobile.com now to see the best up-to-date Discomobile content and also check out these interesting facts you probably never knew about discomobile.com
L'Ultime disco mobile contactez nous pour une soumission gratuite.www.discomobile.com mariage dj animateur corporatif
Visit discomobile.comWe analyzed Discomobile.com page load time and found that the first response time was 53 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
discomobile.com performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.7 s
99/100
25%
Value1.0 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value1.4 s
100/100
10%
53 ms
27 ms
40 ms
8 ms
65 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Discomobile.com, 18% (10 requests) were made to Static.xx.fbcdn.net and 14% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (567 ms) relates to the external source Nebula.wsimg.com.
Page size can be reduced by 717.5 kB (49%)
1.5 MB
737.9 kB
In fact, the total size of Discomobile.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 742.7 kB which makes up the majority of the site volume.
Potential reduce by 144.4 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 144.4 kB or 75% of the original size.
Potential reduce by 7.9 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. Discomobile images are well optimized though.
Potential reduce by 476.4 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 476.4 kB or 64% of the original size.
Potential reduce by 88.9 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. Discomobile.com needs all CSS files to be minified and compressed as it can save up to 88.9 kB or 83% of the original size.
Number of requests can be reduced by 34 (64%)
53
19
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discomobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.discoquebec.com
53 ms
css
27 ms
css
40 ms
site.css
8 ms
duel.js
65 ms
addthis_widget.js
12 ms
jq.js
214 ms
48dda4ffe3eda7f1d4117e85482f0325
567 ms
facebookSDKHelper.js
198 ms
social.share.js
199 ms
cookiemanager.js
192 ms
iebackground.js
224 ms
layers.e5ea973510bf60b3db41.js
45 ms
300lo.json
86 ms
fr.js
66 ms
cd2ff9fab9b64a8bc55c1256e8459d2a
567 ms
0e7d7b3bcdc5419ac1992baeb368e67e
363 ms
78be285ad7a31410c9890c2264d14653
348 ms
334b7c5d9cddd710f4fd6d3c19056f9e
216 ms
99061d2daf75314a0ac16c920d09ab10
407 ms
8b860827554cf45e1584d764aed6b2d1
438 ms
xgzbb53t8j-Mo-vYa23n5nhCUOGz7vYGh680lGh-uXM.woff
60 ms
pDM9CVwNx1ufBHCEatJA3D8E0i7KZn-EPnyo3HZu7kw.woff
61 ms
S5z8ixiOoC4WJ1im6jAlYHhCUOGz7vYGh680lGh-uXM.woff
61 ms
sh.8e5f85691f9aaa082472a194.html
58 ms
util.window.js
32 ms
util.fbSDKLoader.js
30 ms
util.instances.js
32 ms
util.model.js
33 ms
helper.js
35 ms
growl.js
44 ms
browser.js
29 ms
sf.core.pkg.js
62 ms
app.css
58 ms
sdk.js
11 ms
141 ms
xd_arbiter.php
35 ms
xd_arbiter.php
42 ms
page.php
194 ms
Ezryo55Cca5.css
29 ms
1kPfZUdGrka.js
36 ms
vb2vBFujz1g.js
60 ms
Qd7TTBR3F_S.js
60 ms
182298_515874121832940_166478101_n.png
195 ms
600864_542594835827535_1049023428_n.jpg
18 ms
1000914_1379766945571872_402522339_n.jpg
19 ms
12391907_10153209125366053_1137140759873765413_n.jpg
18 ms
11947562_978856952178926_3902639518019277055_n.jpg
19 ms
530065_153273431462906_1475786931_n.jpg
16 ms
292205_377393942301126_39003347_n.jpg
34 ms
12687805_215245652159209_807877492012095161_n.jpg
17 ms
wL6VQj7Ab77.png
7 ms
s7jcwEQH7Sx.png
11 ms
R9GKCzjAnbk.js
5 ms
AWWjhOengNF.js
4 ms
YnSasnyq68i.js
5 ms
kQf_jlUv-kX.js
7 ms
discomobile.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
discomobile.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
discomobile.com SEO score
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discomobile.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Discomobile.com 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.
discomobile.com
Open Graph data is detected on the main page of Discomobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: