[Support request] Some hints from dareboost.com

[Enrico]

Hi Tom,
I am running some tests

I think this hints could be useful to you:

Each resource should define its content type in order to facilitate their interpretation by web browsers.

This resource should define its content type:
/wp-content/themes/generatepress/fonts/generatepress.woff2

Avoid http-equiv <meta> tags. HTTP headers are more efficient than the http-equiv meta tags.

The <meta http-equiv=””/> tags
The http-equiv meta tags allow to communicate to the web browser information equivalent to the ones of HTTP headers. For example, the meta <meta http-equiv=”content-type”/> will have the same consequences than the HTTP Content-Type header.

Two points don’t stimulate the use of http-equiv meta tags:

Going through the meta requires to interpret the beginning of the HTML page, which is slower than going through the HTTP headers in terms of performance
If the HTTP header is already present, the meta is ignored
In which cases are the <meta http-equiv=””/> useful?
Only one case can justify the presence of these meta tags: if you don’t have access to the configuration of your server, and that is to say to the HTTP headers.

However, we advice you to use a configurable server so that you can establish the most efficient site possible.

This page contains 1 http-equiv meta tag.
If possible, you should replace it: X-UA-Compatible

[Tom]

Thanks for this! I’ll do some research 🙂

[Author]

Posts