2.5 sec in total
262 ms
2 sec
233 ms
Click here to check amazing Symfony content. Otherwise, check out these important facts you probably never knew about symfony.fr
Visit symfony.frWe analyzed Symfony.fr page load time and found that the first response time was 262 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
symfony.fr performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.6 s
8/100
25%
Value7.8 s
23/100
10%
Value440 ms
63/100
30%
Value0
100/100
15%
Value6.5 s
58/100
10%
262 ms
176 ms
248 ms
410 ms
25 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Symfony.fr, 50% (29 requests) were made to Symfony.com and 16% (9 requests) were made to Connect.sensiolabs.com. The less responsive or slowest element that took the longest time to load (509 ms) relates to the external source Symfony.com.
Page size can be reduced by 469.7 kB (60%)
788.2 kB
318.4 kB
In fact, the total size of Symfony.fr main page is 788.2 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. 30% of websites need less resources to load. Javascripts take 328.5 kB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 11.9 kB, which is 26% 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 36.2 kB or 80% of the original size.
Potential reduce by 24.4 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 needs image optimization as it can save up to 24.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 198.1 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 198.1 kB or 60% of the original size.
Potential reduce by 211.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. Symfony.fr needs all CSS files to be minified and compressed as it can save up to 211.1 kB or 82% of the original size.
Number of requests can be reduced by 18 (34%)
53
35
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Symfony. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
symfony.fr
262 ms
symfony.com
176 ms
all.css
248 ms
all.js
410 ms
ld.js
25 ms
ga.js
21 ms
fbevents.js
148 ms
bg_page.gif
109 ms
header-logo.svg
99 ms
slproduct.svg
181 ms
icon-download.svg
183 ms
sf-white.svg
177 ms
sf-positive.svg
183 ms
home-main-illu.svg
179 ms
logo-drupal.png
182 ms
logo-phpbb.png
268 ms
logo-laravel.png
269 ms
logo-ezpublish.png
263 ms
logo-orocrm.png
269 ms
logo-piwik.png
267 ms
home-illu-book.svg
265 ms
blue_arrow.png
347 ms
symfony-con-berlin-2016-logo.png
437 ms
symfony-con-berlin-2016-mascot.png
438 ms
sfliveparis-picto.png
349 ms
sflivekoln-picto.png
349 ms
sflivelondon-picto.png
351 ms
certification-big.png
509 ms
twitter-black.gif
438 ms
facebook-black.gif
438 ms
youtube-black.gif
438 ms
linkedin-black.gif
509 ms
sln.css
363 ms
__utm.gif
19 ms
event
19 ms
collect
84 ms
event
175 ms
106 ms
criteohandler
21 ms
nr-885.min.js
18 ms
sln.js
85 ms
dis.aspx
192 ms
b10765e88c
44 ms
dc.js
38 ms
sln_customiser.js
110 ms
__utm.gif
24 ms
event
21 ms
event
101 ms
1c5498dd-0649-4d42-af4b-1de957825f62.png
27 ms
search.png
85 ms
search-alt.png
151 ms
sensiolabs.png
234 ms
sensiolabsinsight.png
387 ms
blackfire.png
247 ms
triangle-down.png
249 ms
picto-connectwithSLBlack.png
250 ms
criteohandler
11 ms
dis.aspx
166 ms
symfony.fr 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.
symfony.fr 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
symfony.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Symfony.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Symfony.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.
symfony.fr
Open Graph description is not detected on the main page of Symfony. 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: