Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

api.symfony.com

GitHub - symfony/symfony: The Symfony PHP framework

Page Load Speed

2.5 sec in total

First Response

275 ms

Resources Loaded

1 sec

Page Rendered

1.2 sec

About Website

Welcome to api.symfony.com homepage info - get ready to check Api Symfony best content for Tanzania right away, or after learning these important things about api.symfony.com

The Symfony PHP framework. Contribute to symfony/symfony development by creating an account on GitHub.

Visit api.symfony.com

Key Findings

We analyzed Api.symfony.com page load time and found that the first response time was 275 ms and then it took 2.2 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.

Performance Metrics

api.symfony.com performance score

0

Network Requests Diagram

api.symfony.com

275 ms

index.html

87 ms

stylesheet.css

84 ms

jquery-1.3.2.min.js

248 ms

permalink.js

168 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Api.symfony.com, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Api.symfony.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.3 kB (82%)

Content Size

360.6 kB

After Optimization

65.3 kB

In fact, the total size of Api.symfony.com main page is 360.6 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. 25% of websites need less resources to load. Javascripts take 340.0 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 523 B

  • Original 906 B
  • After minification 736 B
  • After compression 383 B

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 170 B, which is 19% 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 523 B or 58% of the original size.

Image Optimization

-6%

Potential reduce by 51 B

  • Original 903 B
  • After minification 852 B

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. Api Symfony images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 279.4 kB

  • Original 340.0 kB
  • After minification 273.7 kB
  • After compression 60.6 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 279.4 kB or 82% of the original size.

CSS Optimization

-82%

Potential reduce by 15.4 kB

  • Original 18.8 kB
  • After minification 12.1 kB
  • After compression 3.4 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. Api.symfony.com needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (29%)

Requests Now

14

After Optimization

10

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

SEO Factors

api.symfony.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.symfony.com 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 Api.symfony.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.

Social Sharing Optimization

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