Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pfsense.com

pfSense® - World's Most Trusted Open Source Firewall

Page Load Speed

35.3 sec in total

First Response

328 ms

Resources Loaded

11.7 sec

Page Rendered

23.3 sec

About Website

Welcome to pfsense.com homepage info - get ready to check PfSense best content right away, or after learning these important things about pfsense.com

pfSense is a free and open source firewall and router that also features unified threat management, load balancing, multi WAN, and more

Visit pfsense.com

Key Findings

We analyzed Pfsense.com page load time and found that the first response time was 328 ms and then it took 35 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

pfsense.com performance score

0

Network Requests Diagram

pfsense.com

328 ms

www.pfsense.org

794 ms

css

231 ms

VarelaRound-Regular.ttf

169 ms

font-awesome.min.css

210 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pfsense.com, 70% (23 requests) were made to Pfsense.org and 21% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 706.1 kB (55%)

Content Size

1.3 MB

After Optimization

574.4 kB

In fact, the total size of Pfsense.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. 45% of websites need less resources to load. CSS take 597.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.1 kB

  • Original 34.4 kB
  • After minification 34.4 kB
  • After compression 10.3 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 24.1 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 10.7 kB

  • Original 382.1 kB
  • After minification 371.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. PfSense images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 158.2 kB

  • Original 266.6 kB
  • After minification 251.9 kB
  • After compression 108.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 158.2 kB or 59% of the original size.

CSS Optimization

-86%

Potential reduce by 513.1 kB

  • Original 597.4 kB
  • After minification 502.4 kB
  • After compression 84.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. Pfsense.com needs all CSS files to be minified and compressed as it can save up to 513.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (57%)

Requests Now

21

After Optimization

9

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PfSense. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

SEO Factors

pfsense.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 Pfsense.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 Pfsense.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 PfSense. 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: