Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

securityheaders.io

Analyse your HTTP response headers

Page Load Speed

1.6 sec in total

First Response

160 ms

Resources Loaded

1.3 sec

Page Rendered

150 ms

securityheaders.io screenshot

About Website

Click here to check amazing Security Headers content for Spain. Otherwise, check out these important facts you probably never knew about securityheaders.io

Quickly and easily assess the security of your HTTP response headers

Visit securityheaders.io

Key Findings

We analyzed Securityheaders.io page load time and found that the first response time was 160 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

securityheaders.io performance score

0

Network Requests Diagram

securityheaders.io

160 ms

securityheaders.io

509 ms

jquery.min.js

27 ms

skel.min.js

50 ms

skel-layers.min.js

54 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Securityheaders.io, 32% (6 requests) were made to Securityheaders.azureedge.net and 21% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (509 ms) belongs to the original domain Securityheaders.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.2 kB (47%)

Content Size

174.9 kB

After Optimization

92.7 kB

In fact, the total size of Securityheaders.io main page is 174.9 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. 20% of websites need less resources to load. Javascripts take 106.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.7 kB

  • Original 24.1 kB
  • After minification 24.1 kB
  • After compression 5.4 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 18.7 kB or 78% of the original size.

JavaScript Optimization

-28%

Potential reduce by 29.6 kB

  • Original 106.0 kB
  • After minification 105.9 kB
  • After compression 76.3 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 29.6 kB or 28% of the original size.

CSS Optimization

-76%

Potential reduce by 33.8 kB

  • Original 44.8 kB
  • After minification 44.7 kB
  • After compression 11.0 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. Securityheaders.io needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (79%)

Requests Now

14

After Optimization

3

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

SEO Factors

securityheaders.io 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 Securityheaders.io 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 Securityheaders.io 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 data is detected on the main page of Security Headers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: