2.2 sec in total
345 ms
1.5 sec
379 ms
Welcome to symfony2.ylly.fr homepage info - get ready to check Symfony 2 Ylly best content for France right away, or after learning these important things about symfony2.ylly.fr
Blog Symfony 2 dédié à l'information et à l'actualité du framework Symfony 2 par l'équipe Ylly, merci Fabien Potencier !
Visit symfony2.ylly.frWe analyzed Symfony2.ylly.fr page load time and found that the first response time was 345 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
symfony2.ylly.fr performance score
345 ms
17 ms
25 ms
95 ms
162 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 77% of them (58 requests) were addressed to the original Symfony2.ylly.fr, 9% (7 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (559 ms) belongs to the original domain Symfony2.ylly.fr.
Page size can be reduced by 282.4 kB (49%)
577.0 kB
294.6 kB
In fact, the total size of Symfony2.ylly.fr main page is 577.0 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. 45% of websites need less resources to load. Images take 253.8 kB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.0 kB or 84% of the original size.
Potential reduce by 49.2 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, Symfony 2 Ylly needs image optimization as it can save up to 49.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 172.0 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 172.0 kB or 69% of the original size.
Potential reduce by 20.1 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. Symfony2.ylly.fr needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 86% of the original size.
Number of requests can be reduced by 42 (58%)
72
30
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Symfony 2 Ylly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
symfony2.ylly.fr
345 ms
buttons.js
17 ms
css
25 ms
style.css
95 ms
l10n.js
162 ms
shCore.css
163 ms
shThemeDefault.css
165 ms
shCore.js
187 ms
shBrushBash.js
185 ms
shBrushCpp.js
193 ms
shBrushCSharp.js
237 ms
shBrushCss.js
238 ms
shBrushDelphi.js
239 ms
shBrushDiff.js
275 ms
shBrushGroovy.js
275 ms
shBrushJava.js
278 ms
shBrushJScript.js
314 ms
shBrushPerl.js
315 ms
shBrushPhp.js
316 ms
shBrushPlain.js
364 ms
shBrushPython.js
365 ms
shBrushRuby.js
371 ms
shBrushScala.js
391 ms
shBrushSql.js
392 ms
shBrushVb.js
393 ms
shBrushXml.js
454 ms
swfobject.js
495 ms
ga.js
43 ms
bg_all.gif
105 ms
bg.gif
184 ms
logo.png
102 ms
head.png
158 ms
nav.jpg
105 ms
rss.png
103 ms
search.jpg
161 ms
cont_top.jpg
161 ms
footer.jpg
183 ms
cont_left.jpg
187 ms
br.gif
239 ms
post.png
241 ms
more.gif
241 ms
icon_smile.gif
275 ms
sidbar_top.png
367 ms
Jordan1.jpg
280 ms
Dan.jpg
318 ms
Franck.jpg
320 ms
benoit.png
425 ms
photo-3.jpg
366 ms
photo-1.jpg
373 ms
adrien.jpg
426 ms
samuel.jpg
475 ms
yannick.jpg
457 ms
vincent.jpg
548 ms
sym.png
470 ms
cat.png
473 ms
archives.png
475 ms
link.png
549 ms
footer_logo1.gif
559 ms
footer_logo2.png
553 ms
footer_logo3.png
551 ms
vLVN2Y-z65rVu1R7lWdvyF9q9cSakIY5dTu4rft1WBw.ttf
54 ms
getAllAppDefault.esi
124 ms
likebox.php
137 ms
footer.gif
559 ms
__utm.gif
21 ms
getSegment.php
155 ms
checkOAuth.esi
5 ms
n7IAcY2jJIh.css
87 ms
_rx8naC75Dy.js
124 ms
x5F9OMjKyLw.js
170 ms
ICDbTSzjQEg.js
149 ms
TTCre3391I0.js
148 ms
t.dhj
66 ms
I6-MnjEovm5.js
20 ms
vlXaquuXMrr.js
36 ms
symfony2.ylly.fr SEO score
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Symfony2.ylly.fr 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 Symfony2.ylly.fr 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.
symfony2.ylly.fr
Open Graph description is not detected on the main page of Symfony 2 Ylly. 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: