4.7 sec in total
885 ms
3.5 sec
313 ms
Click here to check amazing Direct Salles content for France. Otherwise, check out these important facts you probably never knew about directsalles.com
Annuaire et moteur de recherche de location de salle de mariage, salle de réception, salle de séminaire, salle de conférence, réunion, location de salle de fête
Visit directsalles.comWe analyzed Directsalles.com page load time and found that the first response time was 885 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
directsalles.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.4 s
39/100
25%
Value5.7 s
51/100
10%
Value260 ms
83/100
30%
Value0
100/100
15%
Value7.9 s
43/100
10%
885 ms
481 ms
21 ms
492 ms
494 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Directsalles.com, 23% (28 requests) were made to Static.directsalles.com and 19% (24 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (885 ms) belongs to the original domain Directsalles.com.
Page size can be reduced by 514.7 kB (41%)
1.3 MB
740.5 kB
In fact, the total size of Directsalles.com main page is 1.3 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. 70% of websites need less resources to load. Javascripts take 559.4 kB which makes up the majority of the site volume.
Potential reduce by 78.2 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 78.2 kB or 81% of the original size.
Potential reduce by 26.7 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. Direct Salles images are well optimized though.
Potential reduce by 369.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 369.4 kB or 66% of the original size.
Potential reduce by 40.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. Directsalles.com needs all CSS files to be minified and compressed as it can save up to 40.3 kB or 86% of the original size.
Number of requests can be reduced by 62 (53%)
118
56
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Direct Salles. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.directsalles.com
885 ms
common+1.0.141.css
481 ms
jsapi
21 ms
jquery.cookie.js
492 ms
jquery.simplemodal-1.3.min.js
494 ms
jquery.defaultvalue.js
492 ms
gmaps.js
503 ms
maps
61 ms
jquery.autocomplete.js
504 ms
eshapes.js
507 ms
home.js
567 ms
jquery.cross-slide.js
570 ms
jquery.autocomplete.css
576 ms
jquery.min.js
30 ms
bg-direct-salles.jpg
310 ms
100578+180903.jpg
461 ms
99646+180903.jpg
460 ms
248135+180903.jpg
487 ms
249513+180903.jpg
487 ms
salon+180903.jpg
485 ms
96043+180903.jpg
501 ms
salle-reception+180903.jpg
548 ms
72596+180903.jpg
548 ms
265289+30302.jpg
570 ms
265304+30302.jpg
567 ms
265285+30302.jpg
569 ms
265265+30302.jpg
739 ms
265273+30302.jpg
626 ms
bg-frame.jpg
97 ms
dot.gif
97 ms
col-plt.jpg
209 ms
col-evt.jpg
210 ms
close-big.gif
96 ms
plusone.js
125 ms
bg_slv_path.gif
195 ms
bg-button-gold.gif
174 ms
puce.jpg
207 ms
bg-btn-devis.gif
185 ms
page_top.gif
166 ms
ga.js
44 ms
like.php
179 ms
__utm.gif
28 ms
slide-01.jpg
186 ms
slide-02.jpg
264 ms
slide-03.jpg
279 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
52 ms
fastbutton
229 ms
likebox.php
214 ms
postmessageRelay
40 ms
-1cfYrhulAt.js
491 ms
LVx-xkvaJ0b.png
368 ms
api.js
42 ms
core:rpc:shindig.random:shindig.sha1.js
73 ms
2536007149-postmessagerelay.js
70 ms
FbUd6dZS1Af.css
277 ms
dGJLq38YL-C.css
288 ms
jsSBgYmM8Bv.css
295 ms
Vqr3k1iJZIS.js
358 ms
x5F9OMjKyLw.js
469 ms
ICDbTSzjQEg.js
341 ms
TTCre3391I0.js
351 ms
C-h3nYPqETO.js
420 ms
rFmE1g6Dkoz.js
605 ms
7cm7D75Y0Sf.js
486 ms
oRoBXlHCpEy.js
422 ms
336JejShbZp.js
457 ms
sj-JwAJi4AH.js
551 ms
DKRU1bYTkTw.js
486 ms
ZNPAadQNc33.js
517 ms
W0OV23mIOyO.js
532 ms
36TdwhIHusi.js
548 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
16 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
89 ms
10943637_883039448383867_4064593614546293599_n.jpg
124 ms
10471326_911145932239885_3876597620851230421_n.png
119 ms
1379841_10150004552801901_469209496895221757_n.jpg
118 ms
12239971_145112492511293_941590500849054584_n.jpg
140 ms
10342784_261261514065539_1359799462421220621_n.jpg
117 ms
12196137_1662528064030250_1265293008498604230_n.jpg
117 ms
10805773_377559225758967_5241206680295357118_n.jpg
118 ms
1517686_574131786057161_6106366813785976825_n.jpg
118 ms
wL6VQj7Ab77.png
109 ms
s7jcwEQH7Sx.png
108 ms
pUFVdPjIRct.png
75 ms
I6-MnjEovm5.js
91 ms
vlXaquuXMrr.js
91 ms
common.js
20 ms
map.js
41 ms
overlay.js
36 ms
util.js
73 ms
marker.js
32 ms
StaticMapService.GetMapImage
124 ms
onion.js
23 ms
openhand_8_8.cur
65 ms
ViewportInfoService.GetViewportInfo
102 ms
stats.js
38 ms
controls.js
36 ms
infowindow.js
63 ms
transparent.png
29 ms
css
82 ms
google4.png
59 ms
mapcnt6.png
51 ms
sv5.png
52 ms
1.png
106 ms
vt
14 ms
vt
20 ms
vt
15 ms
vt
18 ms
vt
22 ms
tmapctrl.png
18 ms
cb_scout5.png
25 ms
tmapctrl4.png
23 ms
imgs8.png
28 ms
2.png
94 ms
3.png
92 ms
4.png
92 ms
5.png
94 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
28 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
62 ms
AuthenticationService.Authenticate
264 ms
directsalles.com 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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
directsalles.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
directsalles.com SEO score
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Directsalles.com 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 Directsalles.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.
directsalles.com
Open Graph description is not detected on the main page of Direct Salles. 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: